Public bug reported:
OS: Lucid 10.04.1 LTS, upgraded from Karmic 9.10
If too much information is sent to an unresponsive network connection,
the connection seems to 'fail' and stops working. The unresponsive
network connection is usually the result of a proxy or NAT router
restarting.
Steps to duplicate in 10.04:
1) set up "ping -f google.com -i 10"
2) set up "ping -f google.com -i 1"
3) restart router
Result: the flood ping with interval 10 will show one or two dropped
packets while the router is restarting, and then will show no further
errors. The flood ping with interval 1 will continue to show dropped
packets after the router has restarted, as too much information is in
the connection buffer or something.
This also applies to IM connections (tested with Pidgin connected to
MSN). If update information is sent while the router is restarting, the
connection to the server 'stalls' and is only reset by the application
after 15 minutes. If no information is sent while the router is
restarting, the connection works fine immediately after the router has
finished restarting and connected to ISP.
Also tested this on 10.04 32-bit from a Live usb. First test with 10-sec
interval stalled when restarting router, but with a 20-sec interval, there was
only one missed packet and then resumed normal operation. Meanwhile the 1-sec
interval ping completely stalled even after the router finished restarting.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: buffer connection overflow pidgin ping
--
Network connections crash from overflow when unresponsive
https://bugs.launchpad.net/bugs/609348
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
