summaryrefslogtreecommitdiffstats
path: root/src/drivers/net
diff options
context:
space:
mode:
authorMichael Brown2016-06-10 18:27:06 +0200
committerMichael Brown2016-06-13 10:58:32 +0200
commit188789eb3cb83496bd48847da59c74e3f06d413e (patch)
treedd8a3c84cee64fdf783664f4824a5455fa73a4f7 /src/drivers/net
parent[tg3] Fix address truncation bug on 64-bit machines (diff)
downloadipxe-188789eb3cb83496bd48847da59c74e3f06d413e.tar.gz
ipxe-188789eb3cb83496bd48847da59c74e3f06d413e.tar.xz
ipxe-188789eb3cb83496bd48847da59c74e3f06d413e.zip
[tcp] Send TCP keepalives on idle established connections
In some circumstances, intermediate devices may lose state in a way that temporarily prevents the successful delivery of packets from a TCP peer. For example, a firewall may drop a NAT forwarding table entry. Since iPXE spends most of its time downloading files (and hence purely receiving data, sending only TCP ACKs), this can easily happen in a situation in which there is no reason for iPXE's TCP stack to generate any retransmissions. The temporary loss of connectivity can therefore effectively become permanent. Work around this problem by sending TCP keepalives after a period of inactivity on an established connection. TCP keepalives usually send a single garbage byte in sequence number space that has already been ACKed by the peer. Since we do not need to elicit a response from the peer, we instead send pure ACKs (with no garbage data) in order to keep the transmit code path simple. Originally-implemented-by: Ladi Prosek <lprosek@redhat.com> Debugged-by: Ladi Prosek <lprosek@redhat.com> Signed-off-by: Michael Brown <mcb30@ipxe.org>
Diffstat (limited to 'src/drivers/net')
0 files changed, 0 insertions, 0 deletions