Hello > ?tap-info Riometer0 > > #log info 964298200737 raw peer\_02:02:00:00:00:00\_at\_29 > #log info 964298200737 raw peer\_d0:67:e5:f1:9b:e7\_at\_15000 > #log info 964298200738 raw peer\_00:1a:a0:b1:1e:9b\_at\_15000 > #log info 964298200738 raw peer\_00:1e:4f:cc:cc:b4\_at\_15000
So that is a good sign, tg-tap has seen 3 peers - managed to exchange arp traffic with them. If you do a tcpdump on the other side of the link to the roach you should see the arp messages being sent ... Is the machine you want to ping from in that list (ie does it have one of those mac addresses ? If not, maybe wait some time until it shows up). If it is then things are strange - are pings maybe blocked by some firewalling rule, or maybe specify a smaller ping packet in case there are some problems with large packets being truncated ? Also: Is there any other roach which might have the same mac address ? Not sure what the length is of a linux ethernet device name - maybe shorten Riometer0 to something 6 bytes or less ? Furthermore note that mac addresses with the 02 bit set have special meaning, maybe there is a fancy router/switch in there which has some rules about that ? Try using tcpdump on a linux/unix box plugged directly into that roach port, let us know if you see any ICMP reply, even if truncated or checksum incorrect And finally: You may be unhappy if you have the tap IP address in the same subnet as the IP address of the powerPC ethernet interface - linux systems have some interesting behaviour if they have multiple interfaces on the same subnet regards marc > #log info 964298200738 raw tap\_device\_name\_Riometer0\_on\_fd\_27
