I'm not actually having a problem right now, but I have observed something particularly strange on my firmware. Or... maybe it's not the firmware? I don't know... I really don't.
Aside from the fact that 5GHz ranges from unusable to unstable right now, I've found some sort of oddity with how different browsers are able to "read" settings from the firmware. Specifically, the wireless channels on the 5GHz frequency.
To my knowledge, valid wireless channels for the 5 GHz frequency go from 36-165. However, I tend to only see 36-161 on the router's interface. So imagine my surprise when I decide to use Internet Explorer to view the GUI and channel 165 joins the party.
I typically try to connect to the highest frequency available, hence, I set it to use channel 165. My 5GHz connection has been more stable than usual lately, but I decided to tinker around and checked the link rate and found it at 144 Mbps. Whaaa? Where did my 300 Mbps go?
As far as I can tell, my alleged channel 165 can only be used at 20MHz, and furthermore, I have it set to use ONLY 40MHz on the 5GHz frequency. So it more or less ignored my setting.
While that's interesting in itself. I went and tinkered a bit more to find that channel 165 apparently doesn't exist. At least... not in Google Chrome. I double checked to be sure channel 165 was set, and sure enough, it is according to IE. Just out of curiosity, I decided to see what Firefox had to say about it and found another surprise. My channel is set to Auto. ..... Wait, what?
So what I've come to find is this:
Google Chrome - Channel 165 doesn't exist. The channel is literally blank.
Internet Explorer - Channel 165 not only exists, it gives me a "stable" 5GHz connection
Firefox - Channel 165 doesn't exist, but the channel isn't blank, it says "Auto."
So somehow, my 1 setting is actually 3 different settings on 3 different browsers.
Still following me? Good. Because I'm not done confusing you.
Apparently, not only is my one setting actually three different settings and not actually at 40MHz, but instead at 20MHz, all 3 of the browsers are telling a lie according to inSSIDer. Not only does inSSIDer not see ANY connections on channel 165, it doesn't see any beyond channel 36. And the one connection on channel 36 is mine. You know... the one that's on channel 165, blank, and auto at the same time. Also, literally, no channel immediately below or anywhere beyond 36 is occupied, more or less confirming what I said earlier. I'm connected at 20MHz despite explicitly setting it to only connect at 40MHz.
Fortunately I can just set it to channel 161 and everything looks normal, otherwise this would be frustrating instead of humorous. But just in case somebody actually cares and wants to look into this, I thought I'd share.
Oh, and this nonsense is sponsored by firmware 3.0.0.4.370. I'm not sure whether or not it happened in .354 honestly, but I wouldn't be awfully surprised if it did.
Aside from the fact that 5GHz ranges from unusable to unstable right now, I've found some sort of oddity with how different browsers are able to "read" settings from the firmware. Specifically, the wireless channels on the 5GHz frequency.
To my knowledge, valid wireless channels for the 5 GHz frequency go from 36-165. However, I tend to only see 36-161 on the router's interface. So imagine my surprise when I decide to use Internet Explorer to view the GUI and channel 165 joins the party.
I typically try to connect to the highest frequency available, hence, I set it to use channel 165. My 5GHz connection has been more stable than usual lately, but I decided to tinker around and checked the link rate and found it at 144 Mbps. Whaaa? Where did my 300 Mbps go?
As far as I can tell, my alleged channel 165 can only be used at 20MHz, and furthermore, I have it set to use ONLY 40MHz on the 5GHz frequency. So it more or less ignored my setting.
While that's interesting in itself. I went and tinkered a bit more to find that channel 165 apparently doesn't exist. At least... not in Google Chrome. I double checked to be sure channel 165 was set, and sure enough, it is according to IE. Just out of curiosity, I decided to see what Firefox had to say about it and found another surprise. My channel is set to Auto. ..... Wait, what?
So what I've come to find is this:
Google Chrome - Channel 165 doesn't exist. The channel is literally blank.
Internet Explorer - Channel 165 not only exists, it gives me a "stable" 5GHz connection
Firefox - Channel 165 doesn't exist, but the channel isn't blank, it says "Auto."
So somehow, my 1 setting is actually 3 different settings on 3 different browsers.
Still following me? Good. Because I'm not done confusing you.
Apparently, not only is my one setting actually three different settings and not actually at 40MHz, but instead at 20MHz, all 3 of the browsers are telling a lie according to inSSIDer. Not only does inSSIDer not see ANY connections on channel 165, it doesn't see any beyond channel 36. And the one connection on channel 36 is mine. You know... the one that's on channel 165, blank, and auto at the same time. Also, literally, no channel immediately below or anywhere beyond 36 is occupied, more or less confirming what I said earlier. I'm connected at 20MHz despite explicitly setting it to only connect at 40MHz.
Fortunately I can just set it to channel 161 and everything looks normal, otherwise this would be frustrating instead of humorous. But just in case somebody actually cares and wants to look into this, I thought I'd share.
Oh, and this nonsense is sponsored by firmware 3.0.0.4.370. I'm not sure whether or not it happened in .354 honestly, but I wouldn't be awfully surprised if it did.