Just a note to say this is probably not the problem, since ps -elf on the ROACH gives the following output:
4 S root 615 596 1 80 0 - 448 select 12:52 ? 00:00:00 tgtap -b /proc/614/hw/ioreg/gbe0 -a 10.0.0.20 -t tap3 -m 02:02:0A:00:00:14 -p 60000 So the command is arriving at the ROACH in the right format, and I suppose ifconfig just does not display it as I expect. Still, I am not getting any packets. (and I know that I stated the expected address incorrectly below--decimals 10 and 20 become 0A and 14 hex). Regards, Dale ________________________________________ From: [email protected] [[email protected]] On Behalf Of Gary, Dale [[email protected]] Sent: Thursday, January 05, 2012 8:34 PM To: [email protected] Subject: [casper] Problem with tap? Hi All, I am setting up a ROACH at the observatory that worked fine in the lab. However, here I am not getting 10Gbe packets, although the internal counters show that the design is creating them. I looked around and believe I have a problem with the tap creation. The Python script does this: print 'Configuring transmitter core...', sys.stdout.flush() fpga.tap_start('tap3',tx_core_name,mac_base+source_ip,source_ip,fabric_port) print 'done' where source_ip=10*(2**24) + 20 #10.0.0.20 mac_base=(2<<40) + (2<<32) I therefore expect a hardware address 00 02 02 10 00 00 20. When I do an ifconfig, I see tap3 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 inet addr:10.0.0.20 P-t-P:10.0.0.20 Mask:255.255.255.0 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) That is a lot of zeros in the hardware address! Am I right that this anomalous hardware MAC address is the cause of the problem? I could have some setup wrong somewhere. Any ideas what could cause this? All other register settings seem to work okay. Thanks, Dale
