This is partly off-topic except that my LAN consists of 2, sometimes 3
OpenBSD machines.
I've got a little LAN sharing a dial-up modem. I'm running pf, doing NAT to
192.168.0.0/24, running DHCP serving up the IP, gateway, DNS server
addresses, all that's working fine.
Along comes a Kindle Fire which is helpless without WiFi, so I need to make
a WiFi access point. Of the 4 wireless cards I've got, the ones that are
supported by OpenBSD can't be access points (according to their drivers' man
pages). I've got a US Robotics 8054 WiFi router (it was free) which I'd
like to hang off my LAN somehow, except that's not quite what it was made
for. The 8054's got its own internal DHCP server (which can be turned off).
When I use it, it doesn't seem to be passing the gateway and DHCP server
addresses along to the Kindle, just an IP address from its pool. It also
wants to be a router/firewall.
I can go into the Kindle's WiFi settings and manually enter a gateway and
DHCP server addresses (since I know them on my own network). The last time
I got a chance to connect to a public WiFi for an hour, it took me 45
minutes to figure out that it was applying my manual settings to every
potential WiFi network, which of course didn't work.
My goal is to get my WiFi access point working as much like public ones as
possible. If I could configure the 8054 to do that, or else just use it as
a dumb bridge between my LAN and wireless that would be great. I haven't
tried setting up a formal bridge device in /etc but I've spent 3 days trying
about everything else I can think of.
I'm not too concerned about security since I've already got pf running on
the internet side and I'm in a rural area. The 8054 can be secured by WEP,
WPA, MAC address limiting, plus I can just unplug it when I'm not using it.
Knowing how to tell what's being passed by a DHCP server would also help.
The Kindle's not a very good diagnostic tool.
Thanks,
Alan, AB1JX
