On 21-Jun-00, Fred Wright wrote:
> Address Resolution Protocol - it's used to determine the Ethernet
> address for a given IP address. When you ping "from scratch", it
> first needs an ARP exchange for the machines to determine each
> other's Ethernet addresses, then the actual IP packets can be sent.
You bring light into my darkness....
> This shows that you are receiving the PC's broadcasts OK, but not
> ARP responses. I'd suggest trying broadcast pings to see if it's
> specifically ARP that's failing, but Windoze doesn't like to answer
> broadcast pings. What I'd suggest is that you try pinging from the
> PC (again starting
>> from scratch) with MiamiTCPDump running. Try both a normal unicast
>> ping
> (192.168.1.1) and a broadcast ping (192.168.1.255), and see what
> gets through.
This is what I get:
miamitcpdump: listening on eth0
;unicastping from PC to 192.168.1.1
12:35:22.780001 arp who-has 192.168.1.1 tell 192.168.1.2 (0:e0:7d:7d:2c:38)
12:35:22.780006 arp reply 192.168.1.1 is-at 52:54:40:26:79:ca (0:e0:7d:7d:2c:38)
12:35:24.260001 arp who-has 192.168.1.1 tell 192.168.1.2 (0:e0:7d:7d:2c:38)
12:35:24.260006 arp reply 192.168.1.1 is-at 52:54:40:26:79:ca (0:e0:7d:7d:2c:38)
12:35:25.280001 arp who-has 192.168.1.1 tell 192.168.1.2 (0:e0:7d:7d:2c:38)
12:35:25.280006 arp reply 192.168.1.1 is-at 52:54:40:26:79:ca (0:e0:7d:7d:2c:38)
12:35:26.300000 arp who-has 192.168.1.1 tell 192.168.1.2 (0:e0:7d:7d:2c:38)
12:35:26.300005 arp reply 192.168.1.1 is-at 52:54:40:26:79:ca (0:e0:7d:7d:2c:38)
;broadcastping from PC to 192.168.1.255
12:35:54.780000 192.168.1.2 > 192.168.1.255: icmp: echo request
12:35:54.780005 192.168.1.1 > 192.168.1.2: icmp: echo reply
12:35:56.240000 192.168.1.2 > 192.168.1.255: icmp: echo request
12:35:56.240005 192.168.1.1 > 192.168.1.2: icmp: echo reply
12:35:57.260001 192.168.1.2 > 192.168.1.255: icmp: echo request
12:35:57.260006 192.168.1.1 > 192.168.1.2: icmp: echo reply
12:35:58.260001 192.168.1.2 > 192.168.1.255: icmp: echo request
12:35:58.280001 192.168.1.1 > 192.168.1.2: icmp: echo reply
12:36:08.100000 192.168.1.2.138 > 192.168.1.255.138: udp 209
> Unfortunately this looks more like a hardware problem with the NIC
> on one of the two machines, where unicasts from PC to Amiga aren't
> working (the other direction is unknown, although you might look to
> see if the PC's hub LED flashes when you ping from the Amiga).
NIC? No, the PC hub-leds aren�t flashing when I ping from the Amiga.
>>>> Subnet-mask 255.255.255.0
>>>> Gateway 192.168.0.2
>>
>> Is the PC really supposed to be a gateway to somewhere? If not,
>> this is incorrect. In any case, it's unneeded for local pings.
I added both, the Amiga-ID and the PC-ID in the Gateway-entry on
PC-side. This is what is recommended in the X-Surf maunual. "All
computers on the network have to be added here".
> I forgot that Miami insists on having some gateway definition, due
> to its PPP roots. If you don't have a real gateway on the LAN (i.e.,
> you're not using the PC to route net traffic), it's usually best to
> use a nonexistent IP, e.g. 192.168.1.254.
>
> This is fixed in MiamiDx, which is perfectly happy to have no
> gateway on the LAN.
I�m sorry that I forgot to mention that I meant MiamiDx when I spoke
of "Miami".
> If you're using Miami rather than MiamiDx, it's absolutely guranteed
> that the Amiga isn't a gateway. :-)
>> Yes, I understand that. But disabling Microsoft-Networking would
>> not allow file-sharing, would it?
>
> True, just be careful you're not sharing your files with every
> cracker on the net. They like nothing better than to look for open
> shares or shares with easily guessable passwords.
So if I ever go to the Internet with the PC and Amiga as gateway I
disable filesharing? I have the firewall enabled in MiamiDx; not now
as long as I�m testing the LAN.
>> on the Amiga. I get errors with Yam that my ISP is not available.
>> Also downloading a file with Voyager fails when the ethernet is
>> online.
>> Going offline with the ethernet-interface and then online with ppp0
>> works then.
>
> Are you using Miami or MiamiDx? In the former case, you obviously
> can't have both interfaces online at the same time. In the latter
> case, make sure you set the gateway priority to 0 for the Ethernet,
> or at least to a lower value than what you use for the PPP
> interface.
Thanks for that! I�ll try it out.
Regards
--
Andreas Meyer
--
http://home.wtal.de/MeineHomepage/
--
--
To unsubscribe send "unsubscribe miami-talk-ml" to
"[EMAIL PROTECTED]". For help on list commands send "help" to
"[EMAIL PROTECTED]".
