Q: Can I use a secondary IP range in the Connection Profiles?
I have successfully used a primary IP range (ex 22.214.171.124/24) in my connection profiles. I would like to use a valid secondary IP range (ex 126.96.36.199/24) in my connection profile. NOTE: this range is a valid public address range on my network.
My client system (Windows 7) is able to successfully obtain an address in the specified secondary IP range. However, I'm not able to access any devices. when I bypass the MAG4610 VPN appliance, and statically configure a test laptop with an ip in the secondary range, all is fine.
I supect an issue with the MAG4610 providing the proper gateway/netmask to the VPN client.
Spinning my wheels quite a bit her. So, any help would be *GREATLY* appreciated.
Are the routes in place to send the traffic for the secondary range to the internal port of the MAG? I am guessing it is not as the same IP works outside the appliance. If the range is not on the same subnet as the internal port, routes need to be defined on the network to send traffic to the MAG internal port