On 08/04/2014 02:59 AM, Dan Egli wrote: > Next, the physical segment is both wired (eth1) AND Wireless > (wlan0/ath0/whatever). I don't want to plug in a physical Wi-Fi router, for > various reasons. I just want the server to offer DHCP addresses to anyone > who connects to eth1, or to anyone who connects to wlan0 IF they also have > the correct wpa2_personal key configured. These machines would connect via > simple IP masquerading since there will be no connections originating > outside the network that need to be responded to. Not that dissimilar to a > Wi-Fi router. However, like I said above, I have various reasons for > preferring to not use a separate Wi-Fi router/AP.
I'm unclear as to why you do not want to use a conventional AP. When configured to act as a bridge, with dhcp disabled (no routing), it would act exactly the same as an internal wifi card in host mode, but without having to mess with drivers, many of which are not available on server distros. Just a normal ethernet port would be required. Functionally, and security-wise, the external AP is equivalent to the internal card. And more future proof, and less prone to breakage. Rather than having to mess with restarting things on the server, you can just restart the external AP. Just a suggestion. /* PLUG: http://plug.org, #utah on irc.freenode.net Unsubscribe: http://plug.org/mailman/options/plug Don't fear the penguin. */
