Difference in network access

I am using two computers. One is a laptop working under Leap 13. I access the internet via WLAN and everything works, e.g.this message. The other one is an old Compaq workstation connected to the same router via a LAN cable. 13 running Leap 15.1. I cannot access the network from the latter machine. I have checked the cable and the network settings. They seem alright. However, I cannot even do a simple ping. The response is ‘network unavailable’.

I’d appreciate any idea on what I could do or check further.

BG

The standard way of checking such things from the software side is:

You check from bottom to top:

  1. Is the NIC up with an IP address?
    
ip addr
  1. Can you connect to another system on your LAN?
    
ping -c1 <IP-address of your router>

(I hope you know that address)

  1. Do you have a default route to the Internet?
    
ip route
  1. Can you connect to a system on the internet?
    
ping -c1 195.135.221.161

and/or

ping -c1 2001:67c:2178:8::161
  1. Can you resolve host/domain names?
    
ping -c1 forums.opensuse.org

Take care. As soon a one step fails, that must be resolved first. It is useless to go to the next step before it is resolved.

So start with 1. and do not hesitate to post the output here to get help on the interpretation.

And of course I assume you are aware of the fact that 15.1 is end of life (since 2021-01-31), the more so for 13.1 (since 2016-02-03) that was not even called Leap :wink:

Further to Henk’s advice, also let us know which network management framework you are using. If not sure, the following command will help determine if NetworkManager or wicked is in use…

sudo systemctl status network

I checked from bottom to top. In order to make things clearer I start with each command and quote the results thereafter.

**ping -c1 forums.opensuse.org: ‘name or service unknown’

ping -c1 195.135.221.161: ‘connect: network unreachable’

ip route: ** **192.168.0.0./24 dev eth0 proto kernel scope link src 192.168.0.99’

ping -c1 192.168.2.1: ‘connect: netork unreachable’

ip addr:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether a0:48:1c:77:b1:13 brd ff:ff:ff:ff:ff:ff
inet 192.168.0.99/24 brd 192.168.0.255 scope global eth0
valid_lft forever preferred_lft forever
**
systemctl status network:

● w**icked.service - wicked managed network interfaces
Loaded: loaded (/usr/lib/systemd/system/wicked.service; enabled; vendor preset: disa>
Active: active (exited) since Fri 2021-04-23 16:26:41 CEST; 1min 38s ago
Main PID: 973 (code=exited, status=0/SUCCESS)
Tasks: 0 (limit: 4915)
CGroup: /system.slice/wicked.service

**I assume that I messed up the network addresses. I hope we can sort it out.

Bernd

If this is really the only output (which is impossible to say as you just show some random line without showing full command and its output) then default gateway is missing, so your system can only access directly connected addresses.

Your whole post is a bit upside down. The ip addr should come first. It shows that eth0 is up and has 192.168.0.99 as IP address and 255.255.255.0 as bitmask. Which means that your network is 192.169.0.*

Next is the ping to your router. You seem to think that your router is 192.168.2.1, which is in 192.168.2.* network and thus is incorrect as your router address.

All the rest (as I said before ) is useless and time spoiing efforts.

So either you have the wrong IP address in your system, or you have another router then you think.

Where did you get that IP address 192.168.2.99 from? From a DHCP server? Fixed coded?

I resubmit the result of the commands with CODE. Hope that you now can read it. Bernd

          Directory: /home/bernd
/home/bernd> ping -c1 forums.opensuse.org
ping: forums.opensuse.org: Der Name oder der Dienst ist nicht bekannt
/home/bernd> ping -c1 195.135.221.161
connect: Das Netzwerk ist nicht erreichbar
/home/bernd> ip route
192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.99 
/home/bernd> ping -c1 192.168.2.1
connect: Das Netzwerk ist nicht erreichbar
/home/bernd> ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether a0:48:1c:77:b1:13 brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.99/24 brd 192.168.0.255 scope global eth0
       valid_lft forever preferred_lft forever
/home/bernd> 

Please re-read post #2. It asks you to do (and post) output in a sequence. It also says that when there is a problem showing,** it is useless to go on with the next command**, the problem showing must first be resolved.

In post #4 you tried to show the results.

In post #6, I already hinted that you did it last command first and thus that I had to read from bottom to top :(.

I also explained that what you show last (and what should have been first) is showing that the NIC is up and has an IP address, OK so far.

I also explained that what should have been the second command, the ping to the router, is not finding the router. So from there on we have to find out why not.

I also explained, again, in post #6 that doing the other commands is waste of time, also for us who have to skip all the useless text. And now you again start with posting ping to opensuse.forums.org, which I said is useless.

I also, in post #6, discussed the ping -c1 192.168.2.1 that says that the network is unreachable. This must be solved first. And I also told you that 192.168.2.1 is not in the same network as 192.168.0.99/24 and thus can not be your router, or your system has got the wrong IP address. Then I asked how the system got that IP address. You did not answer that. The result is that we are at the same point as yesterday ~18:00 hours with not one bit more of information. :frowning:

========================

Btw, I see you have a German language system. While I can understand what it says, it would be a service to others here when you would precede all your commands with LANG=C, like

LANG=C ping -c1 192.168.2.1

/home/bernd> ip route
192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.99
/home/bernd> ping -c1 192.168.2.1
connect: Das Netzwerk ist nicht erreichbar

As said, better is to show:

LANG=C ping -c1 192.168.0.1

OK, I understand and reset our system to English. Please let me know if I should repeat the commands previously suggested and in what order. Here are the results of the ping that you mentioned.

  Directory: /home/bernd
/home/bernd> ping -c1 192.168.2.1
connect: Network is unreachable
/home/bernd>    

That is NOT what we asked. We did NOT ask to set your system to English. When you want to do that, that is complete your own choice. We only asked to precede your commands with LANG=C. Nothing more, nothing less.

And we saw that ping already two times. Why do you not answer questions???

You are wasting our time.

This is really getting difficult. I asked you how your system got it’s IP address. Did you provide that yourself in a configuraion? Does the system use DHCP? Please, please , please give an answer. That is when you want this solved!

Also I told you there is a discrepancy between your IP address and what you use as router IP address. @Sauerland suggested that your router address might not be 192,168.2.1, but 192,168.0.1. But again, you do not read carefully and you post a ping 192.168.2.1 (what we already saw two times!), but not

LANG=C ping -c1 192.168.0.1

Can’t you read and type what you see? Can’t you copy/paste what text is there?

problem solved with the aid of the Stuttgart Linux users group. The malfunction resulted from an error in the routing information.
Thread closed BG