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

Sophos UTM9 Driving me crazy!

Hi all, any responses would be greatly appreciated......

We are currently setting up a Hyper-V guest as an MSP but are having trouble routing packets inbound to our DMZ's message relay (MR) on our Software based Sophos UTM9.

We have created a Network Definition within the UTM pointing to our MR (NOT tied to an interface), we have created Service Definitions for the port forwarding, we have created our DNAT rules for the Services (Traffic Selector - Any to Service to External WAN to Destination MR) and we have created our Firewall rules to allow free flowing traffic for the Services.

However, we are not able to Telnet from an external location into the MR through the UTM. We have checked the logs on the UTM and see no record of any packets over the Service ports we have defined yet we do see rejected packets from other external sources, none of which relate to any of our activity.

We have a Draytek Router on the WAN side of the UTM and we have DMZ'd the LAN port on the Draytek which connects the two and are forcing traffic from our designated public IP for this service through this LAN port to the UTM.

I am tearing my hair out over attempting to resolve this issue and I now have very little left, I may have to resort to a wig and pluck at that instead.

Any help would be greatly appreciated. Thanks in advance.

This thread was automatically locked due to age.

Parents

0 jeff.welling over 12 years ago

Thanks for providing this additional info!

Just as a heads up, you might want to verify that the program you're using has a specific source port, most applications choose the source port at random and the destination port is the one that's specific, but this isn't saying you're configuration is incorrect just to watch out for those. Even if this was the cause of the problem, you would see it dropped in the firewall log and this would be a case of "why is my firewall rule not matching" so this is not the problem here.

The problem at hand seems to be that the UTM never receives the packets since they aren't showing up in the firewall logs. Check tcpdump on the WAN interface, filtering for the source IP address that you're connecting from. With tcpdump running, try and connect, if you see the packets arriving then the UTM is infested with demons. If you don't see packets arriving, the demons are upstream, perhaps in the modem.

*shakes first*, bloody demons. [:)]
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 jeff.welling over 12 years ago

Thanks for providing this additional info!

Just as a heads up, you might want to verify that the program you're using has a specific source port, most applications choose the source port at random and the destination port is the one that's specific, but this isn't saying you're configuration is incorrect just to watch out for those. Even if this was the cause of the problem, you would see it dropped in the firewall log and this would be a case of "why is my firewall rule not matching" so this is not the problem here.

The problem at hand seems to be that the UTM never receives the packets since they aren't showing up in the firewall logs. Check tcpdump on the WAN interface, filtering for the source IP address that you're connecting from. With tcpdump running, try and connect, if you see the packets arriving then the UTM is infested with demons. If you don't see packets arriving, the demons are upstream, perhaps in the modem.

*shakes first*, bloody demons. [:)]
Cancel
Vote Up 0 Vote Down

Cancel

Children

No Data