Date: Sat, 10 Sep 2005 10:50:17 -0700 (PDT) From: Cheng Jin <chengjin@cs.caltech.edu> To: Leonidas Tsampros <ltsampros@upnet.gr> Cc: freebsd-questions@freebsd.org Subject: Re: ipfw out xmit trouble Message-ID: <Pine.LNX.4.60.0509101046370.5533@orchestra.cs.caltech.edu> In-Reply-To: <20050910145147.GA3028@bifteki.lan> References: <Pine.LNX.4.60.0509100029001.19120@orchestra.cs.caltech.edu> <20050910145147.GA3028@bifteki.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
Thanks, Leonidas. > According to the FreeBSD Handbook, Chapter 26.5 you have to set the > following sysctl variables in order to enable bridging support: > > net.link.ether.bridge.enable=1 > net.link.ether.bridge.config=xl0,fxp0 > net.link.ether.bridge_ipfw=1 The bridge.ko is loaded via /boot/loader.conf, and both bridge.enabled and bridge.config are set via /etc/sysctl.conf bridge_ipfw is set in my script that was shown in the original e-mail. dummynet.ko is also loaded via /boot/loader.conf. I believe I have all the necessary ko's loaded and configs set. Otherwise, the second pipe wouldnt have worked. > Also you must have recompiled your kernel to include "options BRIDGE". > (you can also load the bridge.ko module with "kldload bridge") Yes, I loaded the ko at start-up. This thing just seems strange to me. Maybe there is something about bridging that I don't understand. Cheng
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.LNX.4.60.0509101046370.5533>