Linux

49393 readers

1678 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

Why my nftables do not block DHCP ? (programming.dev)

submitted 2 weeks ago* (last edited 2 weeks ago) by SpongeB0B@programming.dev to c/linux@lemmy.ml

8 comments fedilink hide all child comments

Hi,

On my Debian 12 Bookworm ( raspberry pi )

My nftables do not block DHCP packets ! according to this basic rules

nft -y list rulesset

table ip Tip {

	chain chIN {
		type filter hook input priority 0; policy drop;
		ct state established,related accept
	}
	chain chFW {
		type filter hook forward priority 0; policy drop;
	}
	chain chOUT {
		type filter hook output priority 0; policy drop;
		udp dport 67 drop #DHCP
		udp dport 53 accept
		tcp dport { 80, 443} accept
		ct state established,related accept
	}

}

DHCP should be blocked... but it's not as I get an IP from it..

Any ideas ?

Thanks.

top 8 comments

sorted by: hot top controversial new old

[–] synestine@sh.itjust.works 8 points 2 weeks ago (1 children)

Block port 68 as well as 67. And are you sure the output rule is the best place for that?

[–] SpongeB0B@programming.dev 1 points 2 weeks ago (1 children)

As I want the system to be quite ( not sending data ) I was suspected the output hook to be the one. what are you suggesting ?

[–] synestine@sh.itjust.works 2 points 1 week ago

Ah. It just didn't compute for me. I'd think stopping the DHCP server or making it not listen on that interface would be easier than trying to firewall it off.

Yeah, blocking thise inbound and outbound will quiet that service.

[–] lazynooblet@lazysoci.al 6 points 2 weeks ago (1 children)

Why block from the firewall. Normally you would set a static ip to not use dhcp. You could also uninstall or disable the dhcp client service.

[–] SpongeB0B@programming.dev 1 points 2 weeks ago

Obviously, but I'm anyway wondering why it doesn't blocking like it should
I hope nftables do not let other pass like this...

[–] Morphit@lemmy.wtf 4 points 2 weeks ago

DHCP uses raw sockets so it gets to skip the normal networking stack. See here for the same question on Reddit: https://www.reddit.com/r/linuxadmin/comments/flcsc8/nftables_not_blocking_incoming_dhcp_traffic/

[–] AnnaFrankfurter@lemmy.ml 1 points 1 week ago (1 children)

I know nftable is more secure and robust but sometimes I feel like iptables is the way.

[–] Auli@lemmy.ca 3 points 1 week ago* (last edited 1 week ago)

They are literally the same now. Use IPtables it's getting converted to nftables now. Just a different interface.