Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
MR62 Mesh - No clients can communicate via Ping, SSH, VNC or other common protocols
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2021-10-01
01:20 PM
2021-10-01
01:20 PM
MR62 Mesh - No clients can communicate via Ping, SSH, VNC or other common protocols
Hello,
It seems this a common sympton set (no clinets on the 5ghz, 2.4ghz, or wired lan port can communicate with each other when using the MR62 and a single satellite. Is there some clear instruction on how to enable clients on the plan (wifi AND wired) to communicate with each other with out any restrictions?
Current Config and Symptoms
- The Router is service as a router and not as just a access point.
- All Clients can access internet service over any protocol
- nmap shows no ports open when testing vs another host on the same network
- nmap shows the correct ports open when testing via localhost
PORT STATE SERVICE
22/tcp open ssh
88/tcp open kerberos-sec
5900/tcp open vnc
6666/tcp open irc
Is this some bad OOB box config that is not documented? How does one enable host to host communications on these mesh network routers (that do not have a CLI?!)
Message 1 of 1
Announcements
• What is the difference between WiFi 6 and WiFi 7?
• Yes! WiFi 7 is backwards compatible with other Wifi devices? Learn more