Re: [lwip-users] dhcp_bind never called if DHCP_DOES_ARP_CHECK

2013-06-13 Thread ella
Thanks. Did not see hat flow. For some reason it does not work on my setup. I will turn on debug traces and will see. -- View this message in context: http://lwip.100.n7.nabble.com/dhcp-bind-never-called-if-DHCP-DOES-ARP-CHECK-tp5359p21567.html Sent from the lwip-users mailing list archive at

Re: [lwip-users] LPC1768/9 :: FreeRTOS 7.4 :: lwIP 1.4.1 ::TCPsend/recv

2013-06-13 Thread furiantes
Hm, that would be correct but... why than is all ok on other tool. It's seem that server or lwIP do not send some things ok and the server than just don't know about connection. Becouse the same request it was sent trought the putty and his TCP connection and it worked very well. It's really b

Re: [lwip-users] LPC1768/9 :: FreeRTOS 7.4 :: lwIP 1.4.1 ::TCPsend/recv

2013-06-13 Thread Pomeroy, Marty
If the server is initiating the close, it's not an lwip issue... -Original Message- From: lwip-users-bounces+martypomeroy=novabio@nongnu.org [mailto:lwip-users-bounces+martypomeroy=novabio@nongnu.org] On Behalf Of furiantes Sent: Thursday, June 13, 2013 2:00 PM To: Mailing lis

Re: [lwip-users] LPC1768/9 :: FreeRTOS 7.4 :: lwIP 1.4.1 :: TCPsend/recv

2013-06-13 Thread furiantes
Actually i have (and trying with) Connection: Keep-Alive As I wrote down. The problem it seems that server after sending full of data (all packets) just send a FIN, ACK which is closing conn, so than i cant do netconn_write anymore. As i sad i tried with Connection: Keep-Alive etc. but it ju

Re: [lwip-users] LPC1768/9 :: FreeRTOS 7.4 :: lwIP 1.4.1 :: TCPsend/recv

2013-06-13 Thread Pomeroy, Marty
You have "Connection: Close" in your request string. Doesn't that tell the server to close the socket? -Original Message- From: lwip-users-bounces+martypomeroy=novabio@nongnu.org [mailto:lwip-users-bounces+martypomeroy=novabio@nongnu.org] On Behalf Of Furiantes Sent: Thursda

Re: [lwip-users] dhcp_bind never called if DHCP_DOES_ARP_CHECK

2013-06-13 Thread Pomeroy, Marty
Setting a breakpoint in dhcp_bind, it is called from dhcp_timeout. So DHCP offers an address, lwip ARPS the address and gets no response, so it binds to it. Those with more experience, is that right? -Original Message- From: lwip-users-bounces+martypomeroy=novabio@nongnu.org [mail

Re: [lwip-users] dhcp_bind never called if DHCP_DOES_ARP_CHECK

2013-06-13 Thread ella
HI, I also stuck with the same problem (in 1.4.1 it is the same): And in opt.h: So if ARP and DHCP are enabled dhcp_bind will be newer called. What is the logic behind it (assuming this is not a bug)? Maybe ARP is not required if DHCP is in use? -- View this message in context: http://lw

Re: [lwip-users] ppp_new gprs

2013-06-13 Thread Sylvain Rochet
Hi Nikolas, On Thu, Jun 13, 2013 at 09:39:59AM +1000, Nikolas Karakotas wrote: > Hi, > > I thought so, by the way where is the best place to call pppapi_sighup? When DCD state change to NO CARRIER, but DCD is rarely wired nor relevant with GPRS modems, so you just have to wait for LCP timeout.

Re: [lwip-users] LPC1768/9 :: FreeRTOS 7.4 :: lwIP 1.4.1 :: TCP send/recv

2013-06-13 Thread Furiantes
Hello, after sometime of debug, i saw: - Server send FIN, ACK after sending the packet - which cause the connection to go to state CLOSE_WAIT - after that i can't write to tcp_write, device dont send any more request to a server becouse of state CLOSE_WAIT So how to keep things alive, i tried