Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
About Norman3
Norman3
Conversationalist
Member since Jan 20, 2023
Jan 24 2023
Community Record
6
Posts
0
Kudos
0
Solutions
Badges
Jan 23 2023
11:25 AM
nope. Just the IP field
... View more
Jan 23 2023
11:12 AM
I configure it as a url, it just tells me it needs to be an IP address.
... View more
Jan 23 2023
8:01 AM
Thank You for your help, I found the settings in the article but I am confused by one thing, When I'm doing the Local breakout rule, it asks for a CIDR/Hostname, but it won't accept a hostname. I have to use an IP address. For the issue I'm currently trying to solve, this should be okay, but I'd like to use an actual hostname rather than CIDR entry. Am I missing something?
... View more
Jan 20 2023
11:11 AM
Meraki Teleworker -- S2S VPN --> Meraki MX250(x2 one in Denver and one in Chicago) --> Directly connected to Denver/Chicago Routers --> Routed to Corp Network or Our Internet connection Currently we have 2 base templates, One uses the Chicago connection as primary and Denver as backup while the other is Reversed. In both cases the MX250 is connected directly to our router in each location and traffic is routed accordingly. In every case though all traffic, including internet traffic is routed through the S2S connection with the MX250.
... View more
Jan 20 2023
11:07 AM
The site is published to the Internet. The caveat to that is we route all of our Meraki users' internet traffic through the Meraki VPN through our network and out our company internet pipe. What I'm looking to do is create a rule to offload traffic to certain sites out the User's local internet pipe while keeping the rest of the internet traffic going through the regular route through our network.
... View more
Jan 20 2023
10:46 AM
Good Day, I hope I can find some help with a routing issue. First I'll layout the scenario: We are a primarily Cisco WLC shop but we also use Meraki MX64 and Z3 teleworker gateways for most of our remote users. With that in mind, we normally route all traffic through the Meraki including Internet traffic. This is for a variety of reasons that include Security logging, as well as some of the sites we connect to require us to be added to whitelists in order to connect. That being said, there are several sites that run super slow for our Meraki users when they are international. One of those sites (lets call it https://company.thissite.com) can be reached publicly through the internet and does not require the traffic to come from our networks. Unfortunately the site is hosted in AWS which sees the traffic coming from our Denver location, and routes into the AWS network from there. Users in the UK that connect to this site regularly have complained about how slow it is. When I do my investigations, it shows the traffic is basically crossing the Atlantic twice (there and back) to get to the site and process data inputs. When I tested on a user's personal PC connected to their home network the site is super responsive and functions perfectly with very little delay. Doing the same investigations, I find the traffic going out of the user's local internet connects into the AWS cloud from a regionally local point rather than traversing the world and exiting our network in the states before hitting the AWS network. Now with that in mind what I would like to figure out a way to configure a template like this: Rather than offloading all internet traffic out the user's local internet, I'd like to create a template that will have all the traffic going through our network as it currently is, but create a rule that allows certain Addresses (preferably by name rather than IP) to be routed out the user's local internet. Ideally this would be a rule for a group, so that as we go along and find other sites with performance issue we can just add them to that group rather than having to add a new rule every time. Is this possible in the Meraki configurations? Please understand, I am new to Meraki and still learning the ins and outs of everything.
... View more
© 2024 Cisco Systems, Inc.
