public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick.Holloway@pyrites.org.uk (Nick Holloway)
To: linux-kernel@vger.kernel.org
Subject: Re: dummy ethernet driver
Date: 6 Jan 2003 10:16:54 -0000	[thread overview]
Message-ID: <avbl2m$ros$1@alfie.demon.co.uk> (raw)
In-Reply-To: Pine.LNX.4.44.0301060553260.24333-200000@skynet

airlied@linux.ie (Dave Airlie) writes:
> device but rather a useless one :-), so I patched the dummy so it had an
> address (hardcoded) is broadcast and loops back packets to itself...
> 
> the patch is attached.. is there any reason why the dummy device doesn't
> want to do this stuff? I'm just submitting the patch as a request for
> comments on why this isn't done anyway in the dummy?

[Some background on the dummy driver -- I don't know if there is another
way to configure devices for your purpose, or if your patch is the only
way, I'll leave that for others to answer]

With the way the dummy driver was used, it wasn't necessary to handle
packets.

I wanted my dial-up static IP address to be valid even when the ppp device
was not connected, so I wrote the dummy interface.  If the destination
IP of a packet matches the IP of a local interface, then the packet is
routed over the loopback interface.

So, for this use the dummy interface doesn't need to handle packets, it
just needs to hold an IP address.  In the case that someone configures
the routing tables so that packets are sent via the dummy device, it
just black-holes the packets.

-- 
 `O O'  | Nick.Holloway@pyrites.org.uk
// ^ \\ | http://www.pyrites.org.uk/

  reply	other threads:[~2003-01-06 10:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-06  5:57 dummy ethernet driver Dave Airlie
2003-01-06 10:16 ` Nick Holloway [this message]
2003-01-06 14:54 ` Alan Cox
2003-01-06 22:33   ` Dave Airlie
2003-01-07  6:51     ` Peter Svensson

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='avbl2m$ros$1@alfie.demon.co.uk' \
    --to=nick.holloway@pyrites.org.uk \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox