New router killed my server

MasterC · 01-20-2003, 01:07 PM

Hello, this sounds like progress to me!

Pinging 192.168.0.1 I get nothing, a 100% packet loss. I don't know this IP though, it's not my router, or any box. However, I continued...

I pinged 213.130.63.234 and got out! I got a 100% packet return. It pinged there just fine, so I continued...

I pinged www.slackware.com and got "unknown host www.slackware.com"

Which sounds good to me, sounds like something in resolv.conf (even though I have NO networking skills, it just sounds right

) so here's my resolv.conf:

Code:

nameserver 4.2.2.1
nameserver 4.2.2.2
nameserver 4.2.2.3
search dsl-verizon.net

Hmmm, so maybe I just need to add my router's IP in there, and comment out the verizon info (my ISP)?

And I also did the traceroute while I was down, it too returned "unknown host www.linuxquestions.org".

And while I'm up here's what I get from the traceroute:

Code:

masterc@masterc:~$ traceroute www.linuxquestions.org
traceroute to www.linuxquestions.org (64.179.4.146), 30 hops max, 38 byte packets
 1  evrtwa1-ar8-4-65-016-001.evrtwa1.dsl-verizon.net (4.65.16.1)  22.434 ms  21.625 ms  21.942 ms
 2  4.24.255.217 (4.24.255.217)  28.862 ms  21.956 ms  22.364 ms
 3  p7-0.evrtwa1-cr6.bbnplanet.net (4.0.79.129)  22.129 ms  23.127 ms  22.255 ms
 4  p7-0.evrtwa1-br2.bbnplanet.net (4.24.9.125)  23.494 ms  22.212 ms  25.419 ms
 5  so-4-2-0.sttlwa1-hcr2.bbnplanet.net (4.24.6.61)  23.578 ms  22.907 ms  22.941 ms
 6  so-7-0-0.sttlwa1-hcr1.bbnplanet.net (4.24.10.233)  23.207 ms  23.103 ms  23.153 ms
 7  p3-0.sttlwa2-br1.bbnplanet.net (4.24.11.201)  27.834 ms  23.375 ms  23.307 ms
 8  p8-0.snjpca1-br2.bbnplanet.net (4.0.3.230)  40.549 ms  40.895 ms  39.832 ms
 9  p2-0.paix-bi3.bbnplanet.net (4.24.7.38)  40.483 ms  43.802 ms  40.470 ms
10  p5-0.paix-bi1.bbnplanet.net (4.0.3.130)  41.749 ms  40.349 ms  40.739 ms
11  p3-3.xpaix18-globalcenter.bbnplanet.net (4.0.6.46)  44.896 ms  41.316 ms  42.694 ms
12  so-6-0-0-2488M.cr1.PAO2.gblx.net (208.51.224.141)  40.782 ms  41.940 ms  41.040 ms
13  pos5-0-2488M.cr2.BOS1.gblx.net (208.49.59.133)  107.213 ms  106.835 ms  106.770 ms
14  so7-0-0-622m.ar2.BOS1.gblx.net (206.132.247.74)  108.074 ms  107.744 ms  106.777 ms
15  Choice-One.s0-1-3-0.ar2.BOS1.gblx.net (64.215.248.2)  115.268 ms  114.466 ms  114.715 ms
16  tr-5-1007-bflo-shasta.choiceone.net (64.65.210.190)  116.328 ms  118.374 ms  116.558 ms
17  linuxquestions.org (64.179.4.146)  117.199 ms  117.944 ms  117.001 ms
masterc@masterc:~$

And I don't even see my IP in there (4.65.28.150) hmm...

I'm gonna give the editing resolv.conf a run really quick.

Thanks for all your guys' help so far.

Darin · 01-20-2003, 01:13 PM

oh duh!
"Pages (3): [1] 2 3 » Go to first unread post first unread"

now it makes more sense <chuckles>

anyhow, sounds like DHCP works and gives you good DNS then you change to static IP on the fly which probably isn't changing your DNS listing so it would work until reboot. This would mean your pings would look like this after you reboot with a static IP:

ping 192.168.0.1 (sorry replace this with the IP of your router's internal connection)
reply, reply, reply

ping 213.130.63.234
reply, reply, reply

ping www.slackware.com
unable to resolve host

And that your missing DNS resolution (the part of the internet that turns names like www.slackware.com into IP addresses) so it's basically a matter of finding out what DNS servers get assigned when you use DHCP and plugging them into /etc/resolv.conf when you assign a static IP, see my other post. Hint: if resolv.conf has DNS servers when the connection works write them down and then add them in after you reboot with static IP and they are gone.

As far as the traceroute thing, don't bother that was more of an FYI, and you don't see your router in it I'm wrong, but others see the router when they traceroute to you

MasterC · 01-20-2003, 01:13 PM

Well tweaking the resolv.conf didn't seem to make a bit of difference, but I did see something. I check resolv.conf after bootup and it just had:
search example.net

And that was it. I edited before reboot to look like this:

Code:

192.168.1.1
#nameserver 4.2.2.1
#nameserver 4.2.2.2
#nameserver 4.2.2.3
#search dsl-verizon.net

So it was altered at some point if that helps any.

Well, so now I'm stuck again, not sure where to go or what to do, thanks again for the help so far.

Cool

MasterC · 01-20-2003, 01:22 PM

*Networking n00b colors shining through*

So how would 1 go about "catting" resolv.conf and having it use the correct DNS entries? It seems to be dynamically altering the lines in there on each boot, I guess I could change perm's on it to read-only, I just don't know how wise that would be?

Darin · 01-20-2003, 01:24 PM

Yea, the resolv.conf gets that info entered into it via DHCP and then it gets yanked out by the shutdown scripts when you reboot. I't's a little different for me because my ISP connection is a modem with ppp and it doesn't change /etc/resolv.conf directly but stores the DNS settings in /etc/ppp/resolv.conf and links to that somehow.

Basically, boot up with DHCP enabled, copy the settings out of resolv.conf, reboot with static IP and the settings should be gone again but just put them back manually and it should work now, even after reboots.

MasterC · 01-20-2003, 02:20 PM

Woohoo! Check me out, I'm surfing without editing a bunch of files

Thanks again, and you guys ROCK!

Darin, you ever here about Affero? You should check out the existing threads in the "Site Suggestions" section to read about it, and maybe sign up!

Thanks again, and now will you guys keep a look out for a soon to come question on my networking problem?

Just kidding, I thank you very very much.

Cool

Darin · 01-20-2003, 03:04 PM

Hey it's my first day here and already I'm someone's hero woohoo!

Just wait till I start throwing out my iptables questions mouhahahaha.