-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MeshChat 2.2 doesn't communicate - new OpenWRT Nightlies 2017+ #590
Comments
2.3 Doesn't seem to pick up on the Correct Zone as set up - continuing to test. |
Attempts to save changes in the Port Forwarding area returns a Bad Gateway message. |
That ones separate from MeshChat :-( |
Try 2.4 |
Version 2.4 appears to be working! |
I may still be experiencing some issues with 2.4 Syncing with Zone. |
Can you attach the support tool data dump? |
Done - this appears to be a one-way outgoing issue from the new Openwrt firmware. I installed 2.4 MeshChat on a TPLink CPE510 and it is working both ways and sees all of the stations within the Zone. |
Looks like MeshChat v2.5 took care of it. Compatability back to units running v2.2 has been tested. Installed on GLINET AR-750 running N-2031. |
No further issues with version 2.5 - closing this issue. |
MeshChat 2.2 does not see or communicate with any stations in Zone when installed on new OpenWRT Nightly 2017+ updates
The text was updated successfully, but these errors were encountered: