Skip to content

https-dns-proxy: correct duplicate nft rules and error tracking#8

Draft
egc112 wants to merge 2 commits intomossdef-org:mainfrom
egc112:main
Draft

https-dns-proxy: correct duplicate nft rules and error tracking#8
egc112 wants to merge 2 commits intomossdef-org:mainfrom
egc112:main

Conversation

@egc112
Copy link
Copy Markdown

@egc112 egc112 commented Apr 30, 2026

Refactor https-dns-proxy init script for nftables
The problem from issue #7 is solved 👍

Some small remaining things:
Every time the firewall restarts there are duplicate nft rules.

A better approach might be to add the table and then flush it.

Furthermore seeing line

[ ! -s "$NOTRACK_NFT_FILE" ]
makes me think you have added it for error tracking?

In that case you might need to add code when that is called see my last proposed change

Signed-off-by: Erik Conijn egc112@msn.com

egc112 added 2 commits April 30, 2026 11:37
The problem from issue mossdef-org#7 is solved 👍 

Some small remaining things:
Every time the firewall restarts there are duplicate nft rules.

A better approach might be to add the table and then flush it.

Furthermore seeing line https://github.com/mossdef-org/https-dns-proxy/blob/64d18e172fbbe79ee1695bcf32e62658f700c7c1/files/etc/init.d/https-dns-proxy#L166 makes me think you have added it for error tracking?

In that case you might need to add code when that is called see my last proposed change

Signed-off-by: Erik Conijn <egc112@msn.com>
Refactor https-dns-proxy init script for nftables
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant