Re: Container networking breaks after a while [message #42974 is a reply to message #42970] |
Thu, 23 June 2011 11:17  |
DavidKnell
Messages: 2 Registered: June 2011 Location: Greece
|
Junior Member |

|
|
An update.
The above isn't strictly correct. A failed container:
- responds to PINGs
- will respond to an inbound SSH connection by opening the TCP connection OK, but won't then go on to try to establish anything above the basic TCP session
- doesn't show anything at all within the container using wireshark
So it looks a bit like there's something hung up half-way up the network stack. netstat shows a bunch of sockets with stuff in their receive queues; these amounts are constant and are sufficient to fill up the container's dgramrcvbuf.
Here's the final weirdness: killing FreeSWITCH within the container fixes things.
--Dave
[Updated on: Thu, 23 June 2011 11:45] Report message to a moderator
|
|
|