Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 1 reply
  • Subscribers 3 subscribers
  • Views 1753 views
  • Users 0 members are here
Options
Suggested
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

Firewall rule blocking QUIC (port 443) also blocks NTP (port 123)

alan weir

I have a firewall rule to block the QUIC protocol. However when a device on my network attempts to synchronize it's clock using NTP, is is blocked by the firewall rule.

The firewall rule is ANY--->QUIC--->ANY----->Block (rule #6)

When my devices try to synchronize it's clock, is is blocked by the firewall rule which shows the destination port 123, which is obviously not QUIC

What is causing this? I had to create a firewall rule to allow NTP port 123 and place it above the "Block QUIC" rule, but still. Why would this be happening?

2022:10:23-12:55:32 xxxxxxxx ulogd[11415]: id="2001" severity="info" sys="SecureNet" sub="packetfilter" name="Packet dropped" action="drop" fwrule="6" initf="eth1" outitf="eth0" srcmac="d8:5e:d3:86:22:3f" dstmac="68:05:ca:58:20:d0" srcip="192.168.1.30" dstip="40.119.6.228" proto="17" length="76" tos="0x00" prec="0x00" ttl="127" srcport="123" dstport="123"




This thread was automatically locked due to age.
Parents
  • 0

    I found what the problem was. When I created the Service definition for the QUIC protocol ports, I accidently entered the port range of 80:443 instead of creating a group with seperate ports 80 and 443, which ended up blocking NTP on port 123.

Reply
  • 0

    I found what the problem was. When I created the Service definition for the QUIC protocol ports, I accidently entered the port range of 80:443 instead of creating a group with seperate ports 80 and 443, which ended up blocking NTP on port 123.

Children
No Data
Unfiltered HTML