> On Apr 12, 2017, at 1:47 PM, Mihai Popescu <mih...@gmail.com> wrote: > > Because of titles like this post there is no clear anymore what > someone is reffering to when one is using words like bridge, switch, > hub, access point, router, ... > Add the IPv6 in the mix and you think you understand the spagetti of internet. > > Bleah, looking again at "non-routing access point". What about the "no > pancake making CPU". > > Sorry for the rant. >
You have a valid point. When one buys a linksys/netgear/whatever “Wireless Access Point”, it is often intended to be a full Internet gateway (router, NAT, DHCP, etc) that also does wifi. For all examples I found for making an OpenBSD access point, the OpenBSD machine is used as the main router/DHCP server/gateway/buzzword on the network. I have a separate machine (currently running pfSense, though I plan on switching it to OpenBSD soon) that is handling the routing/NAT/DHCP/etc functionality on my network. I just want to see if I can make my openbsd machine an access point to this network. I got the hostname.athn0 set up so other devices could connect to it. I then though that just bridging it to the ethernet NIC would make it ‘just work’ - whatever comes in one port goes out the other and vice-versa. It turned out that DHCP requests weren’t going though. I saw a tutorial online that showed enabling the ipforwarding sysctl so i tried that but it made no difference. The suggestion here about turning on relayctld is what made this work for me. I am guessing that OpenBSD does not forward broadcasts over a bridged connection. If there is better terminology for what I am trying to do, I am more than interested in learning it! :) Jordon
