You are not logged in.
Hi -
network is ok when I reboot computer, all works fine (I have onboard NIC but use a PCI Realtek card).
But after some time the network fails, and I get these messages in dmesg:
Oct 4 18:01:39 domu dhcpcd[2963]: terminating on signal 15
Oct 4 18:01:52 domu dhcpcd[5309]: terminating on signal 2
Oct 4 18:02:33 domu ACPI: Getting cpuindex for acpiid 0x1
Oct 4 18:14:49 domu dhcpcd[3291]: terminating on signal 15
Oct 4 18:14:58 domu dhcpcd[3741]: terminating on signal 2
Oct 4 18:15:38 domu dhcpcd[3801]: terminating on signal 2
Oct 4 18:16:22 domu dhcpcd[3804]: terminating on signal 2
Oct 4 18:17:21 domu dhcpcd[3856]: recvfrom: Network is down
Oct 4 18:18:00 domu ACPI: Getting cpuindex for acpiid 0x1
Oct 4 23:56:33 domu dhcpcd[3292]: terminating on signal 15
Oct 5 07:58:20 domu ACPI: Getting cpuindex for acpiid 0x1
Oct 5 17:32:15 domu dhcpcd[2921]: terminating on signal 15
Oct 5 17:32:57 domu ACPI: Getting cpuindex for acpiid 0x1
then I need to reboot again for it work. It seems like it fails only when I use azureus, could there be a link? if any can help with the problem, is much appreciated!
system: AMD Athlon 64 3000+
DFI lanparty nf3 mainboard
nvidia geforce ti 4400
Realtek NIC (ne2k-pci)
Offline
well, problem has not disappeared - network is constantly dying. It works ok every reboot so I think its not a hardware problem.
the error log this morning says this:
Oct 12 07:46:31 domu ACPI: Getting cpuindex for acpiid 0x1
Oct 12 08:17:29 domu dhcpcd[2920]: terminating on signal 15
Oct 12 08:18:08 domu ACPI: Getting cpuindex for acpiid 0x1
again, the dhcpcd termination but I wonder the acpi message is about - could that be a problem?
any suggestions?, thanks.
Offline
hi all -
bumping this again. The connection is consistent when browsing normal websites etc. I noticed that usually within 30 mins. of starting bittorrent client the connection dies, with messages quoted above. It always seems to be a result of bittorrent activity.
Could it be my ISP (telewest in UK) are killing my connection when they notice I use bittorrent? There's nothing about this on their site...
The weird thing is that everything works! all I have to do is reboot then it's all fine, but if I use bittorrent it dies pretty quick. Does anyone know of ISP's doing this sort of thing? or am I on the wrong track? thanks!
Offline
No clue, but next time this happens try
/etc/rc.d/network restart
as root .
If that restores the connection, atleast you won't have to reboot so often anymore.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Hi -
restarting network don't work, only reboot fix it
there's no response if I do
dhcpcd eth0
I'm really starting to think that my ISP is at fault, since I had a network for more than 24 hours the other day, but it died within 2 hours of starting a torrent.
Offline
I'm really starting to think that my ISP is at fault, since I had a network for more than 24 hours the other day, but it died within 2 hours of starting a torrent.
I doubt it. This is what happens with my network connection also, but it doesn't happen with torrents in Windows XP. And as far as I know, my Finnish ISP doesn't prohibit torrent clients.
I haven't tried other clients than Azureus in Linux since my command line bittorrent ceased functioning. I haven't thought it before, but now that I think of it, it seems to be Azureus-related. I will try with another torrent client, though, and report back.
Offline
Well, now I'm not able to reproduce the problem, and errors.log is empty. I've used both ktorrent and azureus for several hours withouth any problems.
Offline
I decided to upgrade my NIC to an rtl-8139 one (yes, my other NIC is even older) and azureus has been happily seeding for several hours now... seems like that might have fixed it.
Offline