Alternatively, putting:
mii-tool -A 100baseTx,10baseT eth0
in a startup script on the roach should do the job with much less fiddling.
(And whoever packages etch for the roach should add ethtool.)
--Andy
On Wed, Oct 27, 2010 at 1:14 PM, Dan Werthimer d...@ssl.berkeley.edu wrote:
Dear Roach
Hi Dave and Jason,
Here are the outputs of print_10gbe_core_details and tcpdump. It looks to
me that the ARP table is configured properly. Do you still see something
funny in the received packet?
FYI, I'm using the latest versions of the roach software with the
exception of the tcpborphserver,
Hi Sean,
On Oct 29, 2010, at 2:10 PM, mch...@physics.ucsb.edu wrote:
Here are the outputs of print_10gbe_core_details and tcpdump. It looks to
me that the ARP table is configured properly. Do you still see something
funny in the received packet?
ARP Table:
IP: 10. 0. 0. 20: MAC: 02
If you ping the the ROACH from the PC (e.g. run ping 10.0.0.20 on the
PC), does it get replies? What does arp -a show afterwards?
[r...@arcons controlScripts]# ping 10.0.0.20
PING 10.0.0.20 (10.0.0.20) 56(84) bytes of data.
From 10.0.0.30 icmp_seq=1 Destination Host Unreachable
From 10.0.0.30
On Oct 29, 2010, at 4:34 PM, mch...@physics.ucsb.edu wrote:
[r...@arcons controlScripts]# /sbin/arp -a
? (10.0.0.20) at incomplete on eth1
This show that the PC is not able to get the MAC address for 10.0.0.20 (the
ROACH). I guess it's probably a routing problem or a firewall problem. What
5 matches
Mail list logo