--On 24 September 2009 01:40:03 +0200 Marco d'Itri <m...@linux.it> wrote:
When a tun/tap device is added, /lib/udev/net.agent ignores the event,
and the appropriate configuration line in /etc/network/interface is not
executed. Line 70 of net.agent says "these interfaces generate hotplug
events *after* they are brought up", however at least in respect of
tun/tap devices, investigation shows that this is not true.
This is correct, so it looks like the driver was fixed in the past
years.
I am inclined to change net.agent in the next release, but:
- I fear this may break existing configurations
- I cannot think about any really useful use case for configuring
tun/tap devices using ifupdown (i.e. a situation which would be
easier to manage than by just using iproute)
Google suggests a fair number of articles using this /etc/network/interfaces
to make ssh tunneling (with 'ssh -w') work at least semi-automatically
(try a google search for '"/etc/network/interfaces" tun0').
I believe ifup / ifdown will already work (with a static config in
/etc/network/interfaces). They just won't be called automatically
with allow-hotplug lines by udev.
You need this patch to automate it properly. Of course you can cope
with typing 'iproute' etc.. What most people seem to do on debian
is just 'ifup' the interface. As ifup'ing and interface which is
already up does nothing, I think the change should be mostly
harmless.
--
Alex Bligh
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
