DHCPv[46] relay must replace the route instead of adding an extra NH
Currently DHCP relay adds an extra next-hop to an already existing route (if any). Instead
it must replace it with the new one.
This patch adds replaceRoute method to the RouteStore interface and corresponding implementations.
The DHCP relay implementation uses the new method instead of updateRoute
Change-Id: I601613168b83290db4e53d2aae5c86e963ae17b0
11 files changed
tree: 80f67af96fe4af84526f21e46371f541d99470ce
- .buckconfig
- .dockerignore
- .gitignore
- .gitreview
- BUCK
- Dockerfile
- Jenkinsfile
- LICENSE.txt
- README.md
- apps/
- buck-tools/
- bucklets/
- cli/
- core/
- docs/
- drivers/
- features/
- incubator/
- lib/
- models/
- modules.defs
- onos.defs
- pipelines/
- pom.xml
- protocols/
- providers/
- tools/
- utils/
- web/
README.md
ONOS : Open Network Operating System
What is ONOS?
ONOS is a new SDN network operating system designed for high availability, performance, scale-out.
Top-Level Features
- High availability through clustering and distributed state management.
- Scalability through clustering and sharding of network device control.
- Performance that is good for a first release, and which has an architecture that will continue to support improvements.
- Northbound abstractions for a global network view, network graph, and application intents.
- Pluggable southbound for support of OpenFlow and new or legacy protocols.
- Graphical user interface to view multi-layer topologies and inspect elements of the topology.
- REST API for access to Northbound abstractions as well as CLI commands.
- CLI for debugging.
- Support for both proactive and reactive flow setup.
- SDN-IP application to support interworking with traditional IP networks controlled by distributed routing protocols such as BGP.
- IP-Optical use case demonstration.
Checkout our website and our tools