Proxy Server

[navysubvet]

My client has a proxy redirect url to port 8080? How do I build that in Meraki?

[alemabrahao]

MX is not a proxy, but if you want to filter however you can use content filtering.

https://documentation.meraki.com/MX/Content_Filtering_and_Threat_Protection/Content_Filtering

If this is not what you want, please provide us with more details.

[navysubvet]

Client currently redirects users through a proxy appliance URL https://xxx.xxx.com:8080, when they log in via Active Directory. Some users are in a group that's allowed to bypass. How/where do I configure this? Hope this makes sense

[alemabrahao]

As explained MX doesn't work like a proxy, but you can use Access control configuration.

https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Splash_Page#MX_Splash...

[almightythor]

are they wired or wireless clients? what traffic are you redirecting? Is it LDAP or Web traffic? First identify the traffic, source, and destination. then you can easily redirect using port forwarding. If this is for web traffic you might also tag an AD group or some other traffic to assign dhcp and vlan and use a policy to route that traffic to the proxy as the gateway for that vlan. Can you give us more details on the topology and interesting traffic?

[navysubvet]

Strictly user internet access. Employees that log in, authenticate via  AD, are directed to a Proxy (https://blahblah:8080), that allows certain internet access, based on their AD group. There's a specific group that bypasses the Proxy altogether. It's straightforward with other firewalls, but, I'm trying to define this in configuring the MX

[alemabrahao]

As explained MX doesn't work like a proxy, but you can use Access control configuration.

https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Splash_Page#MX_Splash...

[almightythor]

yes I agree it's easier with the MR than the MX because you can route to a landing page. Since the authentication happens first, you can assign the group to get a specific dhcp scope, provided you have windows server providing dhcp option 252. Then you can assign that subnet to a vlan in the MX. That is the long way but it is possible to use the MX and use the proxy, but not use the MX TO route to proxy if that makes sense.

Have you tried connecting to the setup.meraki.com or wired.meraki.com local config page? There is an option in many MX I have seen from MX64 and up for a proxy on this page.  The install guide says this:

Web proxy settings
These settings take effect if the MX device has to fall back to using HTTP to contact the Cloud Controller. By default, web proxy is disabled. To enable web proxy, do the following:

When the WAN connection is fully enabled, Internet LED 1 will turn green.
Please note that all these settings below are accessible only via the local management console.
• Choose Web proxy > Yes.
• Enter values as appropriate for Hostname or IP and Port.
• If you require authentication, choose Authentication > Use authentication, and enter appropriate values for Username and Password

I also recommend you call Meraki support desk and if they don't have what you need then please submit a feature request as those are looked into.

Here is a guide to force proxy for MR wireless clients.

https://documentation.meraki.com/MR/Firewall_and_Traffic_Shaping/HTTP_Force_Proxy_on_MR_Access_Point...

You can also try a free proxy like squid which is much easier.

[alemabrahao]

You can use the Access control configuration on the MX.

https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Splash_Page#MX_Splash...