Daniel Lord schrieb am Thu, 12 Feb 2004 19:47:28 +0100: DSL und Router will nicht
Hallo Joerg,
schick mal bitte die Ausgaben der folgenden Kommandos an die Liste.
mii-tool route -n ifconfig ping -c2 <interne ip deines routers> cat /etc/hosts cat /etc/resolv.conf
Greetings Daniel -- "Zwei Dinge halte ich für unendlich: die menschliche Dummheit und das Universum. Bei Letzterem bin ich mir aber noch nicht sicher." -- Albert Einstein
Hallo, Daniel, hmm, hoffe, daß die Signatur nicht allzu sehr zutrifft... im folgenden die Ausgaben, Sorry für lange Zeilen Client (alte DLD-4 Version, da Testrechner. Routing lief aber tadellos über ISDN-Router, Kernel 2.0.36 IP 192.168.0.4=pc586) mii-tool: gibts hier nicht (ist eine 100 MBit-Realtek-Karte, link ist o.k.) route -n: Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 1 lo 0.0.0.0 192.168.0.2 0.0.0.0 UG 0 0 0 eth0 ifconfig: lo Link encap:Local Loopback inet addr:127.0.0.1 Bcast:127.255.255.255 Mask:255.0.0.0 UP BROADCAST LOOPBACK RUNNING MTU:3584 Metric:1 RX packets:2 errors:0 dropped:0 overruns:0 frame:0 TX packets:2 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 eth0 Link encap:Ethernet HWaddr 00:48:54:50:75:85 inet addr:192.168.0.4 Bcast:192.168.0.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:58 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 Interrupt:11 Base address:0x6000 PING 192.168.0.2 (192.168.0.2): 56 data bytes 64 bytes from 192.168.0.2: icmp_seq=0 ttl=64 time=0.3 ms 64 bytes from 192.168.0.2: icmp_seq=1 ttl=64 time=0.2 ms --- 192.168.0.2 ping statistics --- 2 packets transmitted, 2 packets received, 0% packet loss round-trip min/avg/max = 0.2/0.2/0.3 ms /etc/hosts: 127.0.0.1 pc586.lan.vfg pc586 localhost 192.168.0.1 linux.lan.vfg linux 192.168.0.2 pcedv.lan.vfg pcedv 192.168.0.4 pc586.lan.vfg pc586 /etc/resolv.conf search lan.vfg nameserver 192.168.0.2 (hier hatte ich auch schon einen "echten" t-online-DNS drinstehen ... selbes Ergebnis) Router: (Athlon 2,2 GHz, Suse 8.1 Pro, Orig.Kernel 192.168.0.2=pcedv) mii.tool: eth0: negotiated 100baseTx-FD, link ok eth1: negotiated 100baseTx-FD, link ok route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 217.5.98.79 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0 192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 0.0.0.0 217.5.98.79 0.0.0.0 UG 0 0 0 ppp0 ifconfig: eth0 Link encap:Ethernet HWaddr 00:0C:6E:5A:EE:E6 inet addr:192.168.0.2 Bcast:192.168.0.255 Mask:255.255.255.0 inet6 addr: fe80::20c:6eff:fe5a:eee6/10 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:21 errors:0 dropped:0 overruns:0 frame:0 TX packets:12 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:1920 (1.8 Kb) TX bytes:684 (684.0 b) Interrupt:10 Base address:0xd400 eth1 Link encap:Ethernet HWaddr 00:E0:7D:82:B3:81 inet addr:192.168.2.1 Bcast:192.168.2.255 Mask:255.255.255.0 inet6 addr: fe80::2e0:7dff:fe82:b381/10 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:18 errors:0 dropped:0 overruns:0 frame:0 TX packets:23 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:2661 (2.5 Kb) TX bytes:1722 (1.6 Kb) Interrupt:10 Base address:0xff00 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:16436 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) ppp0 Link encap:Point-to-Point Protocol inet addr:217.82.155.228 P-t-P:217.5.98.79 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1 RX packets:11 errors:0 dropped:0 overruns:0 frame:0 TX packets:13 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:3 RX bytes:1993 (1.9 Kb) TX bytes:733 (733.0 b) ping: PING 192.168.0.2 (192.168.0.2) from 192.168.0.2 : 56(84) bytes of data. 64 bytes from 192.168.0.2: icmp_seq=1 ttl=64 time=0.086 ms 64 bytes from 192.168.0.2: icmp_seq=2 ttl=64 time=0.016 ms --- 192.168.0.2 ping statistics --- 2 packets transmitted, 2 received, 0% loss, time 999ms rtt min/avg/max/mdev = 0.016/0.051/0.086/0.035 ms # # hosts This file describes a number of hostname-to-address # 127.0.0.1 localhost # special IPv6 addresses ::1 localhost ipv6-localhost ipv6-loopback fe00::0 ipv6-localnet ff00::0 ipv6-mcastprefix ff02::1 ipv6-allnodes ff02::2 ipv6-allrouters ff02::3 ipv6-allhosts 192.168.0.1 linux linux 192.168.0.100 druck1.lan.vfg druck1 192.168.0.4 pc586.lan.vfg pc586 192.168.0.50 gabi.lan.vfg gabi 192.168.0.99 test.lan.vfg test 192.168.0.2 pcedv.lan.vfg pcedv 192.168.2.1 pcedv.lan.vfg ### BEGIN INFO # # Modified_by: pppd # Backup: /etc/resolv.conf.saved.by.pppd.ppp0 # Process: pppd # Process_id: 635 # Script: /etc/ppp/ip-up # Saveto: # Info: This is a temporary resolv.conf created by service pppd. # The previous file has been saved and will be restored later. ### END INFO search dns00.btx.dtag.de dns02.btx.dtag.de dns03.btx.dtag.de nameserver 193.158.141.116 nameserver 194.25.2.129 kannst Du damit was anfangen? THx für jeden Tip -- Joerg Thuemmler sysadmin@vordruckleitverlag.de