Had something strange happen. Didn’t touch the network settings for a long time and no need to. But tried connecting the the Internet and in Firefox it said it couldn’t find www.yahoo.com and to try again. Also had problems checking for email saying it couldn’t find the server. Checked the router, checked the wires, and checked the idiot lights on the router and NIC and all was supposed to be. Tried pinging the machine next to me. Rebooted the machine and the same thing. The only thing I could see what changed is put on some maintenance very recently.
So I found a couple of commands to try:
ifconfig eth0 192.168.1.9
route add -net 0.0.0.0 netmask 0.0.0.0 gw 192.168.1.254
The address was different than what this machine is supposed to have.
After these commands no problem!
I then changed the address on the first line to what this machine should have and entered it Again no problem.
Tomorrow I will reboot and see if things fall apart. If so, I have the commands to enter to get things back working.
Since you didn’t capture and post information when your system wasn’t working, it’s kind of hard to speculate what the problem was before.
If you experience the problem again…
If you run a test you think is relevant (like pinging a neighboring machine, DG or beyond by name or IP address), state the result and possibly post the result. Don’t just say you ran a test and don’t say what the result was.
Very generally, based on what you describe it sounds like <maybe> your machine might not have had a working network configuration, but what specifically will remain a mystery because of your incomplete info. Maybe there is a rogue DHCP on your network? Maybe your DHCP lease expired, wasn’t renewed and another machine was issued that IP address? Who knows?
On 2014-03-30 06:36, deano ferrari wrote:
> I assume you are using ‘Traditional ifup’ (rather than Network Manager)
> for controlling your interfaces? Your output shows no address assigned
> to eth0.
That is precisely what happens with the reported bug that I mentioned.
And the status is:
network.service - LSB: Configure network interfaces and set up routing
Loaded: loaded (/usr/lib/systemd/system/network.service; enabled)
Active: active (exited) since Sun 2014-03-30 18:54:41 EDT; 1min 25s ago
Process: 510 ExecStart=/etc/init.d/network start (code=exited, status=0/SUCCESS)
Main PID: 510 (code=exited, status=0/SUCCESS)
└─961 /sbin/ifplugd -i eth0 -f -I -b
Mar 30 18:54:39 scott1 ifplugd(eth0): Initialization complete, link beat not detected.
Mar 30 18:54:40 scott1 network: eth0 device: Realtek Semiconductor Co., Ltd. RTL8111/8168/
Mar 30 18:54:40 scott1 network: eth0 ifplugd is running
Mar 30 18:54:41 scott1 network: eth0 no cable connected
Mar 30 18:54:41 scott1 network: eth0 is up
Mar 30 18:54:41 scott1 network: …doneSetting up service network . . . . . . . …done
Mar 30 18:54:41 scott1 systemd: Started LSB: Configure network interfaces and set up routing.
Mar 30 18:54:42 scott1 ifplugd(eth0): Link beat detected.
Mar 30 18:54:43 scott1 ifplugd(eth0): Executing ‘/etc/ifplugd/ifplugd.action eth0 up’.
Mar 30 18:54:43 scott1 ifplugd(eth0): Program executed successfully.
Hint: Some lines were ellipsized, use -l to show in full.
The network manager is only really useful if your are changing network environments frequently. With a desktop and a single network, using ifup is fine. BTW, I note you are using a static address, rather than dhcp. (As long as 192.168.1.1 is not your gateway address.)
I have tried installing 13.1 and 13.2 beta. Both have no network connection and advise that Network Manager is not running. I looked in YAST Network Devices, Network Services and found my eth0 link. Opened it up in Edit and found that the bullet choice “wicked” was selected. I changed this to “Network Manager” and every thing now works. Hope this helps somebody else get their network running.