ignore some specific interfaces, such as non-hotpluggable eth, ipsec

PATCH Fumitoshi UKAI 2 participants 2 messages Feb 4, 2002

Share & tools

Fumitoshi UKAI

author

2002-02-04 17:17 UTC #0 lore raw

Hi,

I've received some bug reports or wish requests to ignore some specific network interfaces, such as non-hotpluggable eth* or ipsec*. David Engel <[email protected]>, submitter of Bug#132224, suggests the following patch.

net.agent Sun Feb 3 14:54:51 2002 renamed from net.agent.orig Mon Jan 14 11:25:25 2002 +7 -0

@@ -25,6 +25,13 @@
     exit 1
 fi
 
+case $INTERFACE in
+    # interfaces that should be ignored altogether
+    ipsec*)  
+       exit 0
+       ;;
+esac
+
 case $ACTION in
 register)

Although, I think pattern "ipsec*" should be configurable in /etc/default/hotplug (or /etc/sysconfig/hotplug on RedHat, maybe), does it make sense to apply such patch to net.agent?

Thanks,
Fumitoshi UKAI

PS.
See more detail, look at http://bugs.debian.org/hotplug
#108857: hotplug should not invoke ifup ethX for built in interfaces #132224: hotplug should ignor ipsec interfaces

_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

David Brownell

2002-02-04 21:03 UTC #1 lore raw

Re: ignore some specific interfaces, such as non-hotpluggable eth*,

Quoted 3 lines

Although, I think pattern "ipsec*" should be configurable in /etc/default/hotplug (or /etc/sysconfig/hotplug on RedHat, maybe), does it make sense to apply such patch to net.agent?

Until the network device initialization model acquires some consistency, I don't see a better solution than continuing to add more special cases. Which won't work in all cases, but I think that won't be a risk for the "ipsec" interfaces (132224) or ppp ones in the way it would be for "eth" interfaces (108857).

FYI with 108857 I think the bug might best be fixed in the "ifup" code: if hotplug is doing its job, then that any "ifup does modprobe" usage should expect that, and so it should stop after the modprobe -- or find a way to tell hotplug it should _in this case_ ignore that interface.

- Dave

Quoted 1 line

See more detail, look at http://bugs.debian.org/hotplug

Some of those might better be redirected upstream, to the sf.net linux-hotplug bug database ... :)

Quoted 2 lines

#108857: hotplug should not invoke ifup ethX for built in interfaces #132224: hotplug should ignor ipsec interfaces