Bug 17631

Summary:	netgraph is not implemented on loopback iterfaces
Product:	Base System	Reporter:	gnn <gnn>
Component:	kern	Assignee:	Archie Cobbs <archie>
Status:	Closed FIXED
Severity:	Affects Only Me
Priority:	Normal
Version:	Unspecified
Hardware:	Any
OS:	Any

Description gnn 2000-03-28 06:40:01 UTC

Netgraph has a permanent node for every Ethernet interface but
none for loopback.  Loopback would be desirable for those who
wish to use laptops, or to simulate traffic through new nodes
without using an actualy interface.

Fix: 

Add netgraph code to if_loop.c and create an ng_loop.h file in
the sys/netgraph directory.

I will have a patch for this in a week or so.

Comment 1 Johan Karlsson freebsd_committer

2000-08-19 08:26:39 UTC

State Changed
From-To: open->feedback


Can you please send the patches you where talking about as a followup to 
this PR, by sending them in a mail to 'freebsd-gnats-submit@FreeBSD.org' 
with the subject of this mail.

Comment 2 Johan Karlsson freebsd_committer

2000-08-19 08:26:39 UTC

Responsible Changed
From-To: freebsd-bugs->archie

Archie has done some recent commits to this area  
and I belive he is one of the maintainers, true?

Comment 3 Archie Cobbs 2000-08-22 01:10:26 UTC

One thing to think about regarding this bug is: what does a loopback
"packet"
look like? Specifially, how do you determine the protocol? Internally
all loopback
packets are accompianied by a struct sockaddr that determines the
protocol.

For example, on Ethernet, the two byte Ethertype determines the
protocol.

So you'd have to make up some kind of pseudo-header, e.g., like a two
byte
Ethertype, so that ng_loop can figure out what protocol the packet is.
Otherwise
it's just gonna be opaque data.

-Archie

___________________________________________________________________________
Archie Cobbs   *   Whistle Communications, Inc.  *   http://www.whistle.com

Comment 4 Archie Cobbs freebsd_committer

2000-09-18 21:35:20 UTC

State Changed
From-To: feedback->closed

No changes to be made.