From owner-freebsd-net@FreeBSD.ORG Thu Jul 10 19:07:52 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AEAC937B404 for ; Thu, 10 Jul 2003 19:07:52 -0700 (PDT) Received: from www.ambrisko.com (adsl-64-174-51-42.dsl.snfc21.pacbell.net [64.174.51.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 88FAE43FB1 for ; Thu, 10 Jul 2003 19:07:51 -0700 (PDT) (envelope-from ambrisko@www.ambrisko.com) Received: from www.ambrisko.com (localhost [127.0.0.1]) by www.ambrisko.com (8.12.8p1/8.12.8) with ESMTP id h6B27eO7038192; Thu, 10 Jul 2003 19:07:40 -0700 (PDT) (envelope-from ambrisko@www.ambrisko.com) Received: (from ambrisko@localhost) by www.ambrisko.com (8.12.8p1/8.12.8/Submit) id h6B27e6q038191; Thu, 10 Jul 2003 19:07:40 -0700 (PDT) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <200307110207.h6B27e6q038191@www.ambrisko.com> In-Reply-To: <1057865744.3f0dc0103f795@www.nexusmail.uwaterloo.ca> To: kw3wong@engmail.uwaterloo.ca Date: Thu, 10 Jul 2003 19:07:40 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL94b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII cc: freebsd-net@freebsd.org Subject: Re: Question about bridging code X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Jul 2003 02:07:53 -0000 kw3wong@engmail.uwaterloo.ca writes: | > 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"...) | | But when I do a ifconfig, only tapX devices are there, where there is no vmnetX | devices. And when I set up the bridge with vmnetX, the kernel will complain | that the vmnetX devices do not exist. Do I need to perform a makedev on it | first to create the devices? If so, do they have a special major and minor | number that I should assign it to? Yes a different offset of minor number maps into vmnetX: a21p% ls -l /compat/linux/dev/vmnet? crw-r--r-- 1 root wheel 149, 0x00010001 Jul 8 18:34 /compat/linux/dev/vmnet1 crw-r--r-- 1 root wheel 149, 0x00010002 Jul 1 19:20 /compat/linux/dev/vmnet2 crw-r--r-- 1 root wheel 149, 0x00010003 Jul 1 19:20 /compat/linux/dev/vmnet3 crw-r--r-- 1 root wheel 149, 0x00010004 Mar 21 2002 /compat/linux/dev/vmnet4 crw-r--r-- 1 root wheel 149, 0x00010005 May 12 09:26 /compat/linux/dev/vmnet5 crw-r--r-- 1 root wheel 149, 0x00010006 Jun 9 15:45 /compat/linux/dev/vmnet6 crw-r--r-- 1 root wheel 149, 0x00010007 Jun 9 15:45 /compat/linux/dev/vmnet7 crw-r--r-- 1 root wheel 149, 0x00010008 Jan 10 2002 /compat/linux/dev/vmnet8 crw-r--r-- 1 root wheel 149, 0x00010009 Jan 10 2002 /compat/linux/dev/vmnet9 a21p% ls -l /dev/tap? crw------- 1 root network 149, 0 Aug 6 2002 /dev/tap0 crw------- 1 root network 149, 1 Aug 6 2002 /dev/tap1 crw------- 1 root network 149, 2 Aug 6 2002 /dev/tap2 crw------- 1 root network 149, 3 Aug 6 2002 /dev/tap3 crw------- 1 root network 149, 4 Dec 11 2001 /dev/tap4 crw------- 1 root network 149, 5 Dec 11 2001 /dev/tap5 crw------- 1 root network 149, 6 Dec 11 2001 /dev/tap6 crw------- 1 root network 149, 7 Dec 11 2001 /dev/tap7 a21p% Then echo -n > /compat/linux/dev/vmnetX and ifconfig will list it. In -current they just show up. Doug A.