Re: RE: TCP sequence numbers. [2 Attachments]

We are using the RCM3000 modules.  They use the Realtek Ethernet controller, which I thought was half-duplex. The customer turned off auto-negotiate and set the switch's port to 10mbit and tried both half duplex and full duplex. They report it didn't help.

I found out they are using a Cisco 3750x switch. I've asked if they could loan us one so we can try to duplicate what they are seeing.

In going through the Wireshark data, I don't see any abnormal packets. Just lots of Gratuitous ARPs from their system. Our device appears to be humming along just fine, and then abruptly resets the connection at random times. Very strange.

Steve




On Wednesday, January 29, 2014 7:13 AM, "Huynh, Henry" <[email protected]> wrote:
  
  
>Hello, 
>You meant “Turning off automatic crossover “ the port of the Rabbit board?, if so, could you show me how. Thanks 
>  
>Henry Huynh 
>
>
>  
>  
>From:[email protected] [mailto:[email protected]] On Behalf Of [email protected]
>Sent: Monday, January 27, 2014 2:57 AM
>To: [email protected]
>Subject: [rabbit-semi] RE: TCP sequence numbers.   
>  
>   
>Hi Steve, 
>  
>I had a similar problem last year. 
>Try to turn off automatic crossover ("auto MDI-X" or "auto-uplink") of the Rabbit ethernet port (you can try with the switch ports also, if there is such option at all). 
>  
>Turn off auto negotiation too. Make sure to configure the right transmission parameters, such as speed, duplex mode, and flow control. 
>  
>Wish you success with this annoying eth problem, 
>Alexander Hristov 
>  
>        
> 
>
>