Wireless ap problem with Asus RT-ac66u
-
While not pfSense issue, use info in reply #1
-
Asus in ap mode.
Cable from pfsense lan(or switch on network) to 1 of the 4 switch ports on asus(not the wan port).
Pfsense lan network 192.168.1.1 , asus static ip 192.168.1.2
This works on my asus and pfsense.
If it is safe i still am investigating, it is stil new to me.Now your lan and wifi is on the same network.
I think it is better to put the asus router on it's own networkcard(or usb to networkcard cable).https://forum.pfsense.org/index.php?topic=81014.0
-
Hi,
I'm back on this issue. I'm starting to think that my problem started just after upgrading to 2.2.2. After I originally built my pfsense box I plugged the asus router (in ap mode) into my switch and had wireless access with no issues. Checking back on when I started this thread, i.e. when my wifi ap issue began was exactly the day I installed the pfsense upgrade. I tried everything to get the asus box to work afterwards but it never would. Note: It will broadcast and you can 'sometimes' connect but it's overheating and chugging so much that no traffic passes.
I waited for a bit, then I pulled out my older WD MyNet900, I plugged it in last night, set it to ap mode. And guess what the same exact issue is occuring, it's running hot. You appear to be able to connect, I even load a webpage, once on my ipad but then the connection times out.
My setup is:
Wifi-AP box –--------------> Switch (zyxel GS1920) <-------------------- PFsense 2.2.2
I'm nervous about downgrading (I made a complete pfsense backup), but I will put money down that my issue will disappear if I do.
Thanks in advance if you have any insight into what's going on here.
-
Perpahs it's time to stop using obviously shitty APs? Your APs overheating are NOT pfSense issue.
-
If you read my last message you would realize that it's exactly related to PFsense. I'll work through this issue better without your input so you will have more time to help other people.
-
Yeah, I did read your message. Shitty AP overheating is still not, and never will be, a pfSense issue.
-
2 different routers who's cpu is pegged at 100% starting the day I upgraded to 2.2.2 - Again, I don't require your assistance, help people elsewhere
-
You have something misconfigured or you have created a network loop or something else. It's not pfSense. Your alleged time coincidence with an upgrade to 2.2.2 is unconvincing evidence.
-
Fair enough, however the same asus unit was working perfectly until that upgrade. I agree it doesn't make sense but I can't find any other cause, especially after testing with another unit.
-
Layer ate brain. What were the results without the managed-switch in between ?
-
The 100% CPU has me thinking layer 2 loop. They're always fun.
-
I will try that next, but for now, downgrading to 2.2.1 has fixed it (although I'm still using the second WD N900 router, I'll test soon with the asus unit to confirm). Not sure why my hardware doesn't like 2.2.2
I have dual wan (cable motorola modems) plugged into a 4 port intel nic on the pfsense unit. The 3rd port from pfsense is plugged into a zyxel GS-1920. The AP is just plugged into the same gs-1920.
The only thing I noticed in the past was that pfsense docs explicitly state to not connect the AP via it's wan port. Even though both asus and wd n900 both explicitly state to connect WITH the wan port to your switch (when the router is in AP mode).
What I found was that it will work barely when plugged to the wan port and works normally with it plugged into a lan port. So I've always had it plugged in via a lan port. Maybe some combo issue between the zyxel swith, intel nic and router are causing the issue with 2.2.2 but I don't even know where to start. For now, I'll stay on 2.2.1
Thanks!
-
The 100% CPU has me thinking layer 2 loop. They're always fun.
Sorry you posted while I was, 2 layer loop? I'm not too familiar, but my zyxel switch is the only managed switch. I have a couple peripheral 8 port d-link switches that are unmanaged, but they aren't interconnected with the ap or the pfsennse box. Both of those are direct to the zyxel. Perhaps this is a configuration issue with the zyxel?
Thanks,
-
Virtually ALL of the documentation on using a consumer router as an AP say plug it into the LAN side because there IS NO AP MODE on most consumer routers.
If your gear has an AP / Bridge mode that bridges the Wi-Fi with the WAN port, then that's the port you need to use. A true AP usually has only ONE port, which is always bridged with the radios.
Sort of up to you to know the capabilities of your specific gear.
Another example that does this is an airport express in bridge mode. The WAN port gets plugged into the LAN in that case.
-
2 layer loop?
Google "layer 2" loop
-
Yes, I understand that, both these routers have AP modes, both say to use the wan port to connect to lan when in AP mode. However, if I do that, I'll speed test with a 300ms ping, dl .5 mb/s and upload .8mb/s. If I move the cable to a lan port my speedtest is 12ms ping, 28mb/s dl and 2.8mb/s upload (same speed as wired, tested on ipad).
-
Sounds like a GREAT question for the Asus guys.
-
True, but either way I don't think it explains why both routers seize up with 2.2.2 and are working fine with 2.2.1 - with no other changes being made.
-
Time for some mirror ports and wireshark.
-
Have you rebooted the Zyxel-1920 yet after pfSense 2.2.2 upgrade ?
