Posted: Sat Apr 20, 2019 20:46 Post subject: What do the wifi options in Ath2 do on WRT3200ACM?
I'm trying to figure out what good the options for Ath2 are as it can't really send out a wifi signal. Are they supposed to be global options since the same options can't be found on Ath0 or Ath1? Otherwise, what's the point of having them?
ATH2 is originally for DFS detection, it can be an AP (although it is only a 1x1 configuration). Personally I don't use it. _________________ Tutorial for flashing WRT series WRT Installation,Upgrade & Basic Setup–Cliff Notes
r52242: WRT3200ACM, WRT1200ACv1 & 1 Velop in bridge mode(IoT subnet), r52242 WRT1900ACv1 AP
Velop:2 WHW0101, RE6500, RE9000(AP)
Spectrum - 1000/50
SysLog Watcher 5, New security Onion box coming soon, Fingboxes, PiHoles, NEMS, Cacti, rpisurv
But it's never actually worked as a 1x1. All it can do is receive and monitor. It can't actually send anything out.
It has all of these options that I wish were on the other two useful wifi devices, but it's essentially useless as a wifi.
Joined: 30 May 2017 Posts: 582 Location: Rural Manitoba
Posted: Fri Apr 26, 2019 15:16 Post subject:
D3m0n1q_733rz wrote:
But it's never actually worked as a 1x1. All it can do is receive and monitor. It can't actually send anything out.
It has all of these options that I wish were on the other two useful wifi devices, but it's essentially useless as a wifi.
I tend to differ with your opinion. Ath2 works just fine on Mixed 2.Ghz using a channel not being utilized by either the local 3200 or another router close by. The gui displays do not give true indication of connection and there is no WiFi led on the 3200 for it. I use Ath2 for some of my ESP8266 devices which are close by. The signal strength may not be the best but it does operate about the same as any antenna less router at reduced power output. Due to the weak signal I would not recommend using it for anything that is long range, but as for close devices that fail on Ath1 (ESP8266) and such, it is a definite option. Just keep in mind the channel cross-talk and it works fine. I don't know if it the 5Ghz works well but I suspect it would but because of the reduced power output probably not a good option. _________________ Starlink & DSL -> TPLink TL-R470T+
->
WRT3200acm Master WDS 5GHz 80Mhz CH 100 (+6) r55819
Ath1 2.4Ghz Disabled
99 Static Leases
ExpressVPN
WRT3200acm r55819 WDS Station 5Ghz
Ath1 AP N/G Mixed Channel 11 HT40
WRT1900Ac V1 5Ghz r55819 WDS Station
(Defective, no 2.4Ghz but 5Ghz works great)
WRT1900AC V1 5Ghz AC 80Mhz WDS Station r55819
2.4Ghz AP Ch1 HT20 Mixed
WRT1900ACS SPARE r54914
WRT1900AC SPARE r54914
WRT1900AC V1 5Ghz AC 80Mhz WDS-AP r55819
2.4Ghz AP Ch1 HT20 Mixed
WRT54G DD-WRT v3.0-r37305 micro AP CH 6 Mixed - Not in use
Hmm, interesting.
Here's my setup and maybe you can tell me what might be causing it to not show.
Ath0 as 5Ghz 802.11ac only AP using WPA3
Ath1 as a 2.5Ghz 802.11n only client receiving from CH4
Ath2 as a 2.5Ghz 802.11g/n mixed AP to connect a secondary network from my housemates on CH6 which will show for a split second on reboot and then disappear upon connection of Ath0 as client.
There are also a plethora of other settings for Ath2 that aren't showing for Ath0 or Ath1, but nobody seems to be addressing why these are so other than myself.
But, from what I can tell, Ath2 doesn't seem to work when Ath0 is connected to anything which seems to indicate that the settings are somehow tied together.
So, if they are tied together, wouldn't that make many of the advanced Ath2 settings global since it's the only wifi with those settings now? Or is that like a small oversight where they were either supposed to be available for all three individually or all removed?
I used to use a lot of those settings and it would really help if I could get Ath2 fixed. But it's just outright irritating me how I can see it at boot, but it poofs on connection of Ath0 to the main AP across the house.
Joined: 30 May 2017 Posts: 582 Location: Rural Manitoba
Posted: Sun Apr 28, 2019 0:16 Post subject:
D3m0n1q_733rz wrote:
Hmm, interesting.
Here's my setup and maybe you can tell me what might be causing it to not show.
Ath0 as 5Ghz 802.11ac only AP using WPA3
Ath1 as a 2.5Ghz 802.11n only client receiving from CH4
Ath2 as a 2.5Ghz 802.11g/n mixed AP to connect a secondary network from my housemates on CH6 which will show for a split second on reboot and then disappear upon connection of Ath0 as client.
There are also a plethora of other settings for Ath2 that aren't showing for Ath0 or Ath1, but nobody seems to be addressing why these are so other than myself.
But, from what I can tell, Ath2 doesn't seem to work when Ath0 is connected to anything which seems to indicate that the settings are somehow tied together.
So, if they are tied together, wouldn't that make many of the advanced Ath2 settings global since it's the only wifi with those settings now? Or is that like a small oversight where they were either supposed to be available for all three individually or all removed?
I used to use a lot of those settings and it would really help if I could get Ath2 fixed. But it's just outright irritating me how I can see it at boot, but it poofs on connection of Ath0 to the main AP across the house.
I use a similar setup but my Master-Client link is on 5Ghz. But that should not matter.
Two things I see wrong with your setup;
You need to change the mode to mixed as the N/G mixed seems to be 5Ghz related. I did a test on my client router and as soon as I changed the mode to N/G mixed it stopped working.
You also need to select your channels to avoid crosstack, even at 20Mhz width your two 2.4Ghz are fighting each other. Remember that channel width on 2.4Ghz is only 5Mhz therefore any selection will encompass 4 channels.
Also as I said previously, the GUI will not show the status of connected devices on Ath2. You need to verify with actual device connection or a scanner program such as Acrylic which would also help with avoiding cross-channeling and allowing better selection of channel.
Let me know how you make out, and if you still encounter problems since I can possibly simulate your setup. _________________ Starlink & DSL -> TPLink TL-R470T+
->
WRT3200acm Master WDS 5GHz 80Mhz CH 100 (+6) r55819
Ath1 2.4Ghz Disabled
99 Static Leases
ExpressVPN
WRT3200acm r55819 WDS Station 5Ghz
Ath1 AP N/G Mixed Channel 11 HT40
WRT1900Ac V1 5Ghz r55819 WDS Station
(Defective, no 2.4Ghz but 5Ghz works great)
WRT1900AC V1 5Ghz AC 80Mhz WDS Station r55819
2.4Ghz AP Ch1 HT20 Mixed
WRT1900ACS SPARE r54914
WRT1900AC SPARE r54914
WRT1900AC V1 5Ghz AC 80Mhz WDS-AP r55819
2.4Ghz AP Ch1 HT20 Mixed
WRT54G DD-WRT v3.0-r37305 micro AP CH 6 Mixed - Not in use
Alright, so I changed the settings from mixed G/N 2.4 Ghz to just mixed (B/G/N) 2.4 Ghz and my phone finally sees it and connects to it.
Though, I have to use crossed channels here due to the Ch 11 having noise from a neighbor's router causing issues with everybody else using the channel and there's really no use trying not to cross channels with anyone at this point. As long as the two chips see each other, they can avoid collisions pretty decently in hardware. It's when you have devices that can't see each other talking to the same router at the same time that issues happen.
Anyway, thank you for letting me know about this odd little bug that requires 802.11b to be enabled in mixed mode with the others.
From what I can tell, this may be a part of the GUI bug I've been trying to have someone look at. It's on the same page anyway. If the selections are sending the wrong information to the system for settings as a sort of result of it, then it would explain why mixed is the only setting that works since it's at the top of the drop-down list.
I know that it seems unrelated that something being at the top of a drop-down list may be the only thing that works while everything else doesn't, but it's a common coding error.
Well, I'll just consider this resolved-ish as a bug.
