Ok then, why isn't it public? How do I abandon a tcp_pcb without any
further activity on it and releasing it ASAP. This is a real-time
embedded system - loss of link is fatal.
I guess because it hasn't been needed, yet. Why do your need to abandon
a pcb ASAP if you lost the link? I would
Bill Auerbach bauerb...@arrayonline.com wrote:
With loss of link being fatal, we stop but we want the PC to reconnect as
quickly as possible and not leave anything taking up resources from the
previous connection.
Bill, I don't want to be picky about this, but I would have thought that trying
Quoting Bill Auerbach bauerb...@arrayonline.com:
Ok then, why isn't it public? How do I abandon a tcp_pcb without any
further activity on it and releasing it ASAP. This is a real-time
embedded system - loss of link is fatal.
I guess because it hasn't been needed, yet. Why do your need to
Quoting Bill Auerbach bauerb...@arrayonline.com:
Ok then, why isn't it public? How do I abandon a tcp_pcb without any
further activity on it and releasing it ASAP. This is a real-time
embedded system - loss of link is fatal.
I guess because it hasn't been needed, yet. Why do your need to
Hello,
Why is tcp_abandon in tcp_impl.h and not tcp.h? I need to abort without
sending an RST . This is for the case of loss of link - there's no point in
trying to send anything when aborting.
Thanks,
Bill
___
lwip-users mailing list
Bill Auerbach bauerb...@arrayonline.com wrote:
Ok then, why isn't it public? How do I abandon a tcp_pcb without any
further activity on it and releasing it ASAP. This is a real-time embedded
system - loss of link is fatal.
I guess because it hasn't been needed, yet. Why do your need to
Kieran Mansley kie...@recoil.org wrote:
Note that this includes the driver clashing with the rest of the stack when
it passes up a received packet; it should be calling netif-input() (and this
should probably be set to tcpip_input() when you create the net if,
Just a tiny correction here
On Sun, Mar 13, 2011 at 7:21 AM, Simon Goldschmidt goldsi...@gmx.de wrote:
Kieran Mansley kie...@recoil.org wrote:
Note that this includes the driver clashing with the rest of the stack
when it passes up a received packet; it should be calling netif-input()
(and this should probably be set
I am trying to debug a tcp error I have with lwip, I have attached a log of
the errors created when
I turn on the TCP_RST_DEBUG debug zone.
These errors occur when serving up a web page ( the 1st few seconds of
loading the page seem fine in Wireshark, but then I get these reset errors
..)
Can
On 6 Mar 2011, at 22:07, Bernard Mentink wrote:
I am trying to debug a tcp error I have with lwip, I have attached a log of
the errors created when
I turn on the TCP_RST_DEBUG debug zone.
These errors occur when serving up a web page ( the 1st few seconds of
loading the page seem fine
10 matches
Mail list logo
