Arch Linux

Llama

Banned

From: St.-Petersburg, Russia

Registered: 2008-03-03

Posts: 1,379

Torrents: OK; pacman -Sy: OK; no pinging

Hi,

I've got a glitch I've never seen before: browser (firefox) won't open any site, while torrents keep on downloading/uploading happily. Sure enough, external hosts won't ping. Rebooting the router (D-Link DSL 2640U) makes no difference.

After pacman -Syu, which again goes without a hitch, the problem's gone; the only network-related package updated is mozilla-common, but what the hell?..

So I'm back in business, but I'd appreciate an explanation .

Allan

Pacman

From: Brisbane, AU

Registered: 2007-06-09

Posts: 11,387

Website

Re: Torrents: OK; pacman -Sy: OK; no pinging

Just to confuse you more, the only change in mozilla-common was to add this message on install ""relogin or source /etc/profile.d/mozilla-common.sh""

---

PGP Key: F99FFE0FEAE999BD

Llama

Banned

From: St.-Petersburg, Russia

Registered: 2008-03-03

Posts: 1,379

Re: Torrents: OK; pacman -Sy: OK; no pinging

Could it be some daemon or whatever restarting? Pacman output shows

relogin or source /etc/profile.d/mozilla-common.sh

...

Ah, sorry, it's the "added message" ... Anything behind it?

Last edited by Llama (2009-03-18 06:29:07)

Dieter@be

Forum Fellow

From: Belgium

Registered: 2006-11-05

Posts: 2,001

Website

Re: Torrents: OK; pacman -Sy: OK; no pinging

Note that firefox caches dns (and probably other things).  It's unreliable to test networks.
It seems to me like your dns setup is broken. (once your torrent client has resolved the hostname(s) it needs, it can keep running).

Here are some things you can use to test:
ethtool/mii-tool: ethernet up?
ifconfig: IP up?
route / ping <name of ip>: do you have routes to your lan and/or external network?
nslookup / dig <dns>: does dns resolving work?
curl -I http://hostname : test http

---

< Daenyth> and he works prolifically
4 8 15 16 23 42

ybotspawn

Member

From: Oz

Registered: 2008-04-06

Posts: 140

Re: Torrents: OK; pacman -Sy: OK; no pinging

can you list the contents of your /etc/resolv.conf file?  is there anything there?  Try pinging the addresses in there... no luck?  Go into your etc/rc.conf file and find your gateway... ping that ... any luck? yes or no?  Can you access your router? Can you verify the addresses in your resolv.conf file to the dns addresses in the router?

---

"As long as people are going to call you a lunatic anyway,
why not get the benefit of it? It liberates you from convention. "

Llama

Banned

From: St.-Petersburg, Russia

Registered: 2008-03-03

Posts: 1,379

Re: Torrents: OK; pacman -Sy: OK; no pinging

can you list the contents of your /etc/resolv.conf file?  is there anything there?  Try pinging the addresses in there... no luck?  Go into your etc/rc.conf file and find your gateway... ping that ... any luck? yes or no?  Can you access your router? Can you verify the addresses in your resolv.conf file to the dns addresses in the router?

/etc/resolv.conf

# Generated by dhcpcd from eth0
# /etc/resolv.conf.head can replace this line
nameserver 192.168.1.1
# /etc/resolv.conf.tail can replace this line

/etc/hosts:

#
# /etc/hosts: static lookup table for host names
#

#<ip-address>   <hostname.domain.org>   <hostname>
127.0.0.1               localhost.localdomain   localhost
192.168.1.2               stovepipe.localdomain stovepipe
192.168.1.3               rimfire.localdomain rimfire

# End of file

Strictly speaking, I have no right to hardcode IP addresses like this using DHCP, but so far no trouble experienced: the router seems to remember. Things like

[stovepipe]$ ping -c 3 rimfire

go without a hitch.

The trouble's gone; all I can remember with any certainty is that the router's been accessible at all times .