DNS server from pppoe does not work with 2.0.2

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.

jimp

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.

jimp

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.

ptt

Just updated, and seems to be OK (i can get / use DNS's from PPPoE) ;D

From:


2.0.2-RELEASE (amd64)
built on Fri Dec 7 22:39:43 EST 2012
FreeBSD 8.1-RELEASE-p13

To:


2.0.2-RELEASE (amd64)
built on Wed Dec 26 09:20:23 EST 2012
FreeBSD 8.1-RELEASE-p13

Anything else i can do to help ? just let me know ;)

Gertjan

Hi all.

Had the same issue here (France, using pppoe on WAN, ADSL modem), had some initial portal-page problems (on OPT1), which winded up to be the issue of this thread.
The DNS servers weren't collected anymore from my pppoe connection.

The patch that was supplied on the first page of this thread worked very well :
Connection pppoe down:

[2.0.2-RELEASE][admin@pfsense.brithotelfumel]/root(3): cat /etc/resolv.conf
domain brithotelfumel
nameserver 127.0.0.1

I activated the connection, and:

[2.0.2-RELEASE][admin@pfsense.brithotelfumel]/root(4): cat /etc/resolv.conf
domain brithotelfumel
nameserver 127.0.0.1
nameserver 81.253.149.9
nameserver 80.10.246.3

The 2 name servers are my usual ISP DNS servers.

After work I'll apply " http://files.nyi.pfsense.org/jimp/foo/shiny/ehrmagerd/ " to confirm if it is ok.

But: no need to hurry for a 2.0.3, this issue took me a couple of minutes to understand, found it on this forum, the patch worked.

edit: I found also a recap of the problem here: http://blog.pfsense.org/?p=676

timur_dav

@jimp:

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.

NanoBSD i386 image worked for me.

periko

hahaha yea is danger, I had to drive to 2 locations for this issue after the upgrade from 2.0.1 to 2.0.2.
Just add my ISP dns and done.
Right now they back online, not a big issue just more miles to my car.
Thanks!!!

slu

@periko:

Right now they back online, not a big issue just more miles to my car.

Find it out before I have to drive 200 miles 8)

bennyc

@ jimp: I stumbled on this thread as I also encountered the DNS problem after upgrading from 2.0.1 to 2.0.2. Upgraded my system with non-signed image from your site (pfSense-2.0.2-RELEASE-4g-i386-nanobsd-upgrade-20121226-0919.img.gz), seems to work again without any other modifications done. 2 thumbs up for the fix! Thanks…