Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
About GraphiteJess
GraphiteJess
New here
Member since Dec 10, 2019
Dec 10 2019
Community Record
11
Posts
0
Kudos
0
Solutions
Badges
Dec 10 2019
11:33 AM
Well, it didn't work before, either. If this all fails, I might try rolling a plain old 24 and see if it plays nice. Cisco support just asked for the same pcap I just sent them, so... not holding my breath there.
... View more
Dec 10 2019
11:10 AM
You'd think so, but it was at 14 before, because whoever intiially set up this network decided that fourteen computers and half a dozen phones needed 64k IP addresses. It is possible it can only do some mask bits? That seems pretty.... odd.
... View more
Dec 10 2019
10:57 AM
Whelp, back to static and waiting for another restart. Why is the MX giving out the wrong mask? If this fixes the problem, imma be pissy about it.
... View more
Dec 10 2019
10:48 AM
I just got a restart on the PLC, and it getting the wrong mask from the DHCP server. The VLAN is supposed to be 10.24.0.0/23, but the mask it's getting from DHCP is 255.255.252.0, when it should be 255.255.254.0, right?
... View more
Dec 10 2019
10:39 AM
Dynamic ARP appears to be a switch setting, not the MX, and the PLC is plugged directly into the MX. I can ping the Client VPN machine from a computer on the default VLAN.
... View more
Dec 10 2019
9:48 AM
Yup. In addition to a number of security devices, other PC's, etc, and I have no issue hitting any of them.
... View more
Dec 10 2019
9:47 AM
We've been over it a few times, though I'm not sure the mask is set correctly; they have reserved IP's if they're getting it via DHCP, though I'm pretty sure we configured them manually. It sucks because they have to be restarted when IP configs change, and they're currently running normal operations, so I can't just reboot them without causing issues with the business.
... View more
Dec 10 2019
9:32 AM
When the PLC programmer is in the office, he IS on the same VLAN, and can do what he needs to do. When he's remote and on the VPN, he can't.
... View more
Dec 10 2019
9:16 AM
Yes. In desperation I connected to a local printer and sent a help note over the VPN; printed no problem. Based on what I'm seeing from Wireshark, it looks like the PLCs want to run things layer 2 with ARP requests. When I attempt to ping the PLC, the MX ARPs for the PLC IP, and the PLC arps a response. When the PLC ARPs for my computer's IP on the VPN, it does NOT get a response from the MX.
... View more
Dec 10 2019
9:14 AM
It is. I have no problems hitting the rest of the resources on the default VLAN. The gateway on the PLC is set to the IP of the MX on the Default VLAN. I've expressly permitted all traffic between the VLANS via the Firewall interface, but I can't set static routes on either, as it appears to not be an option; the MX complains about overlap.
... View more
Dec 10 2019
6:54 AM
Hello all, I'm a technician for an MSP provider, and we recently inherited a client with all Meraki gear. Their former MSP handed over control of the network, and by and large, it has been bulletproof. However, the client's industrial automation guy installed some new PLC's for their microwave controllers, and we're unable to work with them over the VPN. When you're on the default VLAN, in the building, there are no issues. As soon as you use a remote connection and are connected via the VPN, nothing. No web interfaces, lost pings, etc. I've even gone as far as opening up huge holes in the firewall. I've just settled in to review Cisco's CIP information, but this all seems relegated to their switches, rather than any Meraki gear, so I worry that these devices aren't ever going to work correctly on the network. I would appreciate any info about Meraki and Common Industrial Protocol, or Allen-Bradley/Rockweel PLC's in particular. Given my google results on these items, it feels like a long shot.
... View more
© 2025 Cisco Systems, Inc.
