[En-Nut-Discussion] Wrong ethernut broadcast.

[Zachary]

Hi all,

I am having problem with tcp stack.

The only thing that run all the time seems to be ARP protocol, because when 
I turn on the board, the tcp answer any request for a very short time after 
that I have no more answer from it, no ping, no connections seems it dies, 
so I am loonking my network using ethereal, and stayed suprise because the 
ethernut was sending a broadcasts all the time, so stack tcp seems to be 
running and not died as was thinking.

I put into the board the example application named logtime, this application 
search the syslogd in an IP that we specify for it, so it sends a broadcast 
to network to discover the MAC of this server, but no one answer this 
request and the target is on line, below I have the data it sends:

You may see that we have some difference betwin this 2 requests.
The request made by linux does not have trailer option, and when this 
options exist it is not zeroed like Ethernut does, and another diference is 
that target mac address goes zeroed and nod filled like Ethernet does.

I am not especialist in TCPIP, so ask to you guys, Is Ethenut doing a wrong 
broadcast? The ethernut needs some configuration that i did wrong?



 /****************************************************************************************************************/THIS IS THE REQUEST MADE BY O LINUX BOX THAT WAS ANSWERED.No.     Time        Source                Destination           ProtocolInfo    207 285.019744  CompalEl_7c:1d:e0     Broadcast             ARP      Whohas 192.168.0.12?  Tell 192.168.0.11Frame 207 (42 bytes on wire, 42 bytes captured)    Arrival Time: Nov  1, 2006 12:09:43.792372000    Time delta from previous packet: 0.000103000 seconds    Time since reference or first frame: 285.019744000 seconds    Frame Number: 207    Packet Length: 42 bytes    Capture Length: 42 bytes    Protocols in frame: eth:arpEthernet II, Src: 00:02:3f:7c:1d:e0, Dst: ff:ff:ff:ff:ff:ff    Destination: ff:ff:ff:ff:ff:ff (Broadcast)    Source: 00:02:3f:7c:1d:e0 (CompalEl_7c:1d:e0)    Type: ARP (0x0806)Address Resolution Protocol (request)    Hardware type: Ethernet (0x0001)    Protocol type: IP (0x0800)    Hardware size: 6    Protocol size: 4    Opcode: request (0x0001)    Sender MAC address: 00:02:3f:7c:1d:e0 (CompalEl_7c:1d:e0)    Sender IP address: 192.168.0.11 (192.168.0.11)    Target MAC address: 00:00:00:00:00:00 (00:00:00_00:00:00)    Target IP address: 192.168.0.12 (192.168.0.12) /****************************************************************************************************************/HERE IS THE ETHERNUT REQUEST WITH NOANSWER.No.     Time        Source                Destination           ProtocolInfo    208 285.020082  EdimaxCo_97:dc:fc     CompalEl_7c:1d:e0     ARP192.168.0.12 is at 00:00:b4:97:dc:fcNo.     Time        Source                Destination           ProtocolInfo     10 14.034228   192.168.0.100         Broadcast             ARP      Whohas 192.168.0.14?  Tell 192.168.0.100Frame 10 (60 bytes on wire, 60 bytes captured)    Arrival Time: Nov  1, 2006 12:05:12.806856000    Time delta from previous packet: 6.264926000 seconds    Time since reference or first frame: 14.034228000 seconds    Frame Number: 10    Packet Length: 60 bytes    Capture Length: 60 bytes    Protocols in frame: eth:arpEthernet II, Src: 00:06:98:02:01:00, Dst: ff:ff:ff:ff:ff:ff    Destination: ff:ff:ff:ff:ff:ff (Broadcast)    Source: 00:06:98:02:01:00 (192.168.0.100)    Type: ARP (0x0806)    Trailer: 000000000000000000000000000000000000Address Resolution Protocol (request)    Hardware type: Ethernet (0x0001)    Protocol type: IP (0x0800)    Hardware size: 6    Protocol size: 4    Opcode: request (0x0001)    Sender MAC address: 00:06:98:02:01:00 (192.168.0.100)    Sender IP address: 192.168.0.100 (192.168.0.100)    Target MAC address: ff:ff:ff:ff:ff:ff (Broadcast)    Target IP address: 192.168.0.14 (192.168.0.14)    regardsZach