DNS server not correctly set in PPPoE mode

[matthijs]

On the blog, a user reports that his PPPoE connection is not working and the DNS server is shown as "0" on the dashboard.

Downgrading to beta2 helps.

 http://blog.fonosfera.org/2370-release-candidate-released/#comment-206261

[matthijs]

On the blog, xsash and dbotoca report that this was still working in beta3.

[matthijs]

Fix for this bug

[matthijs]

Turns out there was some really broken code for the DNS handling, not sure what I was thinking when I wrote that...

In any case, I've attached a fix to this ticket. To apply it, simply run this command on your Fonera:

root@Fonera:~# wget -O /lib/fon/config.sh http://trac.fonosfera.org/fon-ng/raw-attachment/ticket/1229/config.sh

Please let me know if this works for you!

[dbotoca]

Thank you for the config.sh correction, it works now on PPoE/DNS/Automatic.

I had to edit manually my /lib/fon/config.sh , couldn't figured out why I was getting bad address on trac.fonosfera.org on the wget - O ...... command. Definetely I was doing something wrong. :(

[matthijs]

Ah, I suspect you experienced another bug (for which there is no ticket, but I already have a fix ready), where setting a static DNS server did not overwrite the previous DNS server, but appended the new setting to the list of DNS servers. This would lead to an invalid nameserver (due to this bug), followed by the valid (custom) DNS server you configured. Wget then failes to resolve any names. Dnsmasq, which takes care of DNS resolution for all PC's in your network, seems to simply ignore the invalid entry and instead uses the valid DNS server, which explains why your internet connection was otherwise working.

For anyone also suffering from this wget error: Rebooting your Fonera and then running the wget command is probably the easiest way to work around this.

[matthijs]

(In [2213]) fonbase: Really fix pppoe mode when DNS is set to automatic.

In r2017, this same thing was supposed to be fixed, but the fix was completely wrong. This fixes the broken condition and also explicitly sets the peerdns value to 1 (which is the default) when using automatic dns to make the code a bit more clear.

Due to a syntax error in the broken code, automatic DNS was still working after r2017, but static DNS was not. When in r2129 this syntax error was fixed, static DNS started working, but automatic DNS was broken again.

References: #686 Closes: #1229