WRAP 2E as Wireless AP



  • I just purchased a WRAP 2E combo from Netgate, and it came preinstalled with m0n0wall, which I don't want.

    I have pfsense on some other WRAP devices(the 3lan 1minipci) and it works great.

    I'm beating my head against the wall with this one, I only have 1 LAN and 1 WLAN(atheros based mPCI card) and want to bridge the two as a wireless AP.

    pfSense forces ath0 to become the WAN interface, which won't allow me to set wireless options, nor will it allow me to bridge with the LAN effectively.

    How can I assign a "dummy" interface to the WAN port(as I don't really even need it) or disable the WAN port so that OPT1 can become the ath0 interface?

    If I have to get into the shell to set this up, i don't have a problem.  I've manually bridged sis0 and ath0 and it works perfectly, just can't use the web interface for anything.

    I'm eager to get this working to use CARP to have all my wireless APs configured identically.



  • From a shell run:

    pfctl -d

    The above will turn off the filter so you can access the webConfigurator from the WAN.  Be aware as soon as you apply a setting it will renable the filter again so you should make all your changes then apply.  If you accidently apply simply rerun the command above again.

    When you are finally finished issue:

    pfctl -e

    To ensure the filter is loaded.



  • I'm guessing this is assuming i tag the sis0 interface as WAN, and the ath0 interface as LAN.  Choosing to bridge the LAN with WAN, will it work?

    Since this sits behind a firewall, and is mainly used for wireless connectivity, will the pfctl -d command stay disabled through a reboot?



  • @jrmann1999:

    I'm guessing this is assuming i tag the sis0 interface as WAN, and the ath0 interface as LAN.  Choosing to bridge the LAN with WAN, will it work?

    Not sure. Give it a try.

    @jrmann1999:

    Since this sits behind a firewall, and is mainly used for wireless connectivity, will the pfctl -d command stay disabled through a reboot?

    It gets reset, but the point of pctl -e is to ensure that it doesn't.



  • should work fine we setup a lan on a vlanof (sis0) for management and the bridge the ath with the sis interface.


Locked