Skip to contentSkip to conversation

conntrack records not going away?

DISCUSSION Tobias DiPasquale 3 participants 7 messages Dec 20, 2004 – Dec 22, 2004

lore
Share & tools
lore
#0 lore raw

Hi all,

We have a box running 2.4.26 (from kernel.org) over here that's serving as a sink for test SMTP traffic. The box sits behind a Linux box that is doing ProxyARP. The weird thing is, sometimes after sending tons of traffic to the sink, conntrack records hang around in the ESTABLISHED state, even though the sink process (the endpoint for the connections in question) has been shut down. Has anyone ever seen this before? TIA :)

Signature · 2 lines
[ Tobias DiPasquale ]
0x636f6465736c696e67657240676d61696c2e636f6d
#1 lore raw
Quoted 9 lines · Tobias DiPasquale

Hi all,

We have a box running 2.4.26 (from kernel.org) over here that's serving as a sink for test SMTP traffic. The box sits behind a Linux box that is doing ProxyARP. The weird thing is, sometimes after sending tons of traffic to the sink, conntrack records hang around in the ESTABLISHED state, even though the sink process (the endpoint for the connections in question) has been shut down. Has anyone ever seen this before? TIA :)

More info: no NAT'ing is going on (the sink box has no firewall rules of any kind and all policies are ACCEPT). I read on an earlier post to some mailing list that this can happen if the application doesn't close the connections in the proper way. I will try to capture the packets and see what could be the issue in that respect.

Signature · 2 lines
[ Tobias DiPasquale ]
0x636f6465736c696e67657240676d61696c2e636f6d
#2 lore raw
In reply to Tobias DiPasquale
Quoted 9 lines · Tobias DiPasquale

Hi all,

We have a box running 2.4.26 (from kernel.org) over here that's serving as a sink for test SMTP traffic. The box sits behind a Linux box that is doing ProxyARP. The weird thing is, sometimes after sending tons of traffic to the sink, conntrack records hang around in the ESTABLISHED state, even though the sink process (the endpoint for the connections in question) has been shut down. Has anyone ever seen this before? TIA :)

once a TCP connection gets to ESTABLISHED [ASSURED] state--it will not be removed from conntrack until it times out (after 5 days by default (432000 seconds)), or one side sends a FIN-ACK packet requesting that the connection be torn down.

it sounds like you're shutting down endpoints after the connections are setup, but before they have a chance to close them.

-j

--
"Ah, beer, my one weakness. My achilles heel, if you will."
--The Simpsons

#3 lore raw

Am Di, den 21.12.2004 schrieb Jason Opperisano um 3:33:

Quoted 11 lines · Tobias DiPasquale
Quoted 9 lines

Hi all,

We have a box running 2.4.26 (from kernel.org) over here that's serving as a sink for test SMTP traffic. The box sits behind a Linux box that is doing ProxyARP. The weird thing is, sometimes after sending tons of traffic to the sink, conntrack records hang around in the ESTABLISHED state, even though the sink process (the endpoint for the connections in question) has been shut down. Has anyone ever seen this before? TIA :)

Quoted 5 lines

once a TCP connection gets to ESTABLISHED [ASSURED] state--it will not be removed from conntrack until it times out (after 5 days by default (432000 seconds)), or one side sends a FIN-ACK packet requesting that the connection be torn down.

Or a TCP-Reset.

Cheers,

Ralf

Signature · 1 line
Ralf Spenneberg <[email protected]>
#5 lore raw
In reply to Jason Opperisano
Quoted 7 lines · Jason Opperisano

once a TCP connection gets to ESTABLISHED [ASSURED] state--it will not be removed from conntrack until it times out (after 5 days by default (432000 seconds)), or one side sends a FIN-ACK packet requesting that the connection be torn down.

it sounds like you're shutting down endpoints after the connections are setup, but before they have a chance to close them.

I wasn't able to get a capture that expressed this particular problem. Every time I did a capture, the FINs were sent properly and the conntrack records were removed. But I have another question: is what you're telling me above that the kernel will sometimes not correctly close a socket that a process has open when it gets killed? Where is the code in the kernel that governs that behavior? linux/net/ipv4/tcp_*?

Signature · 2 lines
[ Tobias DiPasquale ]
0x636f6465736c696e67657240676d61696c2e636f6d
#6 lore raw
In reply to Tobias DiPasquale
Quoted 7 lines · Tobias DiPasquale

I wasn't able to get a capture that expressed this particular problem. Every time I did a capture, the FINs were sent properly and the conntrack records were removed. But I have another question: is what you're telling me above that the kernel will sometimes not correctly close a socket that a process has open when it gets killed? Where is the code in the kernel that governs that behavior? linux/net/ipv4/tcp_*?

um--requesting the socket to be closed is the job of the application. when apps crash, processes die, cables get unplugged, power goes out--connections do not get shut down gracefully and get stuck in your firewall connection table. i'm not telling you the kernel isn't doing its job. i was saying that either the application isn't doing its job or a person between the application and the firewall isn't letting the application do its job.

-j

--
"Getting out of jury duty is easy. The trick is to say you're
prejudiced against all races."
--The Simpsons