Community Record
18
Posts
4
Kudos
1
Solution
Badges
Oct 17 2019
8:50 AM
1 Kudo
SOLVED! Because the other device that I have in my network had always connected properly to its phone app whether or not WiFi was turned-on as long as cellular was on and vice-versa, I refused to consider outside-my-normal pattern of thinking that things ought to work if I simply add port-forwarding to the raspberry pi in an analogous manner. But adding the pi seemed to "break" that internal routing from apps-inside-network to devices (including pi) in network. I finally broke down and captured packets and analyzed with wireshark. I'm pretty rusty with that tool, but what I discovered looked like a double-nat issue (My MX is in a DMZ on a google fiber box). Hence, I added port forwarding (in addition to the DMZ), and now all is well! I do admit that I am still baffled why it worked for the other device in my network - it has for years! But I am happy that all is working, and I apologize for not having done more diligence (wireshark) before posting in the first place. An ever-exuberant Meraki fan! -Mike
... View more
Jul 22 2019
9:08 PM
Hello Not ideal but still we don’t have choice as “Meraki Authentication” 802.1x is not supported on WiFi capable device MX or Z. We have no other way then to add an MR AP ... even if it double the cost . Any improvements in the roadmap planned ? Adding an Extra MS for a small office is really overkill
... View more
@MOT Don´t worry, this has happened to me too. Kudos to @BrechtSchamp for being fastest.
... View more
My Accepted Solutions
Subject | Views | Posted |
---|---|---|
4422 | Oct 17 2019 8:50 AM |
My Top Kudoed Posts