mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bernd Petrovitsch <bernd@firmix.at>
To: Alex Riesen <raa.lkml@gmail.com>
Cc: linux lover <linux.lover2004@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: loading modules at kernel startup
Date: Tue, 21 Dec 2004 11:13:25 +0100	[thread overview]
Message-ID: <1103624005.31674.10.camel@tara.firmix.at> (raw)
In-Reply-To: <81b0412b041221013752802fc5@mail.gmail.com>

On Tue, 2004-12-21 at 10:37 +0100, Alex Riesen wrote:
> On Tue, 21 Dec 2004 14:44:23 +0530, linux lover
> <linux.lover2004@gmail.com> wrote:
[...]
> > How to load own kernel modules just after eth0
> > interface is brought up?
> > I want to load kernel module as soon as networking part of kenrel
> > starts.

This usually depends on your distribution.

> Look at udev and hotplug
> 
> > I dont want to loose any packets that travels on my linux
> > machine.
> 
> You'll always loose something: there will be a gap between activating
> of the network interface and running of your module (or sniffer, as it sounds).

Not if you do all on "activating the network interface" except "ip link
set eth<x> up".
Usually this means patching your distributions network startup scripts
and/or hooking in the firewall-rule-startup-script (where you basically
have the same problem).

	Bernd
-- 
Firmix Software GmbH                   http://www.firmix.at/
mobil: +43 664 4416156                 fax: +43 1 7890849-55
          Embedded Linux Development and Services


  parent reply	other threads:[~2004-12-21 10:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-21  9:14 linux lover
2004-12-21  9:37 ` Alex Riesen
2004-12-21 10:04   ` linux lover
2004-12-21 10:13   ` Bernd Petrovitsch [this message]
2004-12-21 12:38 ` Jan Engelhardt

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=1103624005.31674.10.camel@tara.firmix.at \
    --to=bernd@firmix.at \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux.lover2004@gmail.com \
    --cc=raa.lkml@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®