UTM Blocks reply packet

Hi All,

I have a strange behaviour in the UTM packet filter.
We have an incoming connection which we have allowed as usual with this rule.

FW Rule:
Src: 172.24.nnn.nnn/16
DST: 10.0.bbb.bbb/24
TCP: 443

Incoming connections work, but the reply from 10.0.bbb.bbb:443 seems be to a new connection, as without allowing the 10.0.bbb.bbb:443 > 172.nnn.nnn.nnn:50243 the UTM blocks the reply.

08:07:03.081547 IP 172.nnn.nnn.nnn.50243 > 10.0.bbb.bbb.443: Flags [.], ack 28151, win 255, length 0
08:07:03.082191 IP 172.nnn.nnn.nnn.50243 > 10.0.bbb.bbb.443: Flags [P.], seq 61065:61356, ack 28151, win 255, length 291
08:07:03.082239 IP 172.nnn.nnn.nnn.50243 > 10.0.bbb.bbb.5080: Flags [P.], seq 61356:61719, ack 28151, win 255, length 363
08:07:03.082255 IP 10.0.bbb.bbb.5080 > 172.nnn.nnn.nnn.50243: Flags [.], ack 61719, win 1452, length 0
08:07:03.082597 IP 10.0.bbb.bbb.5080 > 172.nnn.nnn.nnn.50243: Flags [P.], seq 28151:28408, ack 61719, win 1452, length 257
08:07:03.082653 IP 10.0.bbb.bbb.5080 > 172.nnn.nnn.nnn.50243: Flags [P.], seq 28408:28415, ack 61719, win 1452, length 7

    Default DROP    TCP         10.0.bbb.bbb    :    443
    →    172.nnn.nnn.nnn    :    50243
         [RST]    len=40    ttl=63    tos=0x00    srcmac=7c:cccccccccc    dstmac=00

    Default DROP    TCP         10.0.bbb.bbb    :    443
    →    172.nnn.nnn.nnn    :    50243
         [RST]    len=40    ttl=63    tos=0x00    srcmac=7c:cccccccc    dstmac=00

Any Hint what’s going on there?


  • Hi  

    Would you please share the screenshot of the DNAT rule? or the Firewall rule you've configured?

  • Do you see any problems with the connection?
    The dropped packet is a "RST" Packet. This means "TCP session reset".
    This packet often  is send some time after session is timed out ...  If server and client don't close the TCP session properly.
    Normally everything works ... with these packets within FW-log.

  • Hi Pummel,

    without a network diagram it's difficult, my guess asymmetric routing between the peers?

  • Hallo Pummel,

    Herzlich willkommen hier in der Community !

    (Sorry, my German-speaking brain isn't creating thoughts at the moment. Sad)

    Alone among the logs, the Firewall Live Log presents abbreviated information in a format easier to read quickly.  Usually, you can't troubleshoot without looking at the corresponding line from the full Firewall log file.  Please post one line corresponding to those above.  If you prefer, obfuscate IPs like 84.XX.YY.121, 10.X.Y.100, 192.168.X.200 and 172.2X.Y.51.  That lets us see immediately which IPs are local and which are identical.

    Unless you experience a true lack of response, you normally can ignore drops of RST packets.

    MfG - Bob (Bitte auf Deutsch weiterhin.)

  • In reply to BAlfson:

    Hi All,

    sorry for the late reply.

    We have reviewed the rule sets again and have not found any issue.

    But we found some older threads where others had the same issues which were related to the connection tracking table.


    Next plan is a announced fail over to the standby node to check if we have the same issues there.


    But here are more details:

    These issues are related to a IPSec IKE v1 Net2Net VPN between two Networks.

    There is no NAT involved, the Tunnel has a "Automatic Packet Filter" set to active.

    Our Side is a UTM the other side is a Cisco.


    Our side where we have these issues >>>>>>>>>>>>>>>>>www>>>>>>>>>>>>>>>>>>>> opposite

    10.0.xxx.nnn/24>>>>Public IP>>>>>>>>>>>WWW>>>>>>>>>>>>>>Public IP>>>>>>>>172.xxx.nnn.nnn/16


    All connections will come from 172.xxx.nnn.nnn hosts and will arrive here in the Network 10.0.xxx.nnn/24.


    Many Greetings





  • In reply to Pummel:

    Hi Ulrich,

    As Josef said, it's normal to see RST packet drops - it's just part of the "chattiness" between TCP configurations programmed by different people.  If you aren't experiencing problems, then you can just ignore those lines in the log.

    Cheers - Bob