Not Able to ping Internet from Sophos XG 115w

Hi,

please check the dns settings of the XG.

ian

Hi,

DNS Settings are OK, clients are accessing internet

the issue is that  the sophos  device cannot access Internet from the Administration Portal

Karim,

Hi,

which version do you use currently?
Which output do you get from
- diagnostics / Tools / Ping -- 8.8.8.8
- diagnostics / Tools / Traceroute -- 8.8.8.8
- diagnostics / Tools / Name lookup -- 8.8.8.8

Hi,

which version do you use currently?
Which output do you get from
- diagnostics / Tools / Ping -- 8.8.8.8
- diagnostics / Tools / Traceroute -- 8.8.8.8
- diagnostics / Tools / Name lookup -- 8.8.8.8

Hi,

version is XG115w (SFOS 18.5.1 MR-1-Build326)  

Hi Karim GUIDOUM : What is the observation in TPCDUMP and Drop packet on XG CLI when you generate PING or any traffic from XG CLI itself? Is it getting dropped or getting forwarded out to the correct WAN Interface? 

please tell us more about IP 192.168.123.81 and 192.168.161.85
what are these devices? Where are they located?
If you don't mask your internal traffic at the WAN interface, possible your LAN-segments are routable and the transfer-subnet not..
Are there other Ways out of your LAN (2nd  ISP, other routers, ...)?

Try the ping & traceroute 8.8.8.8 tests  again and select the internal interface as source.

Hi,

192.168.123.81 is my default GW for the sophos, wich is ISP router, 

192.168.161.85 is located on the ISP network,

i'm using NAT with a public IP provided by the ISP, the public IP is configured as an alias on the WAN interface of Sophos firewall

ping and traceroute to 8.8.8.8.8 using the internal interface as source is also failing,

i have only one Internet connection

here is the traceroute screenshot from LAN IP of sohops 

Hi,

using the public which is assigned to the external interface of your isp router will not work. You need to put the isp router into bridge mode to be able to use the public IP address.

ian

Hi,

i'm using another public IP (41.111.198.5) as Alias on the external interface (wich has the  primary IP 192.168.123.82 )

thanks

Sorry, this is not making sense, please provide a network drawing to clarify the connections.

ian

here is the network diagram

Seems as your NAT/Masquerading rule don't capture the system-generated traffic ...
Can you show us a screenshot?

@rfcat_vk: if there is a really big bug ... internal users should not be able to work either

Hi dirkokotte,

I am nor sure what you are driving at?

ian