You need to separate your switch Port(s) first: https://www.netgate.com/resources/videos/configuring-netgate-appliance-integrated-switches-on-pfsense-244.html

After that you can do the Setup like in your main office.

-Rico

@sikr did you ever solved this?

@jknott said in Different wifi AC:

For WiFi, the best thing is to have separate access points, so that they can be placed where needed. You can buy access points or use "routers" as APs. However, proper access points often support power over Ethernet, so you don't have to worry about having AC nearby.

Thanks for your reponse.
Regards

I'm using Prolink PRN3001 and TP-Link Archer C20 AC750 Wireless Dual Band. One WAN speed is 50Mbps and other is 30Mbps. In pfsense, I've set them up 1:1 Tier passing via LAN as 'superhighway'. In wired connection I get full 80Mbps speed and only 30Mbps in wireless. I do not even want 80Mbps in wireless. I would be happy even if each get at least 20Mbps simultaneously when in use.
I do have a cheap $6 Ethernet card and old computer. Is that it?

Bumping an old thread. Seems like Unify would be a great way to go if you didn't already have a significant investment in equipment that could easily be converted if FreeBSD got it's act together and supported AC. It's gonna be around for a while longer... why not get some official support on the subject?

I've used a mixture of Unift, Fortigate, Cisco, HPE, Zyxel, TrendNET, Netgear, Ruckus, TPLink... at the end of the day, I would like to use pfSense on the WRT1900AC that I have at home. Why? Cause it's pretty badass. Also cause the guys at Belkin/Linksys actually had talks with Netgate about getting a pfSense distribution together for it and many of it's other devices... but you know what? I'm messing around with DD-WRT because it supports the WiFi. The whole point is if you have an already good device, why not make it better? Unify isn't bad but I really don't see the point in wasting more money on equipment unless you're going for enterprise grade protection... which pfSense already does for free...

Does anyone see what's wrong with this picture? I'll make a new thread with a similar name to bring interest back to the subject, I think it's worth an actual solution.

Damn, now it's work!

So well, just in short, I write two thing about.
Thankfully your nice layout diagram I understand more better your scenario.

First thing I notice is about firewall rules on WIFI, but and LAN as well, something is wrong.
Step one , if you dont'use IPV6 you may will to blocking/disabling this protocol trought System / Advanced / Networking
alt text

Or if you will use IPV6 protocol, please take apart for now and disabing the rules related. Or atleast do the same logic trought interfaces, (ex. if in your lan here ipv4 and ipv6 is detached , why you make ipv4+ipv6 in one at WIFI? this is not consistent according to me)

Step two , You know after restoring pfSense default's rule "Allow LAN to any" under LAN tab, well you need to respect same logic as LAN to WIFI
and set it according, you need to changhe LAn net to WIFI net for this job, and delete your top rule at WIFI "any to any" because this overlaps the right rule below. (right rule if you change it as described above)
for example look my rule below:
alt text

Well after this, now hottest topic, your configuration needs ovpn review according to me.

For avoid some kind of your last problem i advice you to forget bridging at all and set interfaces properly with respective subnet address , dhcp server pool and add "other" routing path under ovpn tunnel configuration, this last done by editing your current tunnel or add new one.

After this I'm absolutley sure you can go trought on internet-
At this stage maybe you miss routing instruction, and bridges will fail under some kind of special scenario like yours.

Because is better live within standard configuration if knowdledge isn't enough.

Unfortunatley I "hate" ovpn's at all :D hehe it's more complex and full of mistery for me, and my defaults in mind is ipsec based protocol, allow me all kind of routing I need between interfaces / wan / interfaces and work easy with easy setup, so if you can do, better forgive ovpn and setup ipsec.

If you love ovpn's stuffs so go to learn more about and find your way.

I would suggest you reconsider the configuration of your setup with pfSense, by following this guide:
https://www.netgate.com/docs/pfsense/wireless/use-an-existing-wireless-router-with-pfsense.html

https://www.netgate.com/docs/pfsense/book/wireless/pfsense-as-an-access-point.html#ieee-802-1x-authentication-wpa-enterprise

@god_bmxes said in Nighthawk X6 WAP issues:

Thank you, it's so far only on my PC but I'll do that as it already has a static set on it.

That should work for a PC too. There are no specific ports set up in that mapping, everything is passed outbound.

Jeff

@jknott Thank you. I need to investigate further as to why these devices are not both being used when in wireless mode.

Forgot to write right away.

The problem solved using Windows Network Diagnostics. After running this tool/app, I was able to connect to Internet from my smartphone. The tool turned out to be a simplest solution. That's all. All the best to netgaters!

P.S. It's is a very strange autoformating of the post... I haven't marked out by another font and haven't used bold face for some text in the main message, here in the thread.

alt text

@stephenw10 I was buy the same adapter m.2 ,

Where is my problem ? Meaby firewall rules ?

@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

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.