I have added an IP alias on the WAN.
I have created an non http rule.
- Alias IP not working
- 'Main' IP on WAN works OK.
What can this be?
Thanks in advance.
Regards,
Michel
This thread was automatically locked due to age.
Important note about SSL VPN compatibility for 20.0 MR1 with EoL SFOS versions and UTM9 OS. Learn more in the release notes.
I have added an IP alias on the WAN.
I have created an non http rule.
- Alias IP not working
- 'Main' IP on WAN works OK.
What can this be?
Thanks in advance.
Regards,
Michel
__
Analyst at Tecnomega
Cyberoam Certified Network & Security Expert (CCNSE)
I have the same problem here.
A 'DNAT' rule using the primary WAN IP correctly sends traffic to the protected internal server, while a using a WAN Alias IP won't.
Someone in the forum suggested this is a problem with http based policy, but it seems to me it's a general problem.
see: community.sophos.com/.../10931
Hope I'm wrong.
--Antonio
Edit (23 Jan 2016):
The support found that the firewall arp table didn't include data about alias IPs.
from the console they issued the command:
> arping -s IP_ALIAS -c 5 -I PortE1 IP_GATEWAY
and it started to work (unti next reboot, they are investigating)