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

Detect packets exceeding MTU #4

Open
msune opened this issue Sep 27, 2024 · 0 comments
Open

Detect packets exceeding MTU #4

msune opened this issue Sep 27, 2024 · 0 comments
Labels
bpf docker Docker container feature

Comments

@msune
Copy link
Member

msune commented Sep 27, 2024

Detecting MTU misconfigurations and raise alarms would be a big plus.

Some early thoughts:

  • When sfunnel is attached in INGRESS, there is no way to know the egress interface at that point in time.
  • Likewise, route MTU checking happens after sfunnel has been executed when attached on INGRESS and before sfunnel is executed when attached on EGRESS. There is literally no way to know that.
  • Sidenote: If IPv4 DF=1 is set, Interface counters dropped and/or tx_dropped should increase

What might be more realistic is to define an env variable $DETECT_MAX_MTU=value, and that sfunnel can emit bpf_printk() warnings,with a clear pattern, when funneling exceeds $DETECT_MAX_MTU.

@msune msune added feature docker Docker container bpf labels Sep 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bpf docker Docker container feature
Projects
None yet
Development

No branches or pull requests

1 participant