Persistent nameserver

[gunnerjoe]

Hi all,

I have PC-BSD 1.4 installed on a Dell D810 laptop dual boot with windows. Install, setup and upgrade was a breeze.

PC-BSD was working fine at home with my DHCP Comcast cable broadband connection. Getting the IP from my Linksys router through "wired" ethernet.

I then took the laptop back to work and was using DHCP through work and it was working fine, (Updates don't work through Proxy, but that's a different problem).

The problem I have now is back at home I keep getting the work NAMESERVERS showing up in the /etc/resolv.conf file and if I manually update that file with the opendns (http://opendns.com/) servers, or the Comcast DNS server the networking will work for a while then the work NAMESERVERS will show up again and networking outside my 192.168 network will not work, i.e google.com etc.

What file is holding the old NAMESERVERS and how do I clear this out.

Thanks,

Joe

[Solarin]

Try removing your leases file:

rm -f /var/db/dhclient.leases.*

[gunnerjoe]

That worked for couple minutes, then networking out side the 192.168.1 network just stops. Well I have been trying to fix this for hours, finally I just backed up the pbi files I downloaded, dropped in the 1.4 install disk and did a fresh install, reloaded the pbi files, reboot install gag boot loader and I'm back up in less than an hour.

DHCP is great right up to the point where it stops working, then not so much :)

Thanks,

Joe

[peispud]

I can confirm the same problem in both DBSD and PC_BSD on both Dlink and Linksys ethernet cards using DHCP - which is weird because usually BSD systems give me better network performance . My problem is simply that the proper default gateway is not being detected and the network has to be manually restarted every couple of minutes . The same card works on my other installs and with other live cds , so it has to be a FreeBSD bug .
Man , with the amount of carping I'm doing lately , the admins should change my user picture to Oscar the grouch . :(

[Solarin]

If you believe it really is a FreeBSD bug, try reporting to the FreeBSD bug tracker:

http://www.freebsd.org/support.html#gnats

[peispud]

http://support.daemonnews.org/viewtopic.php?t=444

What do you think ? Could this be a simple firewall problem ?

[gunnerjoe]

Wish I could test that. In the beginning my DHCP was working fine, took it back to work plugged it in to DHCP network there and worked fine, brought it back home and it went downhill at that point. I have since reloaded and it works fine now :) I did save that page about the firewall for future reference.

Joe