[Bug 592963] Re: UDEV rules ignored for ethernet (eth*) devices

2012-01-15 Thread Launchpad Bug Tracker
[Expired for udev (Ubuntu) because there has been no activity for 60 days.] ** Changed in: udev (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/592963 Titl

[Bug 592963] Re: UDEV rules ignored for ethernet (eth*) devices

2011-11-16 Thread Peter Hendrickson
I have one machine which is experiencing this problem and I know of another which is having it, too. This is a fairly bad problem with troubling security implications. Imagine a router/firewall setup which allows people access to services internally. If the interfaces are swapped, internal se

[Bug 592963] Re: UDEV rules ignored for ethernet (eth*) devices

2011-10-26 Thread Martin Pitt
Thanks, keeping as "incomplete" for now then. ** Changed in: udev (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/592963 Title: UDEV rules ignored for etherne

[Bug 592963] Re: UDEV rules ignored for ethernet (eth*) devices

2011-10-26 Thread Zakhar
Thanks for the news on this bug. Although I reported it, the correction became of very low priority for me as I solved the problem with "hardware": bought a Gigabyte Ethernet switch ;-) -very useful and not that expensive, around 30€- I would gladly do the test on Oneiric, but Oneiric fails to w

[Bug 592963] Re: UDEV rules ignored for ethernet (eth*) devices

2011-10-26 Thread Martin Pitt
There have been some fixes in the net device renaming part some months ago. Does this still happen with oneiric? ** Changed in: udev (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bug

[Bug 592963] Re: UDEV rules ignored for ethernet (eth*) devices

2010-06-23 Thread Zakhar
I have a clue to this bug (and also a workaround). I tried changing my rules instead of using eth0 and eth1 to using eth1 and eth2 Basically, I didn't change the declaration of eth1, and moved the one of eth0 to eth2. So now what happens. 83:2C starts first, it gets eth0 (eth1 on udev) then the

[Bug 592963] Re: UDEV rules ignored for ethernet (eth*) devices

2010-06-14 Thread Zakhar
Thank's Pedro! I confirm, this is not a yelp bug but a udev bug. My bad for not having checked the category before posting. -- UDEV rules ignored for ethernet (eth*) devices https://bugs.launchpad.net/bugs/592963 You received this bug notification because you are a member of Ubuntu Bugs, which i

[Bug 592963] Re: UDEV rules ignored for ethernet (eth*) devices

2010-06-14 Thread Pedro Villavicencio
not a yelp issue, let's assign it to udev for now. ** Package changed: yelp (Ubuntu) => udev (Ubuntu) -- UDEV rules ignored for ethernet (eth*) devices https://bugs.launchpad.net/bugs/592963 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu

[Bug 592963] Re: UDEV rules ignored for ethernet (eth*) devices

2010-06-12 Thread Zakhar
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/50176430/Dependencies.txt ** Attachment added: "ProcMaps.txt" http://launchpadlibrarian.net/50176431/ProcMaps.txt ** Attachment added: "ProcStatus.txt" http://launchpadlibrarian.net/50176432/ProcStatus.txt -- UDEV r