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

All outbound traffic from LAN blocked

Hello,

I'm using Sophos UTM Home Edition v9.3. I've installed this on a PC with two network cards. The WAN interface is connected directly to a fiber modem. The LAN interface is connected to a switch along with my PC etc.

The problem I have is that I cannot reach internet. Both interfaces are up, the WAN-interface has an IP from my ISP. I've created a firewall rule allowing the Local Network to reach Internet on any protocol. See images.

Firewall rule: PS: Even though the image below says WAN I've tried to put in Internet IPv4 & Internet IPv6 but it makes no difference
http://3.ii.gl/B6JlIUe6W.jpg

Interfaces:
http://3.ii.gl/jN8riLN81.jpg

I've not created a DHCP server. The PC I'm testing from has a static IP of 192.168.55.3 and I use either Googles public DNS or OpenDNS. I've set 192.168.55.1 as gateway since that is the LAN-IP of my Sophos.

I did NOT use the wizard. What am I missing here?

This thread was automatically locked due to age.

Parents

0 FrankBarmentlo over 10 years ago

yes, that's the good data..
Question 1: are you using DHCP? the 3th entry is a DHCP-packet being blocked(port 68 to 67)

fwrule=60001 is the "drop/log" default rule in the input chain.
it means that the UTM doesn't know where to send the packets, but as I Can see in your screenshot's, it's already there.
Can you try a fw rule, allowing your internal to any ipv4, in combination with the masq rule you had in place?

the fw-rule in your first post is just allowing internal systems to access your external IP, not the internet or anything else outside your UTM [;)]
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 FrankBarmentlo over 10 years ago

yes, that's the good data..
Question 1: are you using DHCP? the 3th entry is a DHCP-packet being blocked(port 68 to 67)

fwrule=60001 is the "drop/log" default rule in the input chain.
it means that the UTM doesn't know where to send the packets, but as I Can see in your screenshot's, it's already there.
Can you try a fw rule, allowing your internal to any ipv4, in combination with the masq rule you had in place?

the fw-rule in your first post is just allowing internal systems to access your external IP, not the internet or anything else outside your UTM [;)]
Cancel
Vote Up 0 Vote Down

Cancel

Children

0 svendavid over 10 years ago in reply to FrankBarmentlo

yes, that's the good data..
Question 1: are you using DHCP? the 3th entry is a DHCP-packet being blocked(port 68 to 67)

fwrule=60001 is the "drop/log" default rule in the input chain.
it means that the UTM doesn't know where to send the packets, but as I Can see in your screenshot's, it's already there.
Can you try a fw rule, allowing your internal to any ipv4, in combination with the masq rule you had in place?

the fw-rule in your first post is just allowing internal systems to access your external IP, not the internet or anything else outside your UTM [;)]

1. No, I'm not using DHCP on Sophos yet. I've just set my test-PC to use a static IP-address.

TCP/IP properties of test-PC - pointing to 192.168.55.100 which now is the LAN IP of the Sophos:
http://3.ii.gl/Sj4crITQ.jpg

However, my PC is connected to a switch with other devices and they are requesting DHCP. I will set up a DHCP (on Sophos) but first I need to get internet access through the Sophos.

yes, I understood that the FW-rule in my first post was wrong. But I have tried the masquerading rule in combination with allowing my internal to any Internet IPv4 but it doesn't help. I don't understand why it will not work....

Masquerading:
http://3.ii.gl/aEdwhC1Hy.jpg

Firewall rule:
http://3.ii.gl/OGZLsZ-oI.jpg

I can't see the default DROP rule but I believe that's normal.
Cancel
Vote Up 0 Vote Down

Cancel

All outbound traffic from LAN blocked

Submitted a Tech Support Case lately from the Support Portal?