Yes.. And this is the first time I've seen this problem since upgrading.
> The only similar problem that I still see in 3.1.4 is that, in at least
> OUR case, a portmaster at the upper edge of a class of an address space
> sometimes issues an IP address *ONE* higher than it should. E.g. we have
> a pm whose assigned addr in a Class C is a.b.c.225, so the 30 address
> range should be a.b.c.225 - a.b.c.254; but it sometimes assigns
> a.b.c.255, which obviously is a problem. PM's *NOT* at the edge of the
> Class C do not, thus far, exhibit this behaviour. E.g. the PM whose
> range is a.b.c.195 - a.b.c.224 has never accidentally issued a.b.c.225.
This occured on our second PM2-30 which is one of the most heavily used,
but its right in the center of a flat class C.
-- ----------------------------------------------------------------------- Dr. Delete, Ph.D. (doc@NetWare.is.LaMe.ORG) --------------------------- "You can't understand the user's mind" -------------------------------- "But try with your books and degrees" --------------------------------- "If you let yourself go and open your mind" --------------------------- "I bet you'd be doing like me.... and it ain't so bad" ---------------- Alice In Chains, "Dirt", "Junkhead (track 7)" ------------------------- -----------------------------------------------------------------------