On Tue, 16 Jan 2007 01:32:58 -0500
Bob McIsaac <[EMAIL PROTECTED]> wrote:
> This is not exactly a question rather it is wrapup for a
> series of questions. I had a tricky, confusing problem
> getting FreeBSD on the net but I was able to solve it
> with help from this list.. Ian Smith in particular.
> The DHCP lease from my ISP set the nameserver
> address as being 192.168.1.254, the IP of some box
> which connects me to to net. Correct me if wrong,
> but whois would not reveal a nameserver IP in this
> form for a net host.
> Linux accepted this but FreeBSD-6.1 had 10 second
> delays in TCP connects for mail and web pages.
> This does not imply a problem with BSD. It
> probably implies that Linux is more tolerant of
> loosely configured web services. But in the
> world of security it's "casual configuration
> considered harmful".
No, you have misunderstood the problem.
192.168.1.254 is presumably the address of your NAT router. It's
using its own DHCP server to give you its own address as a nameserver
because it's running a DNS proxy.
My D-Link ADSL-router has a similar problem, its DNS proxy was very
unreliable with FreeBSD, much worse than 10 second delays, many
lookups didn't resolve at all. Disabling IPv6 did help speed things
up, but didn't cure the problem entirely.
> I spent many hours reading and testing before
> hitting on a solution in dhclient.conf.
If you have a fixed location (i.e. it's not a laptop that connects
elsewhere), it's probably better and easier to avoid DHCP altogether,
since you are not getting any dynamic configuration from it.
I setup my desktop PC like this:
ifconfig_vr0="inet 192.168.1.201 netmask 255.255.255.0"
this gives me a fixed private ip address, instead of one that depends
on what else is plugged into the router. The address is reserved in
email@example.com mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"