DNS server from pppoe does not work with 2.0.2

slu

Alexander, did you have one or more pppoe connections?

jimp

Do you have anything showing up in /var/etc/nameserver_* ?

slu

[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.

Bentrax

@slu: only one connection

@jimp: I didn't look in that file, I only locked at the interface status page and there was only 127.0.0.1 the local host as DNS. May the content of that file be different, then I will switch slices again and have a look…

jimp

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]

Bentrax

Sorry not enough time atm to play around… maybe slu can test...

slu

@jimp:

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?

jimp

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.

slu

@jimp:

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.

jimp

Only if you have not manually defined DNS servers.

Bentrax

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…

jimp

Or just define custom DNS servers (like 8.8.8.8 8.8.4.4) and don't use the ones from PPPoE.

chpalmer

Yep- I did the upgrade at my office remotely and had no problems. I had defined dns so did not run into this.

timur_dav

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

shenrich

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

jimp

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 :-)

Supermule

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?

jimp

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).

timur_dav

@jimp:

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.

Supermule

I agree. Jim….I think we should meet up in the coming year and talk about development and dedicated staff to do so.