Date: Mon, 19 Jan 2004 15:28:25 +0300 From: Andrew Riabtsev <resident@b-o.ru> To: freebsd-net@freebsd.org Subject: Re: netgraph questions on ng_tee, ng_iface, ng_socket Message-ID: <14414573064.20040119152825@b-o.ru> In-Reply-To: <20040119171546.T312-100000@prophet.alphaque.com> References: <20040119171546.T312-100000@prophet.alphaque.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi all,
Monday, January 19, 2004, 12:34:25 PM, you wrote:
DN> hey all,
skiped
DN> i need some understanding on what exactly ng_iface achieves, as it makes a
DN> reference to the hook inet being connected to something. however,
DN> connecting the ng_iface hook inet to ng_ether's upper or lower doesnt make
DN> any sense because ng_ether itself does not do an encasulation of the IP
DN> packet into an ethernet frame. or am i wrong here, and just configuring it
DN> wrongly ?
DN> any pointers/explanations would sure help a lot. thanx in advance.
Connecting ng_iface:inet and ng_ether:upper/lower do nothing, well, it
do something but not what you are waiting for, i think.
As wrotes in man ng_iface:
This node type supports the following hooks:
inet Transmission and reception of IP packets.
ng_iface works with IP-packets, but ng_ether works with ethernet
frames, so connecting it together require at least transformation
module between IP-packets and ether-frames.
--
Andrew mailto:resident@b-o.ru
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14414573064.20040119152825>