Date: Wed, 02 Jun 1999 18:47:29 +0200 From: Erik de Zeeuw <erik@univ-lehavre.fr> To: freebsd-questions@freebsd.org Subject: Can't get BRIDGE working Message-ID: <37556021.E2C6FE6C@univ-lehavre.fr>
next in thread | raw e-mail | index | archive | help
Hi I already posted a message that sounds like this one, but I didn't get my FreeBSD bridge to work, so I try a second time :) Here's the situation. The box is a PC Pentium 233Mhz, 32Mb RAM, 1.6Go HD, with 2 ethernet cards, for now these are some SMC EZ Card 10/100, wich are working fine despite FreeBSD tells me they are Accton ones :) Here's the story : I'm compiling a new kernel, say MYBRIDGE, with just appending the line : options BRIDGE to the config file. Then I'm doing the config MYBRIDGE, then change to the correct directory, and launch the compilation with make depend, make, make install. Everything compiles Ok. And at the next reboot, I have the bridge informations : BRIDGE 981214, have 7 interfaces -- index 1 rl0 type 6 phy 0 addrl 6 addr 00.e0.29.2d.1b.f9 -- index 2 rl1 type 6 phy 0 addrl 6 addr 00.e0.29.2d.1c.11 For now, everything is just fine. But when I enable the bridge with sysctl -w net.link.ether.bridge=1, there's simply no bridging done. The only machine that have access to both side is the FreeBSD bridge itself. None of the machines from either sides can talk to each other. The story is a bit longer, as I explored several solutions, still ending with the problem above. I started with two NE2000 cards, wich make use of the ed driver, but it gave me the same results. Someone told me the bridging code was not there in 3.1-RELEASE, which was the version I was using at that time. But since I tried 3.1-STABLE, with the bridging code, 2.2.8-STABLE, 2.2.8-RELEASE, 3.2-RELEASE. Each of them with some patch I found on the dummynet home page. I also tried to enable DUMMYNET & IPFIREWALL, with the right config options ( IPFIREWALL_DEFAULT_TO_ACCEPT ), and with rules that cannot block anything. This one was pointed to me by someone, and I indeed found that previous versions of the bridging code required DUMMYNET & IPFIREWALL. I decided today to use the SMC cards, but it stills does not bridge anything, except for the packets sent by the bridge itself. There's one thing that sounds funny. I grabbed PicoBSD, a nice little disk with a complete FreeBSD on it. And I just have to boot on the PicoBSD disk to have my bridge working ... It works just fine with either the ne2000 or the smc cards. That sounds like I'm missing something to get the bridge work out of my kernel compilation. I had a look at PicoBSD and it has some sysctl variables I don't have ( net.link.ether.bridge_ipfw_drop for example ), and wich I can't find anywhere in all the sources I've tested. May be I missed some details, so I ask people who have working FreeBSD bridges to give me some help on that subject :) Is there anything more to do than enabling BRIDGE in the kernel and using sysctl to make it work ? Do I use some bad versions ? Is there any magic to do ? :) As I'm not on the list, thanks for sending some kind of CC to me with your answer/flames.˛ Thanks in advance, Erik de Zeeuw, Université du Havre, France. erik@univ-lehavre.fr erik.dezeeuw@wanadoo.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?37556021.E2C6FE6C>