On Wednesday 22 November 2006 10:07, David Geiger wrote: > Nov 22 19:51:49 blizzmo dhclient: receive_packet failed on eth1: Network is > down > Nov 22 19:51:49 blizzmo dhclient: caught deadly SIGTERM > Nov 22 19:51:49 blizzmo dhclient: could not restore resolv.conf: No such > file or directory > Nov 22 19:51:50 blizzmo dhclient: DHCPRELEASE on eth1 to 192.168.0.254 port > 67 Nov 22 19:51:50 blizzmo dhclient: send_packet: Network is unreachable > Nov 22 19:51:50 blizzmo dhclient: send_packet: please consult README file > regarding broadcast address. > Nov 22 19:51:52 blizzmo kernel: ADDRCONF(NETDEV_UP): eth1: link is not > ready
I often have the same problem with something like Skype on totally different hardware than yours. In my case it locks up the wireless router, and nobody can connect. Also ktorrent thru the router (either hardwired to it or via wireless) is dramatically slower than directly connected to the net. I did some research and found that some routers (mine was an early netgear) do not have a a very large table in their router portion and are easily swamped by things that take many many connections (like bittorrent or skype). When I need a torrent, I get it from a machine directly conntcted to the net, bypassing the cheap router. -- _____________________________________ John Andersen
pgpbo3ZnpUCP8.pgp
Description: PGP signature
