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

Unable to create firewall with direct memif logic #287

Closed
Mixaster995 opened this issue Jun 28, 2021 · 1 comment · Fixed by #291
Closed

Unable to create firewall with direct memif logic #287

Mixaster995 opened this issue Jun 28, 2021 · 1 comment · Fixed by #291
Assignees
Labels
enhancement New feature or request question Further information is requested

Comments

@Mixaster995
Copy link
Contributor

Mixaster995 commented Jun 28, 2021

Issue

I've been working with NSE composition and found that with direct memif i can't create working firewall app.

Detailed description

firewall-flow

Little squares on the picture are memif interfaces. I removed forwarders from the picture for simplicity(they are present in my local tests).
Passthrough endpoints in my tests looks somewhat similar to forwarders and when there is no direct memif then traffic flows 1 -> 2 -> 3 -> 4 as i understand it. When direct memif logic is present traffic flows 1 -> 4 . So if we place ACL in 2 or 3 it wouldn't affect anything and there would be no traffic filtering.

Possible solution

If i understood problem correctly, then one of possible solutions would be extracting direct memif logic to separate server and using it combined with ordinary memif, when option "with direct memif" is passed.

@Mixaster995 Mixaster995 added enhancement New feature or request question Further information is requested labels Jun 28, 2021
@edwarnicke
Copy link
Member

Ah... OK... I think I see what's going on here.

Direct memif got directly incorporated into the memif chain elements, but directmemif needs to be its own independent chain element that is only used in the forwarder.

This is a good catch and debug on your part... the solution I would recommend would be to look at factoring out the 'direct' part to a separate chain element we only use in the forwarder.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request question Further information is requested
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants