> -----Original Message-----
> From: Manuel Kasper [mailto:mk at neon1 dot net]
> Sent: Friday, 27 August 2004 06:38
> We recently discovered that david me's PPPoE problems (being
> able to connect with m0n0wall 1.0, but not 1.1) were related
> to two MPD options that were introduced after 1.0 and that
> request the primary/secondary DNS servers from the peer.
> Apparently, with these options specified, he wasn't able to
> connect; removing them solved the issue. Looking at MPD code,
> it seems that MPD shouldn't insist on getting the DNS servers
> if the peer rejects the request, and now (once more) it's not
> clear whether it's MPD or his ISP's PPP server that is at fault.
> Is there anybody else that can't connect with PPPoE and
> m0n0wall 1.1 (while 1.0 works)?
> To -dev: if somebody on this list is looking for something to
> do/help with, investigating this issue would be available.
> Any takers? It's about the "set ipcp enable req-pri-dns" and
> "set ipcp enable req-sec-dns" MPD options. Of course we could
> just make m0n0wall not generate those MPD options if the
> "Allow DNS server list to be overridden by DHCP/PPP on WAN"
> option is not checked, but maybe there's a better solution.
> - Manuel
No problems here with 1.1 and PPPoE. I had 1.0 running, and the vast
majority of the 1.1 beta releases, and now 1.1 final - they all work
better than 1.0 did - 1.0 failed to work properly in the "Allow
override" when the IP was assigned to a PPPoE connection. There is
definitely email aboot this issue in the lists.
1.1 is fine here.
Hilton Travis Phone: +61 (0)7 3343 3889
(Brisbane, Australia) Phone: +61 (0)419 792 394
Manager, Quark IT http://www.quarkit.com.au
Quark AudioVisual http://www.quarkav.net
http://www.threatcode.com/ <-- its now time to shame poor coders
into writing code that is acceptable for use on today's networks
War doesn't determine who is right. War determines who is left.