Date: Thu, 24 Aug 2000 16:03:57 -0700 (PDT) From: Doug Ambrisko <ambrisko@whistle.com> To: freebsd-net@FreeBSD.ORG Subject: Re: "poor man's bridging" Message-ID: <200008242303.QAA72511@whistle.com> In-Reply-To: <200008242140.OAA02091@bubba.whistle.com> from Archie Cobbs at "Aug 24, 2000 02:40:11 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
Archie Cobbs writes:
| On the topic of bridging..
|
| Just use something like this script..
|
| #!/bin/sh
|
| # Replace with your interface names
| IF1="de0"
| IF2="de1"
|
| kldstat -v | grep -wq ng_ether || kldload ng_ether
| ngctl connect ${IF1}: ${IF2}: lower lower
| ngctl msg ${IF1}: setautosrc 0
| ngctl msg ${IF2}: setautosrc 0
| ngctl msg ${IF1}: setpromisc 1
| ngctl msg ${IF2}: setpromisc 1
| ifconfig ${IF1} up
| ifconfig ${IF2} up
BTW we are doing this instead of bridging for bridging vmware onto a
physical wire. No panics and it works. With bridging I also couldn't
bridge the interfaces I wanted. I have five Nics in the box and didn't
want them all bridged. Doing the cluster thing didn't seem to work at all.
Note that until something opens the "tap" interface it doesn't
exist under ifconfig -a. So I do a dd if=/dev/vmnet0 bs=1 count=0 of=/dev/null
to make it appear first. Then run the above connecting dc0 & vmnet0 then
it works just fine. This also has an advantage that the packets don't
hit the host's IP stack which is what I needed since the host is on a
different "control" network and I need it to go out of the host and
then back in via a router (or our product).
Now if I could only run multiple vmwares.
Doug A.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200008242303.QAA72511>