Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 11 replies
  • Answers 1 answer
  • Subscribers 2 subscribers
  • Views 4860 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

Unable to define the outgoing interface for Web Filtering

RomanoBanchieri

Hi,

For the first time, I've tried to activate the optional outgoing interface with the command "cc set http enable_out_interface 1", like described in https://community.sophos.com/kb/en-us/126892.

The new field appears in the WebAdmin Web filtering, have tried to put some of my secondaries WAN IP addresses, but without success, the source IP address for Web traffic is always my default WAN address.

Please, can someone confirm that this feature works, and with version 9.605?

Thank you,

Romano



This thread was automatically locked due to age.
Parents Reply Children
  • 0 in reply to Jaydeep

    hi Jaydepp,

    I'm sure that my traffic go through, not only because I've checked the log, but because too my masquerading rule who set another ip address.

    If it's working for you (version 9.605 for sure?), it's like something is wrong in my side. but I've tried on another appliance completely different located to another customer, with other settings, and it's the same.

    My WAN IP addressing, in the same subnet, is like:
    - WAN : default interface addr
    - WAN+1 : used for masquerading all my LAN subnet
    - WAN+2 : used for outgoing interface for Web Filtering

    With transparent or standard proxy, my source network traffic to Internet is WAN.
    If I disable my proxy, my source network traffic to Internet is WAN+1.
    if I set the outgoing interface for Web Filtering to WAN+2 on all profiles, my source network traffic to Internet is WAN.

    If someone can have an idea to help me, I will appreciate.

    Regards,

    Romano

Unfiltered HTML