The Meraki Community
Register or Sign in
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
  • About h_p
h_p

h_p

Conversationalist

Member since Sep 7, 2022

‎09-22-2022
Kudos given to
User Count
MyHomeNWLab
MyHomeNWLab
1
View All

Community Record

4
Posts
0
Kudos
0
Solutions

Badges

Lift-Off View All
Latest Contributions by h_p
  • Topics h_p has Participated In
  • Latest Contributions by h_p

Re: Static Route on MX can route IPs on same VLAN but not for a different V...

by h_p in Security / SD-WAN
‎09-08-2022 09:24 AM
‎09-08-2022 09:24 AM
I have the 10.16.2.225 as a gateway for the static route, it's my next hop IP, that's why I'm using that instead of 10.16.2.226. The static route is working, but only for IPs on VLAN 10: 10.16.2.224/28.   ... View more

Re: Static Route on MX can route IPs on same VLAN but not for a different V...

by h_p in Security / SD-WAN
‎09-08-2022 08:58 AM
‎09-08-2022 08:58 AM
I'm not sure, but I'll look into it.   If this were to be the case, how would I go around it? Can I configure something similar on Meraki? ... View more

Re: Static Route on MX can route IPs on same VLAN but not for a different V...

by h_p in Security / SD-WAN
‎09-07-2022 07:08 PM
‎09-07-2022 07:08 PM
I'm assuming it is, considering the Fortigate which was previously connected to the Mikrotik was able to reach the 10.16.0.26 with any of the 192.168.1.0/24 IPs.     ... View more

Static Route on MX can route IPs on same VLAN but not for a different VLAN

by h_p in Security / SD-WAN
‎09-07-2022 03:38 PM
‎09-07-2022 03:38 PM
So I'm fairly new to Meraki, mostly I've been handling the MR line of devices and just recently started a deployment for an MX 250. I've successfully created the addressing and VLANs and all of that is working just fine. The issue is when I'm trying to reach the routes that the MX is knowing through a static route through one of the interfaces, this interface (not a WAN interface) is plugged in to a Mikrotik Router and the Mikrotik has a LAN segment 10.16.2.224/28 with the GW being 10.16.2.225 all of that is configured on the interface that goes directly to one of my MX interfaces.   On the other hand, the MX has the following configuration: VLAN 10 - 10.16.2.224/28 | MX IP: 10.16.2.226 VLAN 40 - 192.168.1.0/24 | MX IP: 192.168.1.1 Static Route for a Subnet: 10.16.0.0/24 with Gateway IP: 10.16.2.225 (Mikrotik's interface IP)   The 10.16.0.0/24 subnet is because it reaches a Virtual PBX through the 10.16.0.26. I can successfully reach the 10.16.0.26 when trying to ping with a VLAN 10 source, but when I try to use VLAN 40 as a source I'm unable to reach those routes. We need the phones that will be registering to the PBX to have an IP from the 192.168.1.x subnet. The PBX has the 192.168.1.0/24 subnet allowed, and the PBX provider has turned off all firewall settings so we could do some testing but still no luck.   Worth mentioning that the customer was previously using a Fortigate device and they had this configuration and it was working just fine for them.   I'll appreciate any input from the community.   Thanks.   ... View more
Labels:
  • Labels:
  • Other
Kudos given to
User Count
MyHomeNWLab
MyHomeNWLab
1
View All
Powered by Khoros
custom.footer.
  • Community Guidelines
  • Cisco Privacy
  • Khoros Privacy
  • Privacy Settings
  • Terms of Use
© 2023 Meraki