You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a result, if it is being used in a domain where packet sizes can exceed this value, verification will fail.
Would it make sense to refactor the code, to allow domains to specify the max packet sizes or are there fundamental reasons, as to why the size has to be set to 65535?
The text was updated successfully, but these errors were encountered:
Looking at the verifier code, I don't see anything special about the number 65535 so I think it would be ok to increase it. IPv6 Jumbograms support payloads up to 2^32-1 (not including the headers).
The verifier currently assumes that the max packet size is 65535:
ebpf-verifier/src/crab/ebpf_domain.cpp
Line 26 in 80ada1c
As a result, if it is being used in a domain where packet sizes can exceed this value, verification will fail.
Would it make sense to refactor the code, to allow domains to specify the max packet sizes or are there fundamental reasons, as to why the size has to be set to 65535?
The text was updated successfully, but these errors were encountered: