[lwip-users] Once UDP fails to receive then resending fails as well

[digitalwave]

hi,

I am working on tm4c1294+FreeRTOS+lwip1.4.1 with daemons running on HP-unix

The communication modules had worked fine in previous network environment. 
One day network guy set up a new network env and it stops communication
after runnig 3~4 hours.

I just took over this project and there is no one who is in charge of
daemons, so it's hard to check where the problems come from.

The network guy said it's same as the previous network environment, but it
seems not for me.

Every second, MCU sends a request of server time and receive a response from
a daemon. It runs well for 3~4 hours then what happens is once the MCU
requests the server time, MCU doesn't receive anything.

Even though MCU re-sends the same packet to the server it fails to send at
lwip_sendto().

Obtaining socket fd and close it works properly. Because of UDP , closing
the socket with fd doesn't physically disconnect the connection I guess.

The daemon doesn't spit out any errors although MCU doesn't receive the
response. it usually says something on log file if something happens.

Weird thing is I can't trace down packets using "Wireshark". I don't see any
packets between the server and MCU even if they communicate each other well
before the error happens.

The network guy is not really supportive so I try to figure things out by
myself.

How can I narrow down the issue? and where is the problem comes from?

Regards,
Jin



--
View this message in context: 
http://lwip.100.n7.nabble.com/Once-UDP-fails-to-receive-then-resending-fails-as-well-tp29535.html
Sent from the lwip-users mailing list archive at Nabble.com.