> OK. So your gateway doesn't answer. That either means your gateway is
> disconnected, defective or switched off.

I don't think so. When I shutdown Suse10 and reboot with Suse9 on this same 
machine there's no problem to connect to the gateway or the other computer. I 
don't change anything on cards or cables etc, just starting other OS. I also 
pinged the gateway from the other computer (a Win98) that is connected to the 
same gateway via the same switch, while running Suse 10 here, and the gateway 
answers to the Win-Machine. 

192.168.2.3 is the Windows Machine, 192.168.2.2 this one, and 192.168.2.1 the 
gateway.  

> Run
> # tcpdump -neti eth0 arp or icmp
> and in another window
> # ping 192.168.2.3
> while this other machine (192.168.2.3) is switched on. If ping works,
> the bug is clearly not at your machine, but between the switch and
> the gateway or directly at the gateway.

> Regards,
> Carl-Daniel

this is the output:

# tcpdump -neti eth0 arp or icmp
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes
00:08:a1:35:bf:bc > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: arp 
who-has 192.168.2.3 tell 192.168.2.2
00:08:a1:35:bf:bc > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: arp 
who-has 192.168.2.3 tell 192.168.2.2
00:08:a1:35:bf:bc > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: arp 
who-has 192.168.2.3 tell 192.168.2.2
00:08:a1:35:bf:bc > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: arp 
who-has 192.168.2.3 tell 192.168.2.2
00:08:a1:35:bf:bc > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: arp 
who-has 192.168.2.3 tell 192.168.2.2
00:08:a1:35:bf:bc > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: arp 
who-has 192.168.2.3 tell 192.168.2.2
00:30:4f:21:d8:f9 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 60: arp 
who-has 192.168.2.1 tell 192.168.2.3
00:08:a1:35:bf:bc > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: arp 
who-has 192.168.2.1 tell 192.168.2.2
00:08:a1:35:bf:bc > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: arp 
who-has 192.168.2.1 tell 192.168.2.2
00:08:a1:35:bf:bc > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: arp 
who-has 192.168.2.1 tell 192.168.2.2
00:08:a1:35:bf:bc > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: arp 
who-has 192.168.2.1 tell 192.168.2.2
00:08:a1:35:bf:bc > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: arp 
who-has 192.168.2.1 tell 192.168.2.2
00:08:a1:35:bf:bc > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: arp 
who-has 192.168.2.1 tell 192.168.2.2

13 packets captured
26 packets received by filter
0 packets dropped by kernel

I pinged to 192.168.2.3, stopped after 4 errors, then pinged to 192.168.2.1 
and stopped again.

Does this list say anything in direction of my problem?

regards, Daniel

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to