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

Sophps XG making sure traffic only goes through Sophos

Am I missing something here ?

I've installed Debian 3cx and Gateway is Sophos XG (static ip and gateway set on network)... however even without Sophos running i can still get normal access to 3CX just fine, which proves despite setting static IP and G/W to Sophos, they are ignored..

Now i'm wanting to troubleshoot with Sophos to see if and what traffic is going though..

For eg... i can login to 3CX management and access page just fine with or without Sophos running.

Under normal circumstances, for instance, you can't log on to a windows domain user if server is not running... Yet i can access 3CX just fine without gateway being up..

Why? Would i just traceroute under SOphos to 3CX to 'see' ? whats going on?

The only 'indication' was at first run when i added URL's exceptions to sophos to allow PBX config...... From that point on, i 'just assumed' Sophos needed to be up.

This thread was automatically locked due to age.

Parents

0 rfcat_vk over 3 years ago

So, basically you are saying the 3cx is not connected to the XG internal network?

ian

corrected typing mistake.

XG115W - v19.5.1 mr-1 - Home

If a post solves your question please use the 'Verify Answer' button.
Cancel
Vote Up 0 Vote Down

Cancel
0 NA NA3 over 3 years ago in reply to rfcat_vk

yes..
Cancel
Vote Up 0 Vote Down

Cancel
0 rfcat_vk over 3 years ago in reply to NA NA3

So, if it is not connected to the XG, how do you intend to make the traffic flow through the XG?

Ian

XG115W - v19.5.1 mr-1 - Home

If a post solves your question please use the 'Verify Answer' button.
Cancel
Vote Up 0 Vote Down

Cancel
0 NA NA3 over 3 years ago in reply to rfcat_vk

Good question, but the idea 3CX PBX didn't start until i added exceptions to sophos, to me suggested it WAS going through Sophos XG (at least to this point)...

After that Now, it doesn't seem so.
Cancel
Vote Up 0 Vote Down

Cancel
0 NA NA3 over 3 years ago in reply to NA NA3

Silly me..

I did a traceroute at linux command line (3CX), and 1st hop was pointing through Sophos IP on network.. and i should have also realized WAN port on router/ISP is pointing to WAN port of Sophos. not server, which is why running 3CX firwall tests all passed.

However when traceroute from Sophos back to 3CX via diagnostics page, it times out.. Why would that be? ICMP not enabled or something..???

I can ping server from Sophos and it gets reply's ok just cannot traceroute IN. Could it be somehow blocked on 3CX ?
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 NA NA3 over 3 years ago in reply to NA NA3

Silly me..

I did a traceroute at linux command line (3CX), and 1st hop was pointing through Sophos IP on network.. and i should have also realized WAN port on router/ISP is pointing to WAN port of Sophos. not server, which is why running 3CX firwall tests all passed.

However when traceroute from Sophos back to 3CX via diagnostics page, it times out.. Why would that be? ICMP not enabled or something..???

I can ping server from Sophos and it gets reply's ok just cannot traceroute IN. Could it be somehow blocked on 3CX ?
Cancel
Vote Up 0 Vote Down

Cancel

Children

No Data

Sophps XG making sure traffic only goes through Sophos

Submitted a Tech Support Case lately from the Support Portal?