Crumb
c/linux · by Corsair@programming.dev · 153d

NTP Packet blocked... nftables [solved]

Hi,

I want to use openntpd to sync my clock

I'm using

ntpd -ds

I see in my firewall that the dns resolution is working, and I get a server IP from the pool 👍

but anyhow I get

ntp engine ready no reply received in time, skipping initial time setting
no reply from x.x.x.x received in time, next query 300s

Weird my nftable config file should allow it:

# extract
chain OUT {
type filter hook output priority 0; policy drop;
udp dport 123 accept
}

chain IN {
type filter hook input priority 0; policy drop;
ct state established, related accept
}

Any ideas, or which lemmy community to cross-post ?

Thanks.

7 points · 6 comments · view on lemmy.world

6 Comments

Corsair@programming.dev · 1 pts · 152d (1 reply)

Thanks all, I've found the problem it was my ISP router that was blocking it. --> solved.

isVeryLoud@lemmy.ca · 1 pts · 150d

Replace that shit

Corsair@programming.dev · 1 pts · 152d (1 reply)

Thanks @InnerScientist@lemmy.world & @ark3@lemmy.dbzer0.com

Actually I don't think it's the firewall, because all the other programs, protocol are working fine. I've tried with chrony too but I get

No suitable source for synchronisation

May be because the client is a VM ?

InnerScientist@lemmy.world · 1 pts · 152d

because all the other programs, protocol are working fine.

With the shown firewall configuration nothing but NTP should work? You're dropping outgoing packets by default.

ark3@lemmy.dbzer0.com · 1 pts · 152d

I would momentarily drop all rules (if possible) to see if it has to do with firewall at all

InnerScientist@lemmy.world · 1 pts · 152d

Update your nftables rulefile or use nft commands to update your firewall to the following:

# extract
chain OUT {
    type filter hook output priority 0; policy drop;
    udp dport 123 accept

    limit rate 3/second log prefix "Nftables Blocked: OUT: "
}

chain IN {
    type filter hook input priority 0; policy drop;
    ct state established, related accept

    limit rate 3/second log prefix "Nftables Blocked: IN: "
}

Blocked pakets will show up in the kernel log (dmesg/journalcl)

If you want more information on why it is blocked then enable nftrace for those packets

nft add rule inet/ip/ip6 tablename OUT udp dport 123 meta nftrace set 1
nft add rule inet/ip/ip6 tablename IN udp dport 123 meta nftrace set 1
nft monitor trace

Or

nft add rule inet/ip/ip6 tablename OUT meta nftrace set 1

Or maybe even

nft add rule inet/ip/ip6 tablename PREROUTING udp dport 123 meta nftrace set 1

Additionally you can use tcpdump -i to show network packets before they enter the firewall, there you should be able to tell what it's a trying to do.