Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 28 subscribers
  • Views 15157 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

WAN IP Alias

MichelJansen

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.
Parents
  • 0

    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)

Reply
  • 0

    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)

Children
No Data