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

Large network traffic detected on HOPOPT/0 to port 0 #56

Open
ddddavid-he opened this issue Feb 26, 2023 · 5 comments
Open

Large network traffic detected on HOPOPT/0 to port 0 #56

ddddavid-he opened this issue Feb 26, 2023 · 5 comments

Comments

@ddddavid-he
Copy link

When grouped the data by protocols, I found the following traffic ranged at the top

PROTO PORT CONNS RX_BYTES ... LAYER7
IP 0 1607268 29298871423 ...  
TCP 443 1770273 9361172256 ... HTTPS
TCP 80 3242169 4158756881 ... HTTP

According to /etc/protocols the No.1 traffic is protocol IP or HOPOPT.
I wonder what kind of traffic it exactly is and what it should be classified in layer7 column?

@jow-
Copy link
Owner

jow- commented Feb 26, 2023

Looks like IP-in-IP tunnel traffic?

@ddddavid-he
Copy link
Author

@jow- Thanks for replying

So it is another kind of IP-in-IP traffic? There's an item in protocol mapping writes 4 0 IP-in-IP which is different from HOPOPT/0 0

@jow-
Copy link
Owner

jow- commented Feb 26, 2023

Not sure, could also mean "no layer 4 protocol information available". You didn't provide any details about the setup you run the service on, but maybe your firewall setup is unusual. Compare with /proc/net/nf_conntrack to figure out which entries are reported without layer 4 protocol info (the 3rd and 4th columns in the proc file)

@ddddavid-he
Copy link
Author

Okay, I'll do some further examination on that file later since I haven't found anything missing layer 4 protocol yet.

@ddddavid-he
Copy link
Author

ddddavid-he commented Feb 28, 2023

After some experiments, I notice that the HOPOPT traffic is mainly caused by torrent downloading. And the connection information looks like

ipv4     2 tcp      6 117 TIME_WAIT src=10.0.1.1 dst=46.232.211.220 sport=59657 dport=64095      packets=6 bytes=388 src=46.232.211.220 dst=125.94.202.131 sport=64095 dport=59657 packets=     4 bytes=184 [ASSURED] mark=0 zone=0 use=2

in nf_conntrack

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