Hi, I have installed Suse server (from vicibox.iso downloaded from http://vicibox.org/server/index.html) on Hetzner Cloud. Hetzner machine has static IP address, I have changed network configurations through yast to assign static IP to machine. But now I am unable to ping internet. This is not the problem with DNS as i am unable to ping using IP (8.8.8.8). I was instructed to followed this link (https://wiki.hetzner.de/index.php/Cloud_IP_static/en) by hetzner support. However,It has no direct instructions for Suse.
Previously internet was working fine when i didn't change the network configurations but stopped working due to unknown reasons to i decided to configure manually using yast.

I have also tried configuring it from command line by changing below files.

1- /etc/sysconfig/network/ifcfg-eth0
2- /etc/sysconfig/network/routes
3- /etc/resolv.conf

But failed to properly configure internet. Any help or suggestions are highly appreciated as i am badly stuck.

Regards,
Faizan

What did you put in those three files? I use fixed IP everywhere. In Leap 15.1 have 3 lines in the first, 1 line in the 2nd, and 7 in the 3rd.

What does 'ip a' produce? 'ip route'?

If /etc/udev/rules.d/70-persistent-net.rules exists, what does it contain?

/etc/udev/rules.d/70-persistent-net.rules exists, see attached image for its contents. Attached image also contains output of ip a command.

Below are results of some other commands you asked.

ip router
default via <server_ip> dev eth0

cat /etc/sysconfig/network/ifcfg-eth0
BOOTPROTO='static'
MTU='1500'
STARTMODE='auto'
BROADCAST=''
ETHTOOL_OPTIONS=''
IPADDR='<server_ip>/32'
NAME=''
NETWORK=''
PREFIXLEN='32'
DNS1='213.133.98.98'
DNS2='213.133.99.99'
NETMASK='255.255.255.255'
STARTMODE='auto'
USERCONTROL='no'

cat /etc/sysconfig/network/routes
default 172.31.1.1

cat /etc/resolv.conf
nameserver 213.133.98.98
nameserver 213.133.99.99
nameserver 213.133.100.100

I am also concerned about logs of packets being received, is that normal.

Thank you for help.

Attached Thumbnails

 

I don't understand enough about networking to know how cloud might affect setup, so to me 172.31.1.1 in your routes looks suspicious. I would expect it to be consistent with what you get from 'ip route' (<server_ip>) and/or 'ip a' output (116.203.#.#). Your problem might be better directed to the networking forum, where more network experts would be expected to be enticed by your predicament.

I'll try changing that. If you can you share your configuration files, that might be helpful.