Re: Implementing IP_SENDIF (like SO_BINDTODEVICE)
From: Bruce M Simpson (bms_at_spc.org)
Date: 10/29/04
- Previous message: Marc Olzheim: "Re: Strange result (EPERM) from a call to connect(2)"
- In reply to: Gleb Smirnoff: "Re: Implementing IP_SENDIF (like SO_BINDTODEVICE)"
- Next in thread: Bruce M Simpson: "Re: Implementing IP_SENDIF (like SO_BINDTODEVICE)"
- Reply: Bruce M Simpson: "Re: Implementing IP_SENDIF (like SO_BINDTODEVICE)"
- Reply: gnn_at_freebsd.org: "Re: Implementing IP_SENDIF (like SO_BINDTODEVICE)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Thu, 28 Oct 2004 15:32:29 -0700 To: Gleb Smirnoff <glebius@freebsd.org>, Julian Elischer <julian@elischer.org>, freebsd-net@freebsd.org
On Thu, Oct 28, 2004 at 03:41:34PM +0400, Gleb Smirnoff wrote:
> ng_device can be attached to "orphans" hook of ng_ether. /dev/ngdX opened
> by dhcpd, and packets processed.
This seems to me like pure configuration overkill. It would require that
people compile and load netgraph to run dhclient, and that the netgraph
graph be created and populated correctly.
> What is benefit to get rid of bpf? What is problem with it?
IPV6_NEXTHOP is intended to support this for IPv6. It doesn't right
now, it returns EAFNOSUPPORT.
Please see my attached game plan.
BMS
- text/plain attachment: ip-unnumbered.txt
- application/pgp-signature attachment: stored
- Previous message: Marc Olzheim: "Re: Strange result (EPERM) from a call to connect(2)"
- In reply to: Gleb Smirnoff: "Re: Implementing IP_SENDIF (like SO_BINDTODEVICE)"
- Next in thread: Bruce M Simpson: "Re: Implementing IP_SENDIF (like SO_BINDTODEVICE)"
- Reply: Bruce M Simpson: "Re: Implementing IP_SENDIF (like SO_BINDTODEVICE)"
- Reply: gnn_at_freebsd.org: "Re: Implementing IP_SENDIF (like SO_BINDTODEVICE)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]