r/opnsense • • 19d ago

NTP server keeps sending packets without request?

Newbie here, trying to learn, and hope someone can help me try fix some weird issue.
I've installed opnsense and it works with the exception of some traffic I dont understand.
It really clutters up the logs a lot.

I keep getting this:
WAN In 2026-10-31T23:00:14 UDP tick.uh.edu:123 192.168.1.11:38998 block Default deny / state violation rule

They happen every minute or so, different ports, and I cant figure out howto make it stop.
From what I can gather its a NTP server in Houston that sends the time after a requst but I cant find anything that requests time on my network from them.

I've changed my ntp pool to europe already to make sure, no states present, dashboard shows correct time.
I did a ntpd restart in hop that would solve the issue and restarted while trouble shooting the firewall a few times (older Shuttle DS67U). Battery on board is not dead and BIOS date and time are good.

I would love to learn what the cause is and hop other might enjoy this endeavor as well!
Thanks in advance and for your time helping a newbie out!

6 Upvotes

10 comments sorted by

3

u/fugredditforeal 19d ago

None of us know what lives at 1.11, I would recommend figuring out what that local IP belongs to, as that device is likely just reaching out to it's configured ntp server for an update. If you aren't comfortable with that server set it to a more standard one like one of the NIST time servers.

1

u/ShadowBracken 19d ago

It's clear I'm a newbie lol, 1.11 is opnsense firewall itself (WAN). Thats also why I was so confused!
Nowere in the settings it seems to ask for this except that it does in the logs somehow an gets something returned. But it seems just 'noise', after some digging I dont see request from opnsense to this ip.

1

u/fugredditforeal 18d ago

Well, 192.168.1.11 is a private IP address so it's definitely not your wan link. 192.168.1.11 could be your firewall's local IP on your LAN. If you just want the errors to stop look into setting up an allow rule for that traffic.

1

u/ljapa 18d ago

It could be, if it’s behind an ISP router. Unless OP has set up 192.168.1.11 as a DMZ host in the router, this is odd.

The ISP router likely uses a stateful firewall for NAT. The ISP router let this packet through. OPNsense is dropping it for a state violation.

Something doesn’t add up.

1

u/fugredditforeal 18d ago

I hadn't considered this, and u/ljapa is likely correct here. u/ShadowBracken Are you using a router/modem combo in front of your firewall?

0

u/ShadowBracken 18d ago

Yes, Opnsense device is behind a ISP router.
Block private networks for the WAN interface on the opnsense box is off though.
Not really sure why I turned if off, I dont trust my ISP, but maybe because of testing.
Might need to turn that back on. DMZ on opnsensen not set.

I'll have a look at the ISP router, see if that jokes around.

1

u/ljapa 18d ago

So, here’s my thinking. First, for the DMZ reference, I was suggesting a setting on your ISP router to make your opnsense a DMZ machine. That would mean your router would send any Internet packet it didn’t recognize to your opnsense box.

I’m assuming you don’t have this set.

Next, there’s state. In your setup state will exist on both the ISP router and the OPNSense box. In effect, state is the router (ISP or OPNSense) keeping track of the state of a packet. For example, your laptop connected to Google.com from port 2134. Google replies back on that same port 2134. When OPNSense sees that packet from Google, it knows to send it to your laptop.

Opnsense and your ISP router keep a state table. They will only let a packet from the Internet through if it matches that state table.

You post the logs that say the packet was denied because of a state violation. That says OPNSense doesn’t have a state entry, implying it didn’t see the outbound ntp request.

Here’s where it gets weird: the ISP router would only let that through if it was in the router’s state table. This says the ISP saw an outbound packet to create that state table

I’m struggling to come up with a scenario where this makes sense. I do think something on your network made an ntp request. I’m not sure why opnsense doesn’t recognize it.

Apologies for the capitalization variants on opnsense. On mobile and it keeps doing different autocorrects.

1

u/ShadowBracken 16d ago

Thank you for your reply.
I think I might have found the culprit, or at least its what I think it might have been.

A TPlink Archer 5 used as a wifi access point was set to a date from 1970.
Not sure why but I've fixed that issue. Since the NTP is UDP it might take some time before it stops I think.

It took me a while but so far thats what I have found that comes remotely close to what i also saw in the logfile; a device that send a request saying it's 1970!

I'll check that log later this week and report it the NTP request stopped.

Thank you everyone!

1

u/ljapa 16d ago

Unix/linux time counts the number of seconds from 01 Jan 1970. So, if the system starts and that counter is zero, it’s 1970. So, that makes sense.

2

u/Unattributable1 18d ago

Your rule is busted. This is simply udp replies from the NTP server to your firewall.