On Aug 12, 2004, at 5:49 AM, Jason Opperisano wrote:
Hello There,i'm not an expert on this--but i've seen it posted multiple times on
I'm a complete newbie to OpenBSD - a veteran from FreeBSD attracted by
the green grass of pf for a new firewall. Here's the rub - simple setup
with nic connected to internet, nic connected to subnet, wireless card
bridged to internal subnet. Dhcpd is running, working fine, handing out
licenses on the internal ethernet - but no licenses on the wlan. If I
manually configure a machine on the wireless lan - all is fine...also I
can't ping from one side of the bridge to the other - but both sides
reach the internet and router fine. Attached is a messy (well hacked)
pf.conf
openbsd-misc that your cannot bridge with a wireless nic. you're going to
have to subnet wireless & wired networks and route between them.
http://marc.theaimsgroup.com/?l=openbsd-misc&m=109170776211283&w=2
http://marc.theaimsgroup.com/?l=openbsd-misc&m=108558996927905&w=2
I'm surprised to read this, as bridging to/from a wireless interface from/to an ethernet interface is a standard behavior of the machines which populate my network -- though these are all Apple products. Is there a reason the wireless cards aren't seen as ordinary ethernet interfaces by OpenBSD? If you plug a wireless card into a Powerbook, the Powerbook sees it as an ethernet interface and you can treat it just like one for firewall and routing purposes.
Are these posts still accurate? I was considering moving from my existing (workable, but suboptimal) router to a Soekris or the like running OpenBSD, but the inability to make the wireless bridge work would be a nuisance. I have configured a base station to do NAT though, and the user experience is very much like a bridge as far as talking to the Internet goes, I just worry that routing between the 10.0.1.x legs and the 192.1698.1.x legs of the lan might be tricky.
Thanks,
Chris
