Sorry, completely wrong. I want to try to catch this before it dies.
(BTW, several people have started to emal 'megazone' instead of 'support'
for support questions. Bad idea on two counts:
1. I will just stick any support mail I get in with the rest of the support
mail and answer it like all the rest, I don't play favorites since I
believe in being fair to everyone. (This applies to new email, obviously
if it is part of an incident I'm working on it is a different matter.)
2. 'support' goes to all of us, 'megazone' just me. And somedays I'm not
in the office. Like today - I was moving into a new place. And I will be
out parts of several days this week as I get moved in. So no one will see
your email. (Also, I generally sit with a mail window open in the support
spool, I check my spool only now and then. I'll see support mail first.)
Right now I'm in my new place, PG&E messed up so I have no power. But
I do have a phone and a laptop with a full charge - so I'm working by the
glow of an active matrix LCD display. Now on to the issue...)
If you have 30 ports setup for network and set assigned to 192.10.20.1 it
will got up to 192.10.20.30 and then loop back to 192.10.20.1.
Now, we do have a minor bug so that if the PM is fully loaded and someone
hangs up and another user dials in *immediately* the routing table won't have
timed out, so the PM may go to .31. We've had rare reports of some PMs that
are really being beat on pushed to .32.
We know about this and it is being worked on.
Now, if you ever have it go beyound that, something is very wrong. To date
I have never seen a report of that kind of action. And we have an extremely
large user base doing assigned IPs.
-MZ
-- Livingston Enterprises Technical Support Phone: 800-458-9966 FAX: 510-426-8951 support@livingston.com <http://www.livingston.com/> 6920 Koll Center Parkway #220, Pleasanton, CA 94566