DNS server from pppoe does not work with 2.0.2
-
The interface status page doesn't have the smarts to split up the DNS servers. They always show up on the "wan" interface.
-
They always show up on the "wan" interface.
Ok, but why "Allow DNS server list to be overridden by DHCP/PPP on WAN" do not work?
Work fine on 2.0.1 with three pppoe connections (6 dns server). -
I don't know. I didn't specifically test pppoe on mine at home with 2.0.2.
-
Hi,
I am having the same issue with 2.0.2. I switched my slice mack to 2.0.1. Nothing else changed in config. pfSense is not getting the DNS servers from the PPPoE connection…Regards,
Alexander -
Alexander, did you have one or more pppoe connections?
-
Do you have anything showing up in /var/etc/nameserver_* ?
-
[2.0.2-RELEASE][user@pfsense]/var/etc(7): ls -l | grep nameserver [2.0.2-RELEASE][user@pfsense]/var/etc(8):
No such file.
-
-
Install the System Patches package, then fetch/apply this patch to see if it helps:
Name: ppp_dns_fix
URL: http://files.nyi.pfsense.org/jimp/patches/ppp_dns_fix_202.patch
Path Strip Count: 1
Base: /
Ignore Whitespace: [X] -
Sorry not enough time atm to play around… maybe slu can test...
-
Install the System Patches package, then fetch/apply this patch to see if it helps:
Name: ppp_dns_fix
URL: http://files.nyi.pfsense.org/jimp/patches/ppp_dns_fix_202.patch
Path Strip Count: 1
Base: /
Ignore Whitespace: [X][2.0.2-RELEASE][user@pfsense]/var/etc(13): ls -l | grep nameserver -rw-r--r-- 1 root wheel 32 Dec 21 20:29 nameserver_pppoe0 -rw-r--r-- 1 root wheel 32 Dec 21 20:29 nameserver_pppoe1 -rw-r--r-- 1 root wheel 32 Dec 21 20:29 nameserver_pppoe2 [2.0.2-RELEASE][user@pfsense]/var/etc(14):
Thank you very much, it work now!
Pfsense 2.0.3 release now?I must remove the patch before I upgrade to the next version? How to handle it?
-
The patch won't reapply itself so it's safe to keep as-is.
There may need to be a 2.0.3, hard to tell just yet.
-
There may need to be a 2.0.3, hard to tell just yet.
It is dangerous to upgrade a remote pfsense with pppoe wan connection to 2.0.2, the system can not reconnect without dns server to my openvpn server.
-
Only if you have not manually defined DNS servers.
-
So the solution for me is to note the DNS servers now, then switch slices, enter the DNS server manually, install the package and the patch (think I can't without DNS, won't find the servers), then remove the manual DNS servers?
I think I'll wait for the next maintenance release…
-
Or just define custom DNS servers (like 8.8.8.8 8.8.4.4) and don't use the ones from PPPoE.
-
Yep- I did the upgrade at my office remotely and had no problems. I had defined dns so did not run into this.
-
Run into the same problem while doing remote update… Had to specify DNS servers manually. I want to see release without need to patch. Expecting quick 2.0.3
-
Had the same problem. The patch solved it. Due to the possibility of locking yourself out when doing the patch remotely, I would prefer a version 2.0.3 of the upgrade too.
Thanks for the great work
Sebastian
-
There likely will be a 2.0.3 but it may not be immediately, in case someone finds a similar bug in the next few days we don't want to end up having a 2.0.4 so soon either :-)