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

Create a tutorials exercise demonstrating using idle timeout feature, plus controller that deletes timed out table entries #656

Open
jafingerhut opened this issue Dec 11, 2024 · 0 comments

Comments

@jafingerhut
Copy link
Collaborator

For example, having a table that matches on TCP/UDP packet 5-tuple of (IPv4 source address, IPv4 destination address, IPv4 protocol, TCP source port, TCP dest port), sending PacketIn message from switch to controller on a miss, and the controller responds to those messages by adding a new entry in the table that matches future packets.

The table uses the idle_timeout feature, and so notifications of entries that have not been matched for too long cause IdleTimeout notification messages to be sent to the controller, which responds to those by deleting the idle entry from the table.

See here for some more details and discussion:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant