Written by meshugga the 29 Feb 08 at 05:46.
Category: Internet & Networking.
Related project:
Nothing/Others.
Status: New
Rationale
Most networking applications don't mind if there are lost packets due to removing the network cable shortly.
Yet, removing the network cable removes the IP from the interface immediately and breaks all running network applications. This doesn't need to be, there could be a grace time and even a popup along the lines of "please plugin your network cable within 10 seconds or chose another network connection on the same network to retain network connections" to make live easier.
If the wired network has any particular security features which require renegotiation they must certainly be renegotiated, but most people are on simple networks where a plucked cable is simply a plucked cable.
So, the idea is sound, even if it requires some added attention.
That aside, it is up to the network etc to make sure that lost connections are authenticated on re-establishment, so the client simply needs to be willing to take part, but if not challenged should be able to remain in the network.
As a network engineer, I am used to being able to ifconfig an interface suitable for a target device, plugging and unplugging that device as required.
Having the interface lose its configuration is a pain, and not what I expect from a Unix system.
Having to edit /etc/network/interfaces every time I wish to select a different local IP (suitable for talking to the target device) is also a pain.
Documentation as to which part of Ubuntu I have to disable to get back normal Unix behaviour would be fine. Killing avahi-daemon didn't do the trick. Is it dhcdbd perhaps?