You're seeing the send stop from the server because the client's receive window
is smaller than the next segment to send. At packet 28091, the receiver's
window drops to 4 bytes and the sender's next segment is 8 bytes
LwIP (on the server) is treating this as a zero window rather than splitting
Thank you very much for your answers. I am able to receive my data from both
clients now at the same time.
One strange issue or at least something I do not understand still remains :
I can receive all incoming data but when I try to send dummy data back in
the receive callback, after
about 20
Noam Weissman wrote:
> My mistake, I thought that pcb->local_port means working port while
> pcb->listenr->local_port is the server port
OK, just to clarify this for anyone reading:
pcb->local_port of an accepted pcb is (by definition!) the same as the
listener's local_port!
Simon
oam=silrd@nongnu.org] On
Behalf Of Simon Goldschmidt
Sent: Monday, May 22, 2017 4:10 PM
To: lwip-users@nongnu.org
Subject: Re: [lwip-users] Raw api + multiple TCP Connections
Noam Weissman wrote:
> If you use Lwip 1.41 the tcp_accepted function should accept the
> SERVER pcb and not the new
Noam Weissman wrote:
> Jan see his code. He was trying to compare listening port with working port
OK, now I'm confused. In the accept callback, he compared the local port to see
for which port the incoming connection was.
I don't see what's wrong there?
Simon
Noam Weissman wrote:
> If you use Lwip 1.41 the tcp_accepted function should accept the SERVER pcb
> and not the new connection pcb
In the initial post, he said he's using 2.0.2, not 1.4.1 (what's that 1.41
again?)
> Your accept function is wrong.
I fail to see the difference between your
Jan see his code. He was trying to compare listening port with working port
-Original Message-
From: lwip-users [mailto:lwip-users-bounces+noam=silrd@nongnu.org] On
Behalf Of Jan Menzel
Sent: Monday, May 22, 2017 4:00 PM
To: lwip-users@nongnu.org
Subject: Re: [lwip-users] Raw api
Hi Werner!
In you initial post you wrote, that your system catches a Hardfault. A
Hardfault indicates are general MCU failure which can be something like
memory corruption, stack problem, unaligned address, division by zero or
even escalated from some other fault. The actual reason can
do not have errors... wrote it fast :).
BR,
Noam.
From: lwip-users [mailto:lwip-users-bounces+noam=silrd@nongnu.org] On
Behalf Of Werner Motz
Sent: Monday, May 22, 2017 2:38 PM
To: 'Mailing list for lwIP users'
Subject: Re: [lwip-users] Raw api + multiple TCP Connections
U are right, but
U are right, but I don't know where the mistake is. I can debug it and the
breakpoints in myCallback1 and myCallback2 are hit.
The also debugged the init_Server and the binding or listen gave no error.
Both connections are initiated correctly.
I do init:
void init_Server(void)
{
@nongnu.org] On
Behalf Of Werner Motz
Sent: Monday, May 22, 2017 1:58 PM
To: 'Mailing list for lwIP users'
Subject: Re: [lwip-users] Raw api + multiple TCP Connections
Hi,
I apologize myself.
I (uC) am the server and I initiate two connections with IP_ADDR_ANY but
different ports.
The PC
Hi,
I apologize myself.
I (uC) am the server and I initiate two connections with IP_ADDR_ANY but
different ports.
The PC is the Client and from here I connect to the Server.
Hi,
Do you mean two connections that you initiate from your device to two
different IP's
or two
To: lwip-users@nongnu.org
Subject: [lwip-users] Raw api + multiple TCP Connections
Hello,
I am using lwip 2.0.2 RAW API and I have a question depending multiple TCP
Connections.
I create two connections without problems. Over each of them I can send and
receive data.
When a single client sends me
Hello,
I am using lwip 2.0.2 RAW API and I have a question depending multiple TCP
Connections.
I create two connections without problems. Over each of them I can send and
receive data.
When a single client sends me data every 1ms, my receive callback function
(tcp_recv(pcb, myCallback1)) gets
14 matches
Mail list logo
