Date: Thu, 10 Jul 2003 11:37:15 -0700 From: Luigi Rizzo <rizzo@icir.org> To: kw3wong@engmail.uwaterloo.ca Cc: dsze@engmail.uwaterloo.ca Subject: Re: Question about bridging code Message-ID: <20030710113715.A37895@xorpc.icir.org> In-Reply-To: <1057860615.3f0dac07e1418@www.nexusmail.uwaterloo.ca>; from kw3wong@engmail.uwaterloo.ca on Thu, Jul 10, 2003 at 02:10:15PM -0400 References: <1057778632.3f0c6bc8af474@www.nexusmail.uwaterloo.ca> <20030709195455.A24039@xorpc.icir.org> <1057860615.3f0dac07e1418@www.nexusmail.uwaterloo.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jul 10, 2003 at 02:10:15PM -0400, kw3wong@engmail.uwaterloo.ca wrote: > Hi Luigi, > >Thanks for response, the vmnet/tap stuff sounds like neat stuff. After reading >the description of tap (from the vtun site), the system seems to make a lot of >sense.However, I'm not sure how vmnet comes into play here - what purpose does >it serve, shouldn't I just be able to read from the /dev/tap0 and bridge >between tap0 and fxp0? It's just a naming issue, vmnetX is the network-device name of /dev/tapX. (the ip-equivalent thing, "tun", has the same name for both the network device and the device entry in the filesystem. As a matter of fact the latter is totally arbitrary so "tun" perhaps should be called "vmnet"...) Packets written by a process to /dev/tapX are seen by the network layer as coming from vmnetX; packets sent by the network layer to vmnetX can be read by a process from /dev/tapX > net.link.ether.bridge_cfg: fxp0:0,tap0:0 tap1:1 bge0:1 here you have to use the names vmnet0 and vmnet1 cheers luigi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030710113715.A37895>