About svennerski

svennerski

This is specifically a member of staff using their Linux workstation to send a magic packet to another host within our network whilst connected via the client VPN. They do not have access to the Meraki dashboard unfortunately.

svennerski

We recently moved over from a Cisco ASA appliance to an MX450 with all the firewalls replicated (where applicable). We have a member of staff who used to use WOL when he was connected to the client VPN in order to wake up a system that sits inside our network. Since moving to the MX450, WOL no longer works and he is unable to wake up the same system he has in the past. The only other thing that's changed is the subnet used by the VPN clients. Old VPN client range: 192.168.105.5/29 New VPN client range: 10.150.0.0/24 Can anyone shed any light on what I would need to get to get this working, or if indeed it's even possible on an MX appliance?

svennerski

Thanks for the great explanation and the link to the further reading. Very helpful!

svennerski

Interesting. I'd really like to see this feature.

svennerski

I was wondering if anyone would be able to explain exactly what setting to "Use VPN" option does against each of the subnets I have available within our MX appliance: When I select "Yes" under the "Use VPN" field, the subnet then appears under the VPN Status page under "Exported subnets": What does exporting these subnets actually do? Does it just present that subnet to all defined VPNs so traffic is routable between the subnet and remote networks at the end of the VPN? I can't seem find a proper explanation for what it actually does.

svennerski

Community Record

Badges

Re: WOL no longer working after move to MX450

WOL no longer working after move to MX450

Re: Exported subnets - VPN

Re: AnyConnect VPN - Migration from ASA to Meraki MX84

Exported subnets - VPN