Eqwatz

[Log in to get rid of this advertisement]

Soho routers will often be on the first line of your resolv.conf file. Even after fixing it--the problem can return on reboot--due to something I think I did during my installation, although I may be wrong.

Close your internet browser first.Carefully look at your resolv.conf file. Make sure that you know the correct addresses for the name-servers at your ISP--there should be a primary and secondary name-server (DNS server). Your Desktop will only read the first two lines of your resolv.conf file. Put the primary DNS server for your ISP on the first line; the secondary DNS server on the second line. Have no more than three lines of text in resolv.conf.

Do not reboot.

Fire up your browser. Does it go fast?If it does: Fix your resolv.conf~ to say the same as the working one and rename it to resolv.conf.keep. The lines: "alias net-pef-10 off" and "alias ipv6 off" go into modprobe.conf--create another file modprobe.conf.local and put them in there also--I think that the .local configuration file will override any thing in the /lib/modules/kernel-name-and-patch-level/ folder-or-directory.

Reboot.If the corrected /etc/resolv.conf gets over-written each reboot: Create /etc/resolv.conf.keep with the correct entries. In /etc/rc.d/rc.local you can put a script which will mv resolv.conf to resolv.conf.bad and cp resolv.conf.keep to resolv.conf and finally rm resolv.conf.bad. . ./etc/rc.d/rc.local is the last script read during the boot-up process. Unless boot-up is threaded and optimized it should be where you do any changes to the stock installation so you can find them (like changing environmental variables.)

Also, if you do anything to a stock installation, you will be really much happier if you keep a log somewhere where you can find it to recreate or reverse any changes you make to the default settings and installations. One on the Hard drive, and one on paper. Don't do as I do and write it down on generic paper legal pads that get lost--or "borrowed and used for something else in the office.

Eqwatz

Oops. I reposted

cybertaz

I know in Suse there is switch in the system config file (I'll find it later, not at my machine right now) that will prevent that from happening.It is something like mod_resolv_conf_dynamic (I think???). I set that to NO and it hasn't been over-written yet.

acummings

My Slack resolv.conf never gets overwritten. 1. It be a static IP and my particular SOHO DSL gateway/firewall/router (it's a 2wire 1701HG) may also have to do with this.

Slack 11 Rocks! I just discovered some more on my particular Slack http www browsing slow issue. So, next, just sharing of what's happened so far.

it's a Slack current that was current until near 7, 8 weeks prior to release of Slack 11 and then I lacked the time to update those the copius changes of those mentioned 8 weeks.

That box is a static 192.168.1.xx IP. I had *manually* added the IP and info of that box to my SOHO dsl modem/firewall/router (a 2wire 1701HG) (AT&T Yahoo DSL).

More info on that box: 2.6.16.20 kernel I had compiled using/adding/changing a base config of one of the official Slack extra or testing kernels.

Its resolv.conf always stays the same, never overwritten it points directly to the 2wire (internet gateway).

My point here is that I just installed Slack 11 on a different box that had not ever been on the 2wire internet gateway; and with this new box's (a static IP box) resolv.conf pointing directly to the 2wire, web browsing with Firefox is blazingly fast nearly all of the time!

I let the 2wire automatically discover this new box. (the 2wire likes to use its arp) (I don't like 2wire using arp but that's another story.)

The differences between these 2 boxes: different 2.6 kernel versions, new box uses Slack 2.6 kernel from /extra -- old box is a compiled 2.6 kernel, differences in firewall (ip tables); old box was manually entered into 2wire -- new box I let it be auto discovered by the 2wire.

I'm simply going to backup my data off of the old box and then format and install Slack 11 on it. I'll also delete it from the 2wire. And then, when Slack 11 is on it up and running, I'll let the 2wire auto discover this box too.

Later on I may experiment with pointing resolv.conf to ISP's name servers. And I also want to try a Linux bridging firewall box in between my 2wire and my small LAN (I don't care that much for that 2wire -- if I knew of better alternative(s) to this 2wire 1701HG I'd do it and dump this 2wire 1701HG) (BTW I'm ready to hear of better alternative(s)

I'm not going to try and figure out just exactly why the old box's www browsing is slow and problematic due to www browsing on Slack 11 on another, new box is working so fast and superbly.

--
Alan.