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.

Sign up for GitHub

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

Jump to bottom

Do not assume that any OpenFlow-enabled switch supports FLOOD port #3

Open
mentels opened this issue Oct 17, 2013 · 0 comments
Open

Do not assume that any OpenFlow-enabled switch supports FLOOD port #3

mentels opened this issue Oct 17, 2013 · 0 comments

Comments

@mentels
Copy link

mentels commented Oct 17, 2013

The controller tries to send messages on FLOOD port that is an optional one and is NOT supported by OpenFlow-only switches. If a controller wants to use this port it should first make sure that the switch supports it. It can also use the ALL port that every OpenFlow-enabled switch is required to implement. See the OpenFlow 1.3.0 specification ch. 4.5.
@mentels mentels mentioned this issue Oct 17, 2013
Merged
mentels pushed a commit to legoscia/LINC-Switch that referenced this issue Nov 11, 2013
Implement reserved OFP port FLOOD
6b12c79 
FLOOD port when used as an output port sends the packet out all standard
ports, but not the ingress port, nor ports that are in BLOCKED state
(OpenFlow spec. v1.3.2 ch. 4.5).
This behavior is required as NOX 1.3 controller uses this FLOOD port.
This commit should be reverted as soon as the issue
CPqD/nox13oflib#3 is fixed.
(Motivated by FlowForwarding#171).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mentels