Am Mittwoch, 17. Mai 2006 16:50 schrieb Dominik Klein:
Was sagt /sbin/ip route|grep default
Ich vermute, dass jetzt eth1 (zweite Karte) als device für das default gateway eingetragen ist. Da dort aber das Modem nicht dranhängt, hast du ein Problem.
Stimmt sogar - mit einem winzigen Unterschied ..... Im lauffähigen zustand : :~> /sbin/ip route|grep default default via 192.168.2.1 dev eth0 :~> ping 192.168.2.1 PING 192.168.2.1 (192.168.2.1) 56(84) bytes of data. 64 bytes from 192.168.2.1: icmp_seq=1 ttl=64 time=1.00 ms 64 bytes from 192.168.2.1: icmp_seq=2 ttl=64 time=0.983 ms 64 bytes from 192.168.2.1: icmp_seq=3 ttl=64 time=0.971 ms 64 bytes from 192.168.2.1: icmp_seq=4 ttl=64 time=0.969 ms 64 bytes from 192.168.2.1: icmp_seq=5 ttl=64 time=0.991 ms --- 192.168.2.1 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4016ms rtt min/avg/max/mdev = 0.969/0.983/1.001/0.012 ms :~> ping suse.com PING suse.com (195.135.220.3) 56(84) bytes of data. 64 bytes from turing.suse.de (195.135.220.3): icmp_seq=1 ttl=55 time=63.6 ms 64 bytes from turing.suse.de (195.135.220.3): icmp_seq=2 ttl=55 time=69.4 ms 64 bytes from turing.suse.de (195.135.220.3): icmp_seq=3 ttl=55 time=68.4 ms 64 bytes from turing.suse.de (195.135.220.3): icmp_seq=4 ttl=55 time=73.2 ms 64 bytes from turing.suse.de (195.135.220.3): icmp_seq=5 ttl=55 time=69.2 ms --- suse.com ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4018ms rtt min/avg/max/mdev = 63.612/68.787/73.241/3.097 ms :~> 2 Eth - Karten aktiv , 1 konfiguriert : :~> /sbin/ip route|grep default default via 192.168.2.1 dev eth0 :~> ping 192.168.2.1 PING 192.168.2.1 (192.168.2.1) 56(84) bytes of data. 64 bytes from 192.168.2.1: icmp_seq=1 ttl=64 time=1.98 ms 64 bytes from 192.168.2.1: icmp_seq=2 ttl=64 time=0.961 ms 64 bytes from 192.168.2.1: icmp_seq=3 ttl=64 time=0.951 ms 64 bytes from 192.168.2.1: icmp_seq=4 ttl=64 time=0.956 ms 64 bytes from 192.168.2.1: icmp_seq=5 ttl=64 time=0.962 ms --- 192.168.2.1 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4016ms rtt min/avg/max/mdev = 0.951/1.162/1.980/0.409 ms :~> ping suse.com PING suse.com (195.135.220.3) 56(84) bytes of data. 64 bytes from turing.suse.de (195.135.220.3): icmp_seq=1 ttl=55 time=68.5 ms 64 bytes from turing.suse.de (195.135.220.3): icmp_seq=2 ttl=55 time=69.2 ms 64 bytes from turing.suse.de (195.135.220.3): icmp_seq=3 ttl=55 time=64.3 ms 64 bytes from turing.suse.de (195.135.220.3): icmp_seq=4 ttl=55 time=73.0 ms 64 bytes from turing.suse.de (195.135.220.3): icmp_seq=5 ttl=55 time=69.0 ms --- suse.com ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4015ms rtt min/avg/max/mdev = 64.302/68.859/73.066/2.794 ms :~> Nach der konfig : :~> /sbin/ip route|grep default default via 192.168.2.1 dev eth1 :~> ping 192.168.2.1 PING 192.168.2.1 (192.168.2.1) 56(84) bytes of data. 64 bytes from 192.168.2.1: icmp_seq=1 ttl=64 time=3.98 ms 64 bytes from 192.168.2.1: icmp_seq=2 ttl=64 time=0.995 ms 64 bytes from 192.168.2.1: icmp_seq=3 ttl=64 time=0.996 ms 64 bytes from 192.168.2.1: icmp_seq=4 ttl=64 time=0.977 ms --- 192.168.2.1 ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3014ms rtt min/avg/max/mdev = 0.977/1.738/3.985/1.297 ms jmarco@cpu1:~> ping suse.com [ Abbruch nach 1 Min !!! ] :~>ping 195.135.220.3 [ IP von suse.com oben ] PING 195.135.220.3 (195.135.220.3) 56(84) bytes of data. From 192.168.2.11: icmp_seq=2 Destination Host Unreachable From 192.168.2.11 icmp_seq=2 Destination Host Unreachable From 192.168.2.11 icmp_seq=3 Destination Host Unreachable From 192.168.2.11 icmp_seq=6 Destination Host Unreachable From 192.168.2.11 icmp_seq=7 Destination Host Unreachable --- 195.135.220.3 ping statistics --- 10 packets transmitted, 0 received, +5 errors, 100% packet loss, time 9041ms , pipe 2 ok eth0 + router funtionieren,eth0 + inet nicht ..... also eth1 als verbindung ins internet nehmen ? ( ist ja machbar ) also fix umgesteckt das kabel ... und : :~> ping 192.168.2.1 PING 192.168.2.1 (192.168.2.1) 56(84) bytes of data. --- 192.168.2.1 ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 2013ms :~> Hmmm wenn ich et0 nehme -> nur verbindumg zum Modem ( Router !! ) wenn ich eth1 nehme geht gar nix ( und im Routermodem ist keine Einschränkung für LAN aktiv, nur WLan ist deaktiv )