cannot ping 13.1 system

I hope this is a simple issue. I have a new opensuse13.1 install (hostname, vicksburg). I’ve tweaked my networking and now I cannot connect to this system from the other hosts on my home network, or even get it to respond to a ping. I don’t have any connectivity issues from the 13.1 host to the other systems or the internet, but the other systems cannot connect to it.

Also I’ve disabled my firewall for the time until I get it sorted out. Any ideas on where to start?

/usr/sbin/service sshd status
sshd.service - OpenSSH Daemon
Loaded: loaded (/usr/lib/systemd/system/sshd.service; enabled)
Active: active (running) since Wed 2013-12-25 00:03:36 MST; 56min ago
Process: 19918 ExecStartPre=/usr/sbin/sshd-gen-keys-start (code=exited, status=0/SUCCESS)
Main PID: 19922 (sshd)
CGroup: /system.slice/sshd.service
`-19922 /usr/sbin/sshd -D

Dec 25 00:03:36 vicksburg systemd[1]: Started OpenSSH Daemon.
Dec 25 00:03:36 vicksburg sshd[19922]: Server listening on 0.0.0.0 port 22.
Dec 25 00:03:36 vicksburg sshd[19922]: Server listening on :: port 22.

ifconfig
eth0 Link encap:Ethernet HWaddr 00:21:9B:1C:58:79
inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::221:9bff:fe1c:5879/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:136038 errors:0 dropped:0 overruns:0 frame:0
TX packets:87683 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:159482986 (152.0 Mb) TX bytes:9627742 (9.1 Mb)
Interrupt:20 Memory:fbdc0000-fbde0000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:637 errors:0 dropped:0 overruns:0 frame:0
TX packets:637 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:121982 (119.1 Kb) TX bytes:121982 (119.1 Kb)

** /usr/sbin/service network status**
network.service - LSB: Configure network interfaces and set up routing
Loaded: loaded (/usr/lib/systemd/system/network.service; enabled)
Active: active (exited) since Wed 2013-12-25 00:48:28 MST; 6min ago
Process: 11780 ExecStop=/etc/init.d/network stop (code=exited, status=0/SUCCESS)
Process: 29996 ExecReload=/etc/init.d/network reload (code=exited, status=7)
Process: 12472 ExecStart=/etc/init.d/network start (code=exited, status=0/SUCCESS)

Thanks!
Craig

Please, please, to make your computer texts readable in posts, put CODE tags around them. You get the CODE tags by clicking on the # button in the tool bar of the post editor. And then copy/paste in one sweep the prompt, the command, the output and the next prompt from your terminal window in between the tags.

Thank you.

The general idea to check from your system if it’s network connection functions is:

  • Look if the NIC is up and has a proper IP address, broadcast and mask:
/sbin/ifconfig -a

.

  • Check if you can ping a system (one were you know it answers to ping, probably your router):
ping -c1 <IP-address>

. When you can do this the system can communicate on the LAN. When you, nothwithstanding this, have problems with connections on the LAN, it is either the other system, or a specific service, or a system located firewall.

  • For going outside the LAN (e.g. to the Internet), check your routes:
/sbin/route -n

. Normaly this wil show at least a line with Destination 0.0.0.0 (the default route), Gateway .

  • When you have a proper route to outside, you can check if you can ping a system on the Internet:
ping -c1 130.57.66.6

. Positive? Then you can reach the Internet.

  • But you probably want to reach systems using their domain name instead of using IP addresses. You can check this e.g:
ping -c1 forums.opensuse.org

. When OK your DNS server functions.

When you now have problems e.g. in using SSH in one or the other direction, you should ckeck firewalls, SSH configs, etc. In short hen you must concentrate on the individual services.

The above is step by step aproach I advise when you have networking problems.

Sorry about that!  I'll do better next time!

:slight_smile:

Thanks for the basic outline of checks, especially the route. I’ve rebooted the system and now it’s working. I’m not sure which service needed restarting to undo the mess.

Craig

You are welcome, nice it works.