DNS server from pppoe does not work with 2.0.2
-
[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 :-)
-
Does it matter??? In the end? It seems that the current pace of releases is way behind the base OS. So that could be a way to speed it up?
-
No, changing the base OS is a huge undertaking. It's not that simple, and has nothing to do with point/bug releases. The base OS will move to FreeBSD 8.3 with pfSense 2.1, and for 2.2 it will move to 9.x. If you want to get a newer base OS, then the shortest path is to help get 2.1 out the door. :-)
If we released 2.0.3 today the only fix would be the PPP DNS issue. Which would be OK, I'd just be worried that another bug would surface in the next few days and we'd just have to turn right back around again and redo the whole release process (which isn't quick/easy) three times in a week (and one with a major Holiday in it, no less).
-
No, changing the base OS is a huge undertaking. It's not that simple, and has nothing to do with point/bug releases. The base OS will move to FreeBSD 8.3 with pfSense 2.1, and for 2.2 it will move to 9.x. If you want to get a newer base OS, then the shortest path is to help get 2.1 out the door. :-)
If we released 2.0.3 today the only fix would be the PPP DNS issue. Which would be OK, I'd just be worried that another bug would surface in the next few days and we'd just have to turn right back around again and redo the whole release process (which isn't quick/easy) three times in a week (and one with a major Holiday in it, no less).
I'm not sure but this bug seems to be one of the critical ones because it brakes basic functionality. It should be fixed as fast as it could be no matter how it will be named 2.0.2patch1 or 2.0.3. And it would be better if it will available as a standard update.
-
I agree. Jim….I think we should meet up in the coming year and talk about development and dedicated staff to do so.
-
No new major reports have come up over the weekend/holiday, so unless someone finds something quick, we may end up with a 2.0.3 that is just 2.0.2+the PPP DNS fix.
-
Can someone with this DNS+PPP problem try one of the images here:
http://files.nyi.pfsense.org/jimp/foo/shiny/ehrmagerd/They still say 2.0.2 but they have the patched file that fixes DNS.
If someone can confirm it does work as-is, I'll bump the version and start poking at making a new batch.
