Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

orphan packets with ownership are not silently dropped #462

Open
jgmbenoit opened this issue Jul 30, 2021 · 1 comment
Open

orphan packets with ownership are not silently dropped #462

jgmbenoit opened this issue Jul 30, 2021 · 1 comment

Comments

@jgmbenoit
Copy link
Contributor

When we fine tune a rule with user , the FIREHOL_DROP_ORPHAN_TCP_ setups have no effect since ownerships are not taking into account. Is there any easy work around ?

@Elkropac
Copy link

Elkropac commented Feb 9, 2022

Hi, can you please provide more info?
I have some firehol rules to allow specific UID go to specific IP and PORT.
It is logged like this:

Feb  9 11:27:28 vps1 kernel: [134646.090060] ACCEPT user output:IN= OUT=eth0 SRC=x.x.x.x DST=y.y.y.y LEN=52 TOS=0x00 PREC=0x00 TTL=64 ID=48694 DF PROTO=TCP SPT=52932 DPT=9543 WINDOW=502 RES=0x00 ACK URGP=0 UID=400013 GID=400013 

Sometimes i see lots of this messages

Feb  9 11:27:28 vps1 kernel: [134646.220985] DROP UNMATCHED OUT-wan:IN= OUT=eth0 SRC=x.x.x.x DST=y.y.y.y LEN=40 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=TCP SPT=52932 DPT=9543 WINDOW=0 RES=0x00 RST URGP=0 

Customer complains, they cannot communicate with their allowed IP/port.

Recently we upgraded to debian 11, so firehol updated from 3.1.6 to 3.1.7 .

But i don't think, this is related. I found this messages in logs before upgrade

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

No branches or pull requests

2 participants