Bug 103419
| Summary: | RFE: add netplug or ifplugd deamons for network cable controlled network activation | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Jef Spaleta <jspaleta> |
| Component: | net-tools | Assignee: | Radek Vokál <rvokal> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 9 | CC: | bos, forresttaylor2000, jaap, julo42, link, mitr |
| Target Milestone: | --- | Keywords: | FutureFeature |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2004-07-29 01:42:21 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Jef Spaleta
2003-08-29 22:21:23 UTC
Installed it and it works find with Fedora Core 1. For more info see also this post to the fedora-devel-list http://www.redhat.com/archives/fedora-devel-list/2003-December/msg00967.html Sorry small typo in previous comment I wanted to say it works fine I'm the netplug developer, and I'll be happy to help with integrating this into FC2, along with providing support in case of problems. Hi folks. As the discussion on fdl seems to really point out a great interrest in that feature i'll be looking into it over the next couple of days. I'll review ifplugd, netplug and whatever i stumble across and let you know here what i'd like to do in FC2. Thanks, Read ya, Phil Sounds good. I'll be working with David Zeuthen to adapt netplug into the GNOME HAL, but I wouldn't hold my breath for that becoming complete enough to use in time for FC2. I think netplug on its own is a decent intermediate step. Re: comment #4 so its been a couple of days Phil, are you ready to tell us what yer looking to do for FC2? or do i get to be surprised by running the test release? Sorry folks, i got pushed down on my priority list week after week. I'll see if i can squeeze it in sometime next week. Read ya, Phil I'd like this functionality as well. I've been using ifplugd for a while in a large corporate environment, and it is invaluable with my laptop. Since Bryan offered to help integrate netplug into FC2, I'd be willing to test it. One thing that I don't like about netplug is that it replaces the ifcfg-eth* scripts. What happens when you add/remove a network card? It looks like you have to manually create/remove the ifcfg-eth?.pre-netplug scripts or reinstall netplug. Bryan, any ideas? With ifplugd, I could add/remove cards without a problem. That can definitely be changed. The reason that it replaces those config files right now is to ensure that interfaces get turned from ONBOOT=yes to ONBOOT=no. That's the only real difference. If your interfaces are already set to ONBOOT=no, it won't do anything. By the way, I think the "right" thing to do would be to teach redhat-config-network about netplug, and allow you to select a policy for pluggable interfaces such that netplug managed them in general. Why exactly do you change the config from ONBOOT=yes to no? Is it so that you can only start them if they are connected? Would netplug still work if all cards were ONBOOT=yes, or does it actually read the ifcfg-eth?.pre-netplug script? I don't recall, to be honest. I think netplugd was getting confused by interfaces that were already up at start time. I'll have to take a look and see. Yeah, see what you can find, and let me know. It's not a bad feature if the network cable is not plugged in at boot. I know I've waited for many minutes while the network scripts timed out on a network card that couldn't get an IP address. You may want to change the start order to something later. netplug starts righ after network, and before PCMCIA. You should be able to make it start right before boot. The problem may be that netplug starts the network even when it is already up. When I installed netplug and started it I got: netplugd: netplugd startup succeeded dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67 dhclient: DHCPACK from 1.2.3.1 dhclient: bound to 1.2.3.4 -- renewal in 263417 seconds. netplugd[6257]: eth0: state INNING pid 6258 exited status 0 If the link is already up when it starts, shouldn't it just listen? In principle, netplug shouldn't do anything if an interface is already up. In practice, it was simpler at the time to just get it to own and manage all interfaces. I don't think it makes much sense to have both the regular init script and netplug try to own an interface. OK, i've looked at ifplugd and netplug and it i'll be including netplug for several reasons: - It's very small (so bugs can be found and fixed quickly and easily) - The author has a real interest in putting it in RH :-) - Code looks good and everything is already prepared for RH inclusion. The question now remains if it should be put into net-tools or iputils, but i think net-tools is really the right place for it. I hope to get a new net-tools package out either tonight or tomorrow and it should hit the development tree in the next few days then. Read ya, Phil Thanks, Phil. I look forward to helping out :-) Please make sure you use v1.2.1 when you're including it. v1.2 doesn't work with ndiswrapper, which seems to be more of an ndiswrapper bug than anything in netplug, but still... netplug 1.2.2 is out, same bat time, same bat channel. netplug 1.2.7 is already in FC2. This bug should be closed. okay im a gonna close the bug as resolved current release since netplug is in net-tools package as stated in the previous comment. |