From: Ben Greear <greearb@candelatech.com>
To: "'netdev@oss.sgi.com'" <netdev@oss.sgi.com>
Subject: new networking features
Date: Thu, 08 May 2003 10:48:02 -0700 [thread overview]
Message-ID: <3EBA9852.4030808@candelatech.com> (raw)
I have a little collection of networking features that may be of
interest. My patches are against 2.4.20... If anyone thinks any of
these are of interest, I will break them out and send them to the list
for review/inclusion...
1) send-to-self: Add an IOCTL that allows an interface to be configured
so that it will answer arps from other interfaces on the same machine.
Also tweaks ip-v4 a bit.
Allows: can send traffic from one interface to another interface on same machine
over an external network. Tested with ipv4, may automatically work with ipv6
too.
2) 802.1Q VLAN: Add an ioctl that can be used to verify that a device is indeed
an 802.1Q VLAN device (no more relying on name or luck).
3) MAC-VLANs: (Upgraded patch that someone else sent me.) Allows one to specify
VLAN-like devices based on source or destination MAC addresses (no extra padding
in the ethernet frame.)
This requires a hook in the skb-rx logic, near where the bridging logic has it's
hook.
4) Pktgen updates: Allows receiving (and accounting) packets & threading changes. Also requires
a hook in the skb-rx logic. (Dave already said he didn't like it before, and I
assume he still doesn't, but including it here for completeness).
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com> <Ben_Greear AT excite.com>
President of Candela Technologies Inc http://www.candelatech.com
ScryMUD: http://scry.wanfear.com http://scry.wanfear.com/~greear
next reply other threads:[~2003-05-08 17:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-08 17:48 Ben Greear [this message]
2003-05-08 16:44 ` new networking features David S. Miller
2003-05-08 18:00 ` Ben Greear
2003-05-08 16:55 ` David S. Miller
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=3EBA9852.4030808@candelatech.com \
--to=greearb@candelatech.com \
--cc=netdev@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).