Re: [lwip-users] handling packets with equal sequence number

2011-03-30 Thread Thomas Richter (TCD - DE/Dresden)
Hi Kieran, based on your answers is it right, that each byte in the data stream occurs only once? Even if a blocking state (equals Receive Not Ready at one side off wire) and after then a retransmission occurs then the IP stack gives me (in lwIP the callback function registered with tcp_recv()) ea

Re: [lwip-users] handling packets with equal sequence number

2011-03-30 Thread Kieran Mansley
On 30 Mar 2011, at 15:59, Thomas Richter (TCD - DE/Dresden) wrote: > Ok the data stream is correctly ordered. But how my application can the > information that the frames have the same sequence number? It won't need to. lwIP will give it each byte exactly once, even if there are duplicates on

Re: [lwip-users] handling packets with equal sequence number

2011-03-30 Thread Thomas Richter (TCD - DE/Dresden)
Hi Kieran, thanks for your answer. Ok the data stream is correctly ordered. But how my application can the information that the frames have the same sequence number? Is there any possibility to get this information in lwIP? Or have I analyze all my data to prevent double data? Best regards Thoma

Re: [lwip-users] handling packets with equal sequence number

2011-03-30 Thread Kieran Mansley
On 30 Mar 2011, at 15:39, Thomas Richter (TCD - DE/Dresden) wrote: > Give lwIP both frames Yes, just give lwIP all the frames your driver receives off the wire. Your driver should have no need to parse the frames at all. lwIP will convert the stream of packets, with gaps, overlaps, out of or

[lwip-users] handling packets with equal sequence number

2011-03-30 Thread Thomas Richter (TCD - DE/Dresden)
Hi, in my tests the following problem occurs: A packet with the same sequence number was sent to lwIP. Wireshark TCP analysis says it was a TCP Retransmission with same sequence number and same data (plus a little bit more data append to the earlier transmitted data). My question: What will be ha

Re: [lwip-users] uIp vs LWip

2011-03-30 Thread FreeRTOS Info
I think, from memory, an lwIP build is about 40K bytes - but that is a rough estimate and the usual caveats apply (compiler, optimisation, configuration, etc.). However, if RAM is your limiting factor, then lwIP uses a lot more RAM than uIP, as uIP has only a single buffer, with no queuing. lwIP

[lwip-users] uIp vs LWip

2011-03-30 Thread Daniel Kilshtein
Currently I run uIp on an ARM11. I'm thinking about moving on to the latest LWIP but a bit worried about the code size (my RAM is a somewhat limited and the whole code should run under FreeRtos) Does anyone know (roughly) how much the LWIP code size is bigger than Uip code size? Thanks & Be

Re: [lwip-users] "flow control" manipulation with lwIP-1.3.2

2011-03-30 Thread Kieran Mansley
On 30 Mar 2011, at 08:02, Thomas Richter (TCD - DE/Dresden) wrote: > > For this I would using the parameter "window" in TCP header and set them > to 0 with lwIP. But what can I do to generate this? There's no API to do this directly, and you still might not get what you want. Although you woul

[lwip-users] how to use loopif in embedded system

2011-03-30 Thread LI Zhong
Hi all, I have ported the LwIP into my system ucosII + s3c2440 + DM9000,I do not finish the driver of NIC .Now, how do I test my lwIP and how to use loopif to test the protocol when the hardware driver is not ready? Best Regards, Li Zhong, ___ lwip-us

[lwip-users] "flow control" manipulation with lwIP-1.3.2

2011-03-30 Thread Thomas Richter (TCD - DE/Dresden)
Hi, I´m searching for a possibility to manipulate the "flow control" of TCP data handling. I know that there is the parameter "Window" in the TCP header (see http://en.wikipedia.org/wiki/Transmission_Control_Protocol#TCP_segment_structure). My task is to transport TCP data over Ethernet interface