Change behavior when handling an OFPBAC_BAD_OUT_PORT

kytos / flow_manager

MIT License

1 stars 16 forks source link

Change behavior when handling an OFPBAC_BAD_OUT_PORT #92

Closed josemauro closed 3 years ago

josemauro commented 4 years ago

This PR is an improvement of PR https://github.com/kytos/flow_manager/pull/88 that changes the behavior when handling an OFPBAC_BAD_OUT_PORT error message, checking the interface config with OFPPC_NO_FWD flag.

Fix kytos/of_core#80

josemauro commented 4 years ago

The last commit is broken because the changes in python-openflow (https://github.com/kytos/python-openflow/pull/618) have to be accepted first.

josemauro commented 4 years ago

@hdiogenes I applied your suggestions and squashed the commits.

josemauro commented 4 years ago

As @hdiogenes mentioned in https://github.com/kytos/python-openflow/pull/618 , we don't need add the complexity to handle with different versions of openflow to fetch the OFPBAC_BAD_OUT_PORT and OFPPC_NO_FWD.