Well, I understand the situation now, thanks for everyone's comments.
I have to agree this sounds like a ComOS problem. The previously posted
output filters depend on the PM having a pool on a nice address block
boundary, which isn't always the case. So the filters can be a bit more
complicated.
Since the PM obviously *knows* that the address isn't in use, I can't
imagine this would be a difficult or risky fix. Is there some subtle issue
here that makes this "squelching" a risky thing to implement?
Our PM3 use a default router that's on the local switched 10MB ethernet, so
I don't think we are hurting from this. But it seems like something worth
fixing.
I'm going to send mail to rfe@livingston.com. Maybe if enough people ask
it will get rolled into the engineering plans.
Thanks again.
Rob
-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-users' in the body of the message.