Is your PC connected by ethernet or wifi? If wifi, is it 2.4 or 5G?
Are you unable (due to physical constraints) to connect the Mi3g via ethernet instead of wifi? connecting by wire is almost always better.
Is your PC connected by ethernet or wifi? If wifi, is it 2.4 or 5G?
Are you unable (due to physical constraints) to connect the Mi3g via ethernet instead of wifi? connecting by wire is almost always better.
It's connected through the ethernet cable.
Its exactly that, AX3600 is so huge, and I don't have any space left in the stand I put the routers because of it.
So, you could make a backup of your current config and then reset the Mi3g to defaults and reconfigure manually... just in case there is some odd setting that was messed up. But I'm grasping at straws here.
Well, restore to default and the only thing I did was connect to the wifi through the 5ghz.
Same still happened, can't acess it, this is so odd! Only happens on the 5ghz wifi.
Too bad client bridge is not supported in OpenWrt easily.
But the client bridge is not needed here... the device in question is simply acting as a host with services (i.e. NAS/fileshare)... client bridging doesn't really matter.
I doubt that matters. Everything gets simplified when not doing double NAT
There is no double NAT here. Sure, the old mi3g does have a lan, but it's not being used, and there are no hosts behind it. Therefore, no real issues with double nat (the router itself is not double-nat'd, only hosts that sit behind it would be, but there are none).
I have somewhere on this forum read that ath11k used in Mi AiOT AX3600 has some issue with broadcast and multicast traffic. Can you temporarily enable "Multi To Unicast" on the main router's 5Ghz wifi settings and see if helps.
Can you also try pinging your PC from the Mi3G and then within 30 seconds pinging it back from your PC?
Well, with Multi to Unicast on MI3G becomes visible to other devices in my main router. Should I leave this on then? Does it break something? Not familiar with this option.
You can leave that option on. Then when you upgrade to a new version, you can test if it works without the option.
The option is mainly made for when you are streaming multicast traffic over wifi (such as ISP provided non-OTT IPTV services). Ordinarily, WiFi sends multicast and broadcast traffic in the AP -> Station direction using shared encryption key and using the slowest modulation rate (6Mbps), which is not enough to stream an HD channel, but is enough in most cases for ARP, NDP, mDNS and similar discovery protocols.
Qualcomm-Atheros wifi chips starting with AC ones require proprietary firmware to be uploaded to the wifi chip on boot to work. Qualcomm-Atheros uses ath5k for 802.11g/a devices, ath9k for 11n, ath10k for 11ac and ath11k for 11ax. ath5k, ath9k and ath10k work fine and I haven't seen these kinds of issues, while ath11k is relatively new and vendor's firmware is not yet as stable as it should be.
Multicast to Unicast instead provides an option to send Multicast and Broadcast to each station individually, which sends more data, but at a faster rate, so depending on the number of wifi stations it is more-or-less equivalent in air time use, and you won't notice a difference. But it works around the bug you are experiencing with the driver and the firmware.
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.