@dmack said in pfsense DHCP not passing IP to Dlink Access point: Connected Dlink access point to same switch as psfense Missing a small but important detail : what port do you use on the back of the router ? @dmack said in pfsense DHCP not passing IP to Dlink Access point: wifi clients connect and are assigned IPs, Getting an IP is important. But the DHCP client on your device asked for much more then that. pfSense gives your device (Smapthone, pad, PC) more then just an IP. So, as usual, here we go (presuming a Windows device - but any device gives this information ) : Run ipconfig /all and show us what your wifi device obtained. Btw : If you connect by wire on the back of you D-Links, do you have a connection to the net ? The IP, ok, and the mask ? There should be a DNS : Typically the IP of pfSense . There should be a gateway : Typically IP of pfSense.

so if you have problem in wireless in general, deal with it or buy a separate AP. So, you are saying that FreeBSD, altough is well suited for embeded applications, it is not suited for building a custom AP using pfSense ? There is no single 802.11n card to make it work ? I didn't even mention 802.11ac ...

Thanks johnpos, will let you know - when one finally arrives. My ISP speeds are always less than 100Mbs WAN speeds anyway.

I have had good success pushing OpenVPN form 4G Routers running OpenWRT / LuCi. http://www.proroute.co.uk/proroute-4g-routers/proroute-h685-4g-lte-router/ or; https://comset.com.au/4g-lte-modem-routers-c-65/

A management/orchestration platform is currently only available for tnsr. As far as I know, something like that is planned for pfSense as well. https://www.netgate.com/blog/further-a-roadmap-for-pfsense.html https://www.netgate.com/blog/more-on-aes-ni.html

It uses the Intel XMM 7360 LTE modem. However im not finding it on the list.

Be it pfsense sees or not - freebsd and wifi just not a good fit. if you want to run wifi on your network - get an AP, or use some old soho wifi router you have or pick up for $20 as your wifi. It just not worth the hassle trying to use some wifi card as AP in pfsense. If your trying to get it to work as some wifi connection for psfense to leverage as a client your going to need to look on the compatibility list. https://www.freebsd.org/releases/11.1R/hardware.html#wlan

@derelict thanks for the tip, yup I know that's why I posted it in the general discussion but I don't know why it appears to a different section of the forum.

It's not supported under FreeBSD.

@Chwaee: … second SSID ... different WPA2 password, however I could not put it on a different frequency ... which is super annoying. I think this is either a hardware limitation with the PCIe card, an OS limitation in BSD, or a driver limitation of sorts. Technical suggestion: it's a limitation of the admin to understand how WiFi with multiple SSIDs on the same wireless NIC works. Multi-SSIDs will always be the same channel. It just broadcasts a different SSID simultaneously, which obviously happens on the same frequency/channel. You have already been told that FreeBSD's support for WiFi is "minimal" at best. Keep that in mind before posting something about limited wireless config options or less than expected WiFi throughput and such. Best option is to buy a used Ruckus 7372/7982 on eBay for $40 and forget about all WiFi troubles. Even though you don't wanna hear that. You have been warned…

Sorry for the late reply, work has been crazy busy and I just had a chance to try this.  Set up the NAT in about 5 minutes and it worked perfectly.  Also your  explanation made perfect sense why it wasnt working and how NAT will make it work.  Thanks for your time!

I would, personally, not put the AP on OPT1 but on one of the SG-3100 switch ports so you can put SSIDs on the same broadcast domains as the remaining switch ports if you wish.

Seems to work fine but the main installation I am using is pretty small and all devices can pretty much see both APs all the time. The last WiFi work I did was in a large warehouse a few months ago.  There were 6 APs throughout the building.  There's no way you'd see the APs at one end of the building, from the other.  The place was so large we had to use fibre to connect parts of it.  They have Cisco APs and switches.

Potentially that may be better. The best option is to use an external 3G/4G modem that provides Ethernet such as the Netgear LBxxxx devices. pfSense may support USB tethering from the Jetpack, it depends how it appears when connected. However it will have issues if that interface is assigned and then disconnected. Steve

Late reply but… We can't actually see if it's running in hostap mode from that, it's just off the screenshot on the 'media' line. The interface settings page would be more useful there. Check the system log for errors. Steve

Cheers. This was actually very helpful, thanks for taking the time.

@Birke: did you assign only the vlans as interfaces in pfsense or did you assign the re1 itself too? the unifi-ap uses the settings of the re1-interface for management. means you need to assign an interface to re1 and set up the dhcp for that too. after that you should be able to do a layer3 adoption This is not necessary in the newest controller. You don't need a native vlan. You can assign management vlan in settings for AP without having to assign a native vlan to it. It takes some planning and basic vlan knowledge to configure.