All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fumitoshi UKAI <ukai@debian.or.jp>
To: linux-hotplug@vger.kernel.org
Subject: ignore some specific interfaces, such as non-hotpluggable eth*, ipsec*
Date: Mon, 04 Feb 2002 17:17:37 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-101284314202868@msgid-missing> (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 <david@debian.org>, submitter of Bug#132224, suggests
the following patch.

--- net.agent.orig      Mon Jan 14 11:25:25 2002
+++ net.agent   Sun Feb  3 14:54:51 2002
@@ -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
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

             reply	other threads:[~2002-02-04 17:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-04 17:17 Fumitoshi UKAI [this message]
2002-02-04 21:03 ` ignore some specific interfaces, such as non-hotpluggable eth*, David Brownell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-linux-hotplug-101284314202868@msgid-missing \
    --to=ukai@debian.or.jp \
    --cc=linux-hotplug@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.