Summary: | hotplug doesn't handle tun*/tap* events properly for vpn's | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Jason Cooper <jason+gentoobugs> |
Component: | [OLD] Core system | Assignee: | Greg Kroah-Hartman (RETIRED) <gregkh> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | CC: | base-system |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 145809 | ||
Bug Blocks: |
Description
Jason Cooper
2006-08-26 08:02:50 UTC
This goes against the wishes of other people who wanted the tun/tap interfaces to be handled by that agent... I suggest just not using the hotplug agent at all... (In reply to comment #1) > This goes against the wishes of other people who wanted the tun/tap interfaces > to be handled by that agent... > > I suggest just not using the hotplug agent at all... > Greg, I apologize, I wasn't clear. Lines 40 and 89 of net.agent catch ADD and REMOVE events and then 'exit 0'. My change allows hotplug to detect tap*/tun* events, and instead of exiting, launch the init script, which is what I need. Is there a better way to detect the creation of tun/tap devices and launch the init script? On the same vein, is there a reason hotplug, by default, doesn't handle tun/tap events? thx, Jason. sys-apps/hotplug is useless with any recent udev version, and 2.4 kernels are no longer supported. Unmerge it and move on. WONTFIX. |