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

https://github.com/opnsense/src/issues/96 #97

Merged
merged 1 commit into from Jan 25, 2021
Merged

https://github.com/opnsense/src/issues/96 #97

merged 1 commit into from Jan 25, 2021

Conversation

muratbalaban43
Copy link

Current implementation for netmap(4) tun(4) support adds a pseudo
ethernet header, src/dst ethernet addresses being all zero'ed.
This seems to cause problems with hashing in the consumer
applications (i.e. Sensei / Suricata ).

Proposed patch fixes this by simply adding a more proper ethernet
pseudo header.

This got tested by us and by a Sensei user who reported this.

Current implementation for netmap(4) tun(4) support adds a pseudo
ethernet header, src/dst ethernet addresses being all zero'ed.
This seems to cause problems with hashing in the consumer
applications (i.e. Sensei / Suricata ).

Proposed patch fixes this by simply adding a more proper ethernet
pseudo header.

This got tested by us and by a Sensei user who reported this.
@muratbalaban43 muratbalaban43 marked this pull request as ready for review January 24, 2021 19:37
@fichtner fichtner linked an issue Jan 25, 2021 that may be closed by this pull request
@fichtner
Copy link
Member

Ranges don't belong to anyone so I guess this is fine. Debating inclusion in 21.1 today (window is still open).

Cheers,
Franco

@fichtner fichtner merged commit bb55290 into opnsense:master Jan 25, 2021
fichtner pushed a commit that referenced this pull request Jan 28, 2021
Current implementation for netmap(4) tun(4) support adds a pseudo
ethernet header, src/dst ethernet addresses being all zero'ed.
This seems to cause problems with hashing in the consumer
applications (i.e. Sensei / Suricata ).

Proposed patch fixes this by simply adding a more proper ethernet
pseudo header.

This got tested by us and by a Sensei user who reported this.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

netmap: tun support has problems with filtering
3 participants