We did not reject their setting, we just said "Hey, we can't tell you what
the secondary is".
>I would guess that since the PM3 has no secondary DNS set, it rejected
>the users' secondary DNS setting. Is there anyway to get it to
>either set a secondary DNS at PM3; or not reject the secondary DNS
>from the user?
You can set a secondary DNS server on the PM-3.
>As a side question, isn't it part of PPP negotiations for the PM3 to
>tell the users' DUN what it's DNSes are (ie. don't set DNS in DUN at all)?
Only if the client ASKS for it. That's how RFC 1877 works. If the client
asks, and we have the data, we tell them.
-MZ
-- Livingston Enterprises - 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