Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Become a member of the Cisco Meraki Community today
Get answers from our community of experts in record time.
Join now- About overblower
About overblower
overblower
Here to help
Member since Sep 15, 2025
3 weeks ago
Community Record
14
Posts
3
Kudos
0
Solutions
Badges
3 weeks ago
After I added these clients to the whitelist (allow list), it worked. Only one thing is strange: 143.161.64.217 from D2 can ping 143.161.65.50 from D1. But 143.161.65.50 cannot ping 143.161.64.217.
... View more
3 weeks ago
Yes, but we decided to allow internet access as well. We didn’t apply the policy. So let’s focus on this thread and ignore the other one.
... View more
3 weeks ago
We also noticed that if another client connects to the MX port and sets its IPv4 settings to "automatic," it gets an IP from the MX and is able to reach the internet. However, other computers that we configured with a manual IP are able to ping the other location via VPN, but they are not able to reach the internet.
... View more
3 weeks ago
Hi All, There are two separate MX75 appliances in two different locations. Location D1 MX IP: 143.161.65.1 Clients: 143.161.65.0/24 Location D2 MX IP: 143.161.64.1 Clients: 143.161.64.0/24 The D1 appliance can ping the D2 appliance. The D1 appliance can also ping google.com. The D2 appliance can ping google.com as well. Clients from D1 and D2 can ping each other. However, clients connected to the MX ports cannot ping google.com. They cannot reach the internet. Could you please support us in this case? Thank you in advance
... View more
4 weeks ago
3 Kudos
The group policy is ready. We just need to apply it. We'll test it first over the weekend and then implement it. Thank you very much, @alemabrahao !
... View more
4 weeks ago
Done. By the way, here's the current network setup: D1: Security Appliance IP: 143.161.65.1 Client Subnet: 143.161.65.0/24 D2: Security Appliance IP: 143.161.64.1 Client Subnet: 143.161.64.0/24 I have already created a group policy for D2. As mentioned earlier, my goal is to block internet access for both D1 and D2 clients, while still allowing them to ping each other internally. Current situation: Clients in both D1 and D2 can access the internet and ping each other at the same time. Now it is time to apply it to the VLAN interface ? And any screenshot or steps?
... View more
4 weeks ago
D1: Security Appliance: 143.161.65.1/24 D2 Security Appliance: 143.161.64.1/24
... View more
4 weeks ago
failed. I have two locations, D1 and D2. They should connect to each other, but clients must not have internet access. SCADA programs talk across the two locations.
... View more
4 weeks ago
There is Auto VPN between the locations using MX75, and it works well. I want the devices connected to the MX75 to not access the internet, but still be able to ping other locations. How can I set this up? Thank you in advance.
... View more
Labels:
- Labels:
-
Auto VPN
-
Client VPN
-
Firewall
a month ago
Hi Team, I have 4 MX devices in different locations. Let’s call them A, B, C, and D. Right now, all of them can ping each other. But I only want communication between A-B and C-D. That means devices in A and B should be able to ping each other, and devices in C and D should be able to ping each other. How should I configure this? Br Tayfun
... View more
Labels:
- Labels:
-
Auto VPN
Sep 16 2025
2:32 AM
According to the link, I should do the following steps: Go to Security & SD-WAN > Configure > Site-to-site VPN. Turn on VPN subnet translation. This will make a new VPN subnet column appear for the local networks. But the "VPN Subnet Translation" option mentioned in step 2 does not appear on the page.
... View more
Sep 15 2025
1:31 PM
I want to create two different networks for two different cities. Each city will use the same security appliance (MX75). City 1: They already use the subnet 143.161.64.X. Example: City1 SCADA SERVER-A IP: 143.161.64.16 City1 SCADA SERVER-B IP: 143.161.64.17 City 2: They also use the same subnet 143.161.64.X. Example: City2 SCADA SERVER-A IP: 143.161.64.216 City2 SCADA SERVER-B IP: 143.161.64.217 We want to connect a specific laptop to City 1, and it should use the IP address 143.161.64.50. This laptop should also be able to ping servers located in both City1 and City2. When I try to configure this, I get the error: "The VLAN subnet 143.161.64.0/24 conflicts with a remote VPN subnet on the network City1 (143.161.64.0/24)." I do not want to change the subnet in either city. Could you please support me in this case? Thank you in advance.
... View more
Labels:
- Labels:
-
Auto VPN
My Top Kudoed Posts
| Subject | Kudos | Views |
|---|---|---|
| 3 | 1022 |
© 2025 Cisco Systems, Inc.
