Arch Linux

sp0rk173

Member

Registered: 2005-11-06

Posts: 8

Network unresponsive after ~12 hours.

Hey.

So i've had this odd problem for the last few months, and now that i'm using arch more than freebsd, it's becoming more and more annoying.  On boot, my network works perfectly.  However, after a few hours it becomes unresponsive (i haven't been able to pin it down to how many hours, but it seems it'll work until i go to bed, then wake up and everything is disconnected).  The network successfully comes back up if i restart it (ie, /etc/rc.d/network restart, and now netcfg2 ethernet since i moved on to netcfg2).  I upgraded to netconfig2 hoping this would solve my problem, but it hasn't.  Has anyone else experienced this?  Any ideas?

Thanks.

tigrmesh

IRC Op

From: Florida, US

Registered: 2007-12-11

Posts: 794

Re: Network unresponsive after ~12 hours.

Have you removed or disabled network from the daemons line in your rc.conf?  See if that helps.

sp0rk173

Member

Registered: 2005-11-06

Posts: 8

Re: Network unresponsive after ~12 hours.

Yup.  my rc.conf follows:

LOCALE="en_US.utf8"
HARDWARECLOCK="UTC"
TIMEZONE="Canada/Pacific"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
MOD_AUTOLOAD="yes"
MOD_BLACKLIST=()
MODULES=(forcedeth slhc snd-mixer-oss snd-pcm-oss snd-hwdep snd-page-alloc snd-pcm 
snd-timer snd snd-hda-intel soundcore fuse)
USELVM="no"
HOSTNAME="xanthor"
NETWORKS=(ethernet)
ROUTES=(!gateway)
DAEMONS=(syslog-ng net-profiles portmap netfs crond dbus xfs.rc hwd gdm sshd)

And again, this problem existed before i made the move to netcfg2, and persists now that i've changed.

sp0rk173

Member

Registered: 2005-11-06

Posts: 8

Re: Network unresponsive after ~12 hours.

still no ideals?

ralvez

Member

From: Canada

Registered: 2005-12-06

Posts: 1,694

Website

Re: Network unresponsive after ~12 hours.

I think that the way to troubleshoot the problem is to check the following when it happens:
1. Check your router. It is working? Can you log in into it and ping websites outside? Can you  ping machines inside the network? etc.
2. From your machine, the one that gets disconnected,try: ping 127.0.0.1 and see if you get a response.

It seems to me that it may be either a hardware or a driver issue.

R.