It can be depending on the traffic, but in general - no. Very, very, very
rarely is there an issue reported associated with this.
>Is this something that ComOS is just doing wrong? Would enabling OSPF help?
Say you have a route on the gateway saying 1.1.1.1 is on PM2. Well, that
IP is in the pool but the user isn't on. Someone sends a packet for 1.1.1.1
and the gateway sends it to PM2. PM2 doesn't have a route for 1.1.1.1 as
it is not active, so it ends up sending it to the default route - back to
the gateway. Which then sends it back - and it bounces until TTL is up.
There is a request open to have a PM squelch packets that come in for a
pool IP address when that address isn't in use. But is hasn't been a
high priority as it hasn't been a major issue for most users. And the
ofilter on the ether0 as describe can do it today. People just want it
to be automatic.
-MZ
-- Lucent Remote Access Division - Chair, Department of Interstitial Affairs Phone: 800-458-9966 510-737-2100 FAX: 510-737-2110 megazone@livingston.com For support requests: support@livingston.com <http://www.livingston.com/> Snail mail: 4464 Willow Road, Pleasanton, CA 94588 - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe portmaster-users' in the body of the message.