Network is unreachable

svetter88 · March 29, 2014, 7:45am

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.

Any ideas?

Tomorrow I will reboot and see if things fall apart. If so, I have the commands to enter to get things back working.

hcvv · March 29, 2014, 9:25am

Which version of openSUSE?

svetter88 · March 29, 2014, 10:32pm

It is 13.1

tsu2 · March 29, 2014, 11:22pm

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?

TSU

robin_listas · March 29, 2014, 11:48pm

On 2014-03-29 23:26, tsu2 wrote:
>
> 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.

It could be the recent broken network update problem.

–
Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

svetter88 · March 30, 2014, 5:17am

I can understand your replay but didn’t know how to show results of why it was failing. However rebooted and the network still did not come up and here is the results of some commands issued:

scott1:/home/scott # ifconfig
eth0 Link encap:Ethernet HWaddr 8C:89:A5:10:A0:27
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:29 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2319 (2.2 Kb) TX bytes:0 (0.0 b)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:62 errors:0 dropped:0 overruns:0 frame:0
TX packets:62 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:5811 (5.6 Kb) TX bytes:5811 (5.6 Kb)

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
loopback * 255.0.0.0 U 0 0 0 lo

The results from a ping is: Network unreachable.

Is there some other commands I should be using to show that there is a problem?

deano_ferrari · March 30, 2014, 6:30am

I assume you are using ‘Traditional ifup’ (rather than Network Manager) for controlling your interfaces? Your output shows no address assigned to eth0.

What is defined in /etc/sysconfig/network/ifcfg-eth0?

For reference, I have

BOOTPROTO='dhcp4'
STARTMODE='onboot'
NAME='NetLink BCM5787M Gigabit Ethernet PCI Express'

Let’s see the status of network.service too

systemctl status network.service

robin_listas · March 30, 2014, 11:53pm

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.

Please view this thread:
http://forums.opensuse.org/showthread.php?t=496398

–
Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

svetter88 · March 31, 2014, 1:01am

Yes, using ifup. Thinking about trying the Network Manager. Why switch?

The ifcfg-eth0 is:
BOOTPROTO=‘static’
BROADCAST=’’
ETHTOOL_OPTIONS=’’
IPADDR=‘192.168.1.1/24’
MTU=’’
NAME=‘RTL8111/8168B PCI Express Gigabit Ethernet controller’
NETWORK=’’
REMOTE_IPADDR=’’

STARTMODE=‘ifplugd’
USERCONTROL=‘no’
IFPLUGD_PRIORITY=‘nil’

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)
CGroup: /system.slice/network.service
└─961 /sbin/ifplugd -i eth0 -f -I -b

Mar 30 18:54:39 scott1 ifplugd(eth0)[961]: Initialization complete, link beat not detected.
Mar 30 18:54:40 scott1 network[510]: eth0 device: Realtek Semiconductor Co., Ltd. RTL8111/8168/
Mar 30 18:54:40 scott1 network[510]: eth0 ifplugd is running
Mar 30 18:54:41 scott1 network[510]: eth0 no cable connected
Mar 30 18:54:41 scott1 network[510]: eth0 is up
Mar 30 18:54:41 scott1 network[510]: …doneSetting up service network . . . . . . . …done
Mar 30 18:54:41 scott1 systemd[1]: Started LSB: Configure network interfaces and set up routing.
Mar 30 18:54:42 scott1 ifplugd(eth0)[961]: Link beat detected.
Mar 30 18:54:43 scott1 ifplugd(eth0)[961]: Executing ‘/etc/ifplugd/ifplugd.action eth0 up’.
Mar 30 18:54:43 scott1 ifplugd(eth0)[961]: Program executed successfully.
Hint: Some lines were ellipsized, use -l to show in full.

svetter88 · March 31, 2014, 1:06am

That is precisely what happens with the reported bug that I mentioned.

Please view this thread:
http://forums.opensuse.org/showthread.php?t=496398

–
Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)[/QUOTE]

I have looked at this thread and it does seem to be the problem I am having since I do use the traditional method. Only have one interface card.

Why use the traditional method vs the Network manager?

deano_ferrari · March 31, 2014, 2:04am

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.)

robin_listas · March 31, 2014, 2:03am

On 2014-03-31 01:16, svetter88 wrote:

> I have looked at this thread and it does seem to be the problem I am
> having since I do use the traditional method. Only have one interface
> card.

In my case, I simply changed from “on cable connect” to “on boot”, and
it worked. If not, revert the update…

> Why use the traditional method vs the Network manager?

IMO, I prefer traditional setup if the machine is always on the same
network. If you change networks, like on a laptop, it is easier with
network manager.

–
Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

svetter88 · March 31, 2014, 2:50am

Thank you Carlos!

I will give that a try. And thank you for the reason to use one method vs the other.

Scott

svetter88 · March 31, 2014, 2:53am

Thank you Deano!

Yes, not doing that here. Running a few services that others on the network need hence the static address. 1.1 is not the gateway as that might be a bit of a problem…

Scott

wolfi323 · March 31, 2014, 8:53am

Right.
That update contained a logical error that broke starting the interface “on cable connect”.
Switching to “on boot” should make it work.

A fix has been submitted already, and should be released as online update soon.

svetter88 · April 1, 2014, 4:35am

Super. I will change from “on cable connect”.

wolfi323 · April 7, 2014, 1:27pm

FYI, the fixed “sysconfig-network” update was released today.

So “cable-connect”/“ifplugd” should work now again.

shadders · April 7, 2014, 7:11pm

Hi Wolfi323,

Thanks for the update, much appreciated.

Regards,

Shadders.

spamnchips · April 8, 2014, 6:38pm

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.

wolfi323 · April 8, 2014, 9:09pm

13.2 is not even beta yet. It’s Milestone0.
“wicked” is the new thing for 13.2 that replaces ifup and might still have problems.

But on 13.1 ifup should work just fine, at least for wired ethernet. If a wireless card is detected during installation, NetworkManager should be enabled by default AFAIK.