yeah I just found out Karmic has a typo in /etc/init/network-
interface.conf
stop on net-device-removed INTERFACE=$INTERFACE
should be
stop on net-device-remove INTERFACE=$INTERFACE
Furthermore, the DRIVERS var is not filled when the device gets plugged (add
action), resulting in an infinite
yeah I just found out Karmic has a typo in /etc/init/network-
interface.conf
stop on net-device-removed INTERFACE=$INTERFACE
should be
stop on net-device-remove INTERFACE=$INTERFACE
Furthermore, the DRIVERS var is not filled when the device gets plugged (add
action), resulting in an infinite
yeah I just found out Karmic has a typo in /etc/init/network-
interface.conf
stop on net-device-removed INTERFACE=$INTERFACE
should be
stop on net-device-remove INTERFACE=$INTERFACE
Furthermore, the DRIVERS var is not filled when the device gets plugged (add
action), resulting in an infinite
hmm and now I cannot reproduce anymore :-Z
must be lack of coffee..
** Changed in: ifupdown (Ubuntu)
Status: Confirmed = Fix Released
--
udev rule can fail to run ifdown, break reinserting device
https://bugs.launchpad.net/bugs/130437
You received this bug notification because you are a
It looks broken again since I've upgraded to Karmic.
ifupdown 0.6.8ubuntu20 changelog says: Replace the udev rule with a
per-interface Upstart job.
Works again if I put the old udev rule file in /etc/udev/rules.d
--
udev rule can fail to run ifdown, break reinserting device
I can confirm that this is fixed with jaunty, usb networking now works
fine with ifupdown udev script in jaunty.
--
udev rule can fail to run ifdown, break reinserting device
https://bugs.launchpad.net/bugs/130437
You received this bug notification because you are a member of Ubuntu
Bugs, which
This bug was fixed in the package ifupdown - 0.6.8ubuntu18
---
ifupdown (0.6.8ubuntu18) jaunty; urgency=low
* debian/ifupdown.udev: Unconditionally call ifdown when the network
interface is removed, instead of checking DRIVERS which is likely gone
anyway. LP: #130437.
*
the same problem with bluetooth PAN, after client disconecting, bnep0
net remove event reaches 85-ifupdown.rules without DRIVER set. fixed
with:
SUBSYSTEM==net, KERNEL==bnep?*, GOTO=net_start
SUBSYSTEM==net, DRIVERS==?*, GOTO=net_start
GOTO=net_end
...
...
--
udev rule can fail to run
Neither of the fixes works properly on Ibex. Both cause routing and
/etc/resolv.conf to get trashed with incorrect values from usb0 which
has neither a default gateway nor DNS servers defined. The end result is
two default routes in the routing table with the usb0 route having
higher priority than
I confirm seeing this on an uptodate Hardy. The attached fix works.
** Changed in: ifupdown (Ubuntu)
Status: New = Confirmed
--
udev rule can fail to run ifdown, break reinserting device
https://bugs.launchpad.net/bugs/130437
You received this bug notification because you are a member of
As I explained in
https://bugs.edge.launchpad.net/ubuntu/+source/dhcp3/+bug/38140/comments/15,
the fix in comment 7 here is wrong.
Removing the DRIVERS== clause would be better, but it adds some value:
it matches real devices with hardware drivers, and not virtual net
devices like lo.
--
udev
A newer suggestion on the openmoko wiki is to move the label net_end to
be above the remove action. The resulting
/etc/udev/rules.d/85-ifupdown.rules looks like:
SUBSYSTEM==net, DRIVERS==?*, GOTO=net_start
GOTO=net_end
LABEL=net_start
ACTION==add, RUN+=/sbin/start-stop-daemon --start
Hardy beta was released. but it wasn't applied yet. :(
--
udev rule can fail to run ifdown, break reinserting device
https://bugs.launchpad.net/bugs/130437
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Just had a look and in the hardy alpha it seems unchanged.
How about some bug love people!
--
udev rule can fail to run ifdown, break reinserting device
https://bugs.launchpad.net/bugs/130437
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I can also confirm this bug on Gutsy (amd64).
--
udev rule can fail to run ifdown, break reinserting device
https://bugs.launchpad.net/bugs/130437
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Same problem here. Moving the DRIVERS==*? out of the top GOTO, to
ACTION==add line fixes the problem. Though adding --auto to ifupdown
at ACTION==add might improve reliability (?).
--
udev rule can fail to run ifdown, break reinserting device
https://bugs.launchpad.net/bugs/130437
You received
Me too. Gutsy too. See also
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/136470.
--
udev rule can fail to run ifdown, break reinserting device
https://bugs.launchpad.net/bugs/130437
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
I can confirm this on my hardware, a Netgear WG111v2, using the rtl8187
driver.
My workaround was just to remove DRIVERS=?*, since I didn't see how a
network device could appear without a driver anyway. I'd say the real
bug is either in udev or the kernel not providing this information.
An
18 matches
Mail list logo
