Static IP DNS issues.

rathel · 2010-12-17 14:16:49

Some websites load just fine like anything from Google, but others like lifehacker.com fails to load. I am using Netcfg to connect to the network.
My netcfg profile config:

CONNECTION='ethernet'
DESCRIPTION='A basic static ethernet connection using iproute'
INTERFACE='eth0'
IP='static'
ADDR='192.168.0.123'
GATEWAY='192.168.0.1'
DNS1=('208.67.222.222')
DNS2=('208.67.220.220')

My /etc/resolv.conf:

nameserver 208.67.222.222
nameserver 208.67.220.220

I can recall everything was working the way it should, until I rebooted.

Every website loads just fine if I use DHCP and using resolve.conf.head to set DNS.

fukawi2 · 2010-12-18 00:48:50

rathel wrote:

Some websites load just fine like anything from Google, but others like lifehacker.com fails to load. I am using Netcfg to connect to the network.

What is the actual error you get?
Can you ping the sites that "fail to load"?
Have you tried other DNS servers such as Google (8.8.8.8) instead of OpenDNS?

rathel · 2010-12-18 00:58:31

If I use Opera and I wait long enough I finally get a "Connection closed by remote server" error but usually the browsers just show them loading indefinitely.

Yes I have tried Googles DNS and the ones from http://opennicproject.org/ all with the same results.

fukawi2 · 2010-12-19 10:17:37

fukawi2 wrote:

Can you ping the sites that "fail to load"?

rathel · 2010-12-19 14:29:28

fukawi2 wrote:

fukawi2 wrote:
Can you ping the sites that "fail to load"?

Yes.

But odd, now it seems to be working...

rathel · 2010-12-21 07:51:44

Geat, now it's back to not working.. lol

fukawi2 · 2010-12-21 09:46:01

rathel wrote:

fukawi2 wrote:
fukawi2 wrote:
Can you ping the sites that "fail to load"?
Yes.

So it seems it's not a DNS issue since you are able to resolve the hostname while not being able to load the site.

Try this (as root) next time it's broken:

tcptraceroute -p80 broken-site.com

(I just noticed that tcptraceroute has been moved from [extra] to AUR. I've adopted it now)

rathel · 2010-12-21 13:25:23

# tcptraceroute -p80 netflix.com
Selected device eth0, address 192.168.0.123, port 80 for outgoing packets
Tracing the path to netflix.com (208.75.79.17) on TCP port 80 (http), 30 hops max
 1  192.168.0.1  1.948 ms  1.874 ms  1.846 ms
 2  hlrn-dsl-gw45-237.hlrn.qwest.net (207.225.112.237)  103.337 ms  104.791 ms  115.495 ms
 3  hlrn-agw1.inet.qwest.net (71.217.189.97)  115.178 ms  115.436 ms  109.714 ms
 4  svl-edge-20.inet.qwest.net (67.14.12.125)  95.267 ms  104.894 ms  81.322 ms
 5  63.145.225.58  119.324 ms  80.927 ms  80.786 ms
 6  xe-2-3-0-954.jnrt-edge01.sv1.netflix.com (69.53.225.25)  82.249 ms  80.738 ms  80.927 ms
 7  te1-7.csrt-agg01.dc2.prod.netflix.com (69.53.230.230)  81.466 ms  81.869 ms  82.092 ms
 8  www.dc2.netflix.com (208.75.79.17) [open]  81.201 ms  82.023 ms  82.691 ms

And yet netflix.com won't load in browser.

Could my second router be a cause? It should be completely transparent acting only as a bridge.

fukawi2 · 2010-12-21 22:55:26

Well that shows that Port 80 traffic is going right through correctly to netflix.com so doesn't appear to be a routing or firewall issue.

Have you tried different browsers?
Do you use a proxy?

rathel · 2010-12-22 00:56:20

fukawi2 wrote:

Have you tried different browsers?

Yes.. lol I even installed some I have no intention on using other than figuring out this issue.

fukawi2 wrote:

Do you use a proxy?

No.

fukawi2 · 2010-12-22 11:54:31

I'm sh!t out of ideas then

rathel · 2010-12-22 14:16:45

It seems to work again whenever I change any router setting and let the router restart itself with the new settings.. And it'll probably stop working anytime.

w0mbatharcos · 2010-12-23 08:21:29

Same problem with my Arch too as rathel. Have issues only with wireless connections, when i'm on wired network, everything works fine.
Some sites (1-2 only, for example, archlinux.org does not) work without problem. I tried OpenDNS and 8.8.8.8 too, without any change.
It's strange, because I use Arch for about a year, and never experienced such problem, only after my last fresh install (new HDD) last week.
I gave a shot for ubuntu (and archbang), to see, if there's any change, but it's the same issue there.
I installed wicd, but the same results, only wired net works, wireless has a connection, but no data transfer.

I'm in dual-boot with WinXP, where wifi works without a glitch, so I don't think it's my networks fault.

Any ideas? I want my Arch back!

w0mbatharcos · 2011-01-04 14:15:17

Any suggestions maybe?
I'm kind of hopeless here. When I set up the network manually

1. ifconfig wlan0 up
2. wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf -B
3. dhcpcd wlan0

I get the network working, iwconfig wlan0 shows, that I'm connected to my router, I got an IP. But when I ping google, I get pakage losses. Some times 33%,or maybe 66%.
If I use pacman, it acts weird too. I do a pacman -Syu, and it can't connect to the choosen mirrors. I say OK, I uncomment some other servers, maybe it helps. The result: maybe it works, maybe not. Sometimes it grabs a package, and downloads it (if it starts it, it always finishes, and it's working on good speed too) but most of the time it says, that it has some FTP-error, or the connection has been timed out. Ten seconds after that, I retry, and the same server works, pacman pulls a package, but with the second, it fails again.
Maybe I'm the noob, but I don't get it.
Sorry if I can't write it down correctly, english isn't my primal.

Thanks

Arch Linux

#1 2010-12-17 14:16:49

Static IP DNS issues.

#2 2010-12-18 00:48:50

Re: Static IP DNS issues.

#3 2010-12-18 00:58:31

Re: Static IP DNS issues.

#4 2010-12-19 10:17:37

Re: Static IP DNS issues.

#5 2010-12-19 14:29:28

Re: Static IP DNS issues.

#6 2010-12-21 07:51:44

Re: Static IP DNS issues.

#7 2010-12-21 09:46:01

Re: Static IP DNS issues.

#8 2010-12-21 13:25:23

Re: Static IP DNS issues.

#9 2010-12-21 22:55:26

Re: Static IP DNS issues.

#10 2010-12-22 00:56:20

Re: Static IP DNS issues.

#11 2010-12-22 11:54:31

Re: Static IP DNS issues.

#12 2010-12-22 14:16:45

Re: Static IP DNS issues.

#13 2010-12-23 08:21:29

Re: Static IP DNS issues.

#14 2011-01-04 14:15:17

Re: Static IP DNS issues.

Board footer