[lwip-users] Transport terminal Using Tcp - ask for help~

2014-05-07 Thread lars.t...@qq.com
Hello everyone: i encounter a problem when i use tcp transport. No.TimeSourceDestinationProtocolLengthInfo (1)2562.210092192.168.1.20192.168.1.60TCP571[TCP segment of a reassembled PDU] (2)2572.212896192.168.1.60192.168.1.20TCP64[TCP segment of a reassembled PDU]

Re: [lwip-users] Transport terminal Using Tcp - ask for help~

2014-05-07 Thread Sergio R. Caprile
I would like to try to help you, but honestly I don't understand what are you doing what is not working I guess that by answer the ACK you mean your application is supposed to send something in response to something and you think it should do it when the ACK comes. Well, that would be true if

Re: [lwip-users] How to add lwIP support for nios2 processor.

2014-05-07 Thread Andreas Bachmann
Hi Ritesh, First, there is a difference between Quartus resp. Nios II Embedded Design Suite (EDS) [= Eclipse + GNU Tools] and the Nios II processor. Altera Quartus resp. EDS is now at version 13.1. The release date of version 9.1 was on November 2009 (long time ago) and version 9.0 even

Re: [lwip-users] Transport terminal Using Tcp - ask for help~

2014-05-07 Thread Pomeroy, Marty
H... (3) 258 2.414096 192.168.1.20 192.168.1.60 TCP 54 56864 → cisco-sccp [ACK] Seq=65157 Ack=1288 Win=16054 Len=0 A 54 byte packet is too small (http://en.wikipedia.org/wiki/Ethernet_frame#Runt_frames). Can you check the ethernet flags generated by your hardware, to see if it has

Re: [lwip-users] Transport terminal Using Tcp - ask for help~

2014-05-07 Thread Sergio R. Caprile
Marty, some sniffers (like Wireshark) on some OSs (like windoze) do not capture the preamble nor the CRC, and are intelligent enough to remove the padding. 54 is OK for 14 bytes Ethernet + 20 IP header + 20 TCP header, no options, no length Regards --

Re: [lwip-users] Transport terminal Using Tcp - ask for help~

2014-05-07 Thread Pomeroy, Marty
Preamble and CRC are stripped because the ethernet chips typically don't pass those on to the buffer (many can be configured to include the CRC). In Wireshark, select your packet 3, and look at the top line of the middle window. It might say something like: Frame 258: 54 bytes on wire (432

Re: [lwip-users] lwip-users Digest, Vol 129, Issue 3

2014-05-07 Thread lars.t...@qq.com
--- ??? TEL : 15501024303 E-mail : lars.t...@qq.com Address : Haidian,Beijing,100091,China -- next part -- An HTML attachment was scrubbed... URL: http://lists.nongnu.org/archive/html/lwip-users/attachments/20140507/45f5450c/attachment.html