> Hi all, > > We have been getting packets from our design from one ROACH2, but when we > added a second one that was supposed to be sending to another interface, > we > discovered that both interfaces were receiving the packets. We discovered > that the packets have broadcast address packet header although they have > unicast IP address inside. The ARP table shows the Roach MAC address, but > not that of the destination. > > We think the problem is that Roach2 is not sending ARP requests (wireshark > does not show any ARP packets from the ROACH). We are able to ping Roach2 > from the machine at the other end, and it can get Roach2's MAC address as > well. Any clue what could be going wrong? We also tried disabling firewall > of the destination machine, but that did not help.
Hi Nimish. We had the same problem here. Glenn Jones hacked something in the tcpborphserver to fix it. Hopefully he can reply to you with the details... > I declare this problem at least mostly fixed. > Disabling the burst checking in tcpborphserver3 has made the ROACH2's > send routine ARP requests and correctly populate their ARP tables. > > The tcpborphserver3 authors may have a more elegant fix we can apply > down the road. > > Glenn John > > Thanks, > > Nimish > > > -- > Nimish Sane > > Center for Solar-Terrestrial Research > New Jersey Institute of Technology > University Heights > > Newark, NJ 07102-1982 USA > > Tel: (973) 642 4958 > > Fax: (973) 596 3617 > [email protected] >
