Lost Network (Internet) Connection Overnight on Slackware 14
Hey. I'm running Slackware 14 on a desktop machine. I installed it about a month ago. I've had no problems connecting to the network/internet, until today.
I'm a relative newbie and know little about networking. My box is connected, via cable, to a switch, which is connected to a wifi router, which is connected to a cable modem. I run three machines off of the switch. The 2 other machines are connected and running as they should be. I booted my Slackware machine today and found I couldn't connect to the internet. As I mentioned, this has never been a problem. I thought it had to do something with changing of the clocks, so I changed the machine time by one hour and rebooted. Still no connection. Here's the message about my network interface during the boot process: Code:
Polling for DHCP server on interface eth0: Code:
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 Code:
[ 10.596574] b44 ssb0:0: eth0: Broadcom 44xx/47xx 10/100 PCI ethernet driver 00:0c:6e:3a:ec:96 Thanks... |
You are not getting an IP address from your DHCP server.
How did you configure the eth0 the first time? Did you use the script as root, netconfig ? Are you using WICD or Network Manager? Have a look at what ever you used, and see if you can see what has changed. Netconfig as root, is very easy to use. You can get a lot more information on network config in this document. -->http://docs.slackware.com/slackware:...e_your_network Hope this helps. |
I forgot to mention my initial configuration. I used netconfig during installation. It's set up to receive an ip address via DHCP. I also set up a hostname and domain. But that was it. It was, essentially, plug and play.
I made rc.networkmanager executable today. I've the associated widget on my KDE desktop. It lists 'Wired connection 1.' |
You probably already tried this, but, what happens if you restart your network immediately after booting and receiving those errors?
Occasionally my pc displays connection errors on boot too, however, a /etc/rc.d/rc.inet1 restart resolves the problem immediately. Also back when I was using Debian I sometimes had to run dhclient to get an IP address. Never had to do so in Slackware, but maybe it's worth a try. |
It turns out, the issue originated with my wifi router. It was limited to leasing a small number of ip addresses and I went over the limit this weekend. I changed the value and the Slack box is working fine. Thanks for the suggestions.
|
All times are GMT -5. The time now is 12:25 AM. |