Versions Compared

Old Version 1

changes.mady.by.user Ayaka Koshibe

Saved on

compared with

New Version Current

changes.mady.by.user Pavlin Radoslavov

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Removed ONOS-1.1 related section (IPv6)

...

After ping is stopped, those flow entries should expire within 10 seconds. This expiration time period is configurable.

IPv6

Description

IPv6 support is an experimental feature that is disabled by default. Currently, the following IPv6-related features have been implemented and tested:

  • IPv6 Host Discovery
  • IPv6-to-MAC Address Resolution
  • IPv6 Reactive Forwarding
  • IPv6 Routes for the ONOS SDN-IP Use Case

...

IPv6 Host Discovery support can be enabled in the org.onosproject.provider.host.impl.HostLocationProvider.cfg configuration file. A sample of that file can be found in the tools/package/etc/samples directory. The file should be copied to the tools/package/etc directory and the following option should be enabled:

Code Block
languagetext
ipv6NeighborDiscovery = true

...

 

IPv6-to-MAC Address Resolution support can be enabled in the org.onosproject.proxyarp.ProxyArp.cfg configuration file. A sample of that file can be found in the tools/package/etc/samples directory. The file should be copied to the tools/package/etc directory and the following option should be enabled:

 

Code Block
languagetext
ipv6NeighborDiscovery = true
Tip
titleIPv6 Neighbor Discovery Config

For all practical purposes, the ipv6NeighborDiscovery  option should be set to true in both files listed above: org.onosproject.provider.host.impl.HostLocationProvider.cfg and org.onosproject.proxyarp.ProxyArp.cfg.

...

IPv6 Reactive Forwarding can be enabled and configured in the org.onosproject.fwd.ReactiveForwarding.cfg configuration file. A sample of that file can be found in the tools/package/etc/samples directory. The file should be copied to the tools/package/etc directory and configured as appropriate. All configuration options are listed and described inside that file.

 

Tip
titleIPv6 Reactive Forwarding Config

It is recommended to enable the following two configuration options. The result Flow Entries will have the IPv6 source and destination addresses in the matching conditions:

 

ipv6Forwarding = true
matchIpv6Address = true

...

Currently, there is no explicit configuration to enable IPv6 routes for the SDN-IP Use Case. BGP-originated IPv6 routes are received in BGP Multiprotocol Extension Capabilities from any BGP peer that advertises them. Such IPv6 routes are handled and processed similarly to the IPv4.

 

Tip
titleIPv6 SDN-IP Config

Currently, the receiving of BGP IPv6 routes (BGP UPDATEs) has been tested only over IPv4 BGP peering sessions. Such sessions might have to be explicitly configured for such purpose. Below is a sample configuration file for the Quagga BGP  implementation:

 
hostname bgp2e
password xxxxxx
router bgp 65002
  bgp router-id 10.0.0.2
  bgp scan-time 5
  timers bgp 10 30
  neighbor 10.0.0.1 remote-as 65001
  neighbor 10.0.0.1 timers connect 3
  neighbor 10.0.0.1 advertisement-interval 3
  network 12.0.0.0/24
  address-family ipv6
  network 2001:db8:1:2::/64
  neighbor 10.0.0.1 activate
  neighbor 10.0.0.1 route-map ipv6-nexthop out
  exit-address-family
route-map ipv6-nexthop permit 10
 set ipv6 next-hop global 2012::2
log stdout
 

Previous : Applications and Use Cases
Next : Appendix A: CLI commands

...