Skip to content

net: NET_CONN_CACHE relevant #4042

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

Closed
zephyrbot opened this issue Sep 14, 2017 · 5 comments
Closed

net: NET_CONN_CACHE relevant #4042

zephyrbot opened this issue Sep 14, 2017 · 5 comments
Assignees
Labels
area: Networking bug The issue is a bug, or the PR is fixing a bug priority: low Low impact/importance bug

Comments

@zephyrbot
Copy link
Collaborator

zephyrbot commented Sep 14, 2017

Reported by Likai Liu:

Find in v1.8.0, not sure it exists in new version .
Set NET_CONN_CACHE y
When we do not have a connection to a host , we can only set the hash value to negative_cache when conn_cache has no free position.
Why not set it to negative_cache when the first time we find no match connection ? Then drop the later packets in negative_cache.

(Imported from Jira ZEP-2616)

@zephyrbot
Copy link
Collaborator Author

by Jukka Rissanen:

The connection cache is not enabled by default so it is not extensively tested thus there might be issues in it.
Anyway, from the bug description it is not clear what is the issue. Could you describe what kind of issue you are seeing, and what is the expected outcome?

@zephyrbot
Copy link
Collaborator Author

by Likai Liu:

Jukka Rissanen On memory and cpu constrained devices ,when we do not have a connection to a host ,I want to drop the received packets immediately, and skip the ICMP destination unreachable which affecting the efficiency.

I want to use negative_cache to drop the received packets . But it seems that it does not work.

@zephyrbot zephyrbot added priority: low Low impact/importance bug area: Networking bug The issue is a bug, or the PR is fixing a bug labels Sep 23, 2017
@zephyrbot zephyrbot added this to the v1.9.0 milestone Sep 23, 2017
@nashif nashif removed this from the v1.9.0 milestone Dec 8, 2017
@nashif
Copy link
Member

nashif commented Nov 5, 2018

@jukkar is this still an issue? Can you please take a look or close if not relevant anymore.

@jukkar
Copy link
Member

jukkar commented Nov 5, 2018

Sure, I will do some more testing for this later this week.

@jukkar
Copy link
Member

jukkar commented Nov 6, 2018

This works now as expected, if the connection entry is in negative cache, it is dropped immediately.

@jukkar jukkar closed this as completed Nov 6, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: Networking bug The issue is a bug, or the PR is fixing a bug priority: low Low impact/importance bug
Projects
None yet
Development

No branches or pull requests

3 participants