On Tue, 20 Jun 2000, Andreas Meyer wrote:
> On 19-Jun-00, Fred Wright wrote:
>
> >> --- 192.168.0.2 ping statistics ---
> >> 45 packets transmitted, 0 packets received, 100% packet loss
> >
> > This means that there is no route to the destination, which usually
> > indicates ARP trouble. Start from offline in MiamiDx and a fresh
> > boot of the PC, and do the ping with MiamiTCPDump running in another
> > window.
>
> I disabled the gateway-entries in Miami and the PC. Then an entry in
> the gateway-gadget in Miami is inserted automaticaly -> 255.255.255.0
> I also disabled the the Samba-entries in Services and InetD.
>
> A ping from both sides says this:
>
> miamitcpdump: listening on eth0
> ........
> 08:18:58.520002 arp who-has 192.168.1.2 tell 192.168.1.1 (52:54:40:26:79:ca)
> 08:18:59.520003 arp who-has 192.168.1.2 tell 192.168.1.1 (52:54:40:26:79:ca)
> 08:19:10.960000 192.168.1.2.138 > 192.168.1.255.138: udp 210
> 08:20:23.960000 arp who-has 192.168.1.1 tell 192.168.1.2 (0:e0:7d:7d:2c:38)
> 08:20:23.960006 192.168.1.1 > 192.168.1.2: icmp: echo request
> 08:20:23.960009 arp reply 192.168.1.1 is-at 52:54:40:26:79:ca (0:e0:7d:7d:2c:38)
> 08:20:25.340000 arp who-has 192.168.1.1 tell 192.168.1.2 (0:e0:7d:7d:2c:38)
> 08:20:25.340005 arp reply 192.168.1.1 is-at 52:54:40:26:79:ca (0:e0:7d:7d:2c:38)
> 08:20:26.360000 arp who-has 192.168.1.1 tell 192.168.1.2 (0:e0:7d:7d:2c:38)
> 08:20:26.360005 arp reply 192.168.1.1 is-at 52:54:40:26:79:ca (0:e0:7d:7d:2c:38)
> 08:20:27.380000 arp who-has 192.168.1.1 tell 192.168.1.2 (0:e0:7d:7d:2c:38)
> 08:20:27.380005 arp reply 192.168.1.1 is-at 52:54:40:26:79:ca (0:e0:7d:7d:2c:38)
> 08:21:35.020002 192.168.1.1 > 192.168.1.2: icmp: echo request
> 08:21:36.020004 192.168.1.1 > 192.168.1.2: icmp: echo request
> 08:21:37.020002 192.168.1.1 > 192.168.1.2: icmp: echo request
> 08:21:38.020005 192.168.1.1 > 192.168.1.2: icmp: echo request
> 08:21:39.020003 192.168.1.1 > 192.168.1.2: icmp: echo request
> 08:21:40.020004 192.168.1.1 > 192.168.1.2: icmp: echo request
> 08:21:40.940001 192.168.1.2.138 > 192.168.1.255.138: udp 209
> 08:21:41.040002 192.168.1.1 > 192.168.1.2: icmp: echo request
> 08:21:42.040004 192.168.1.1 > 192.168.1.2: icmp: echo request
> ...........
>
> It seems that the answer from Miami to the pc-ping tells the right
> hardware-entries. So there must be traffic on PC <-> Amiga?
> But pinging always shows 100% packet-loss on Amiga-side or Request
> timed out on PC-side.
>
> I�m sorry to post this here again but I have no idea what to do now.
> I also tried full-duplex on both sides.
You can't use full-duplex with a hub.
I think what's happening (I should have realized this in the earlier post)
is that Amiga->PC traffic isn't working at all. You can see traffic from
the PC, and you can see traffic being sent by the Amiga, but that doesn't
prove that it gets to the PC.
If the hub LED for the Amiga blinks properly when you do this, check the
cable from the hub to the PC. If it doesn't, check the cable from the hub
to the Amiga. Also try swapping the cables to see if the LED behavior
changes.
Fred Wright
--
To unsubscribe send "unsubscribe miami-talk-ml" to
"[EMAIL PROTECTED]". For help on list commands send "help" to
"[EMAIL PROTECTED]".
