Stefan, I checked the routingtable and therewas something strange about it. I had configured Routing with YAST2. and specified a netmask: 0.0.0.0. But this resulted in the routing table as shown below (netmask 255.255.255.255): dagobert:/home/Bert # netstat -rn Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 0.0.0.0 192.168.43.10 255.255.255.255 UGH 0 0 0 eth1 192.168.43.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 192.168.43.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 0.0.0.0 192.168.43.10 0.0.0.0 UG 0 0 0 eth0 -------------------------------- In fact it did not matter if I filled-in 0.0.0.0 or 255.255.255.255, it gave the same result in the routing table with netstat. I think this is a bug in YAST2 ?/! So I deleted the Default-GW cfg for eth1 in YAST2: dagobert:/home/Bert # netstat -rn Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 192.168.43.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 192.168.43.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 0.0.0.0 192.168.43.10 0.0.0.0 UG 0 0 0 eth0 -------------------------------- .... and put it in via the netstat cmd, as you mentionned. dagobert:/home/Bert # route add default gw 192.168.43.10 dev eth1 -------------------------------- This resulted in the following routing table: dagobert:/home/Bert # netstat -rn Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 192.168.43.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 192.168.43.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 0.0.0.0 192.168.43.10 0.0.0.0 UG 0 0 0 eth1 0.0.0.0 192.168.43.10 0.0.0.0 UG 0 0 0 eth0 -------------------------------- And this looks good. But when I try to ping the DGW, it does not answer. dagobert:/home/Bert # ping 192.168.43.10 PING 192.168.43.10 (192.168.43.10) 56(84) bytes of data. From 192.168.43.61: icmp_seq=4 Destination Host Unreachable From 192.168.43.61 icmp_seq=4 Destination Host Unreachable Hopefully you have any idees? Regards, Bert