Additional configuration parameters that can be configured in the configuration file (org.onosproject.fwd.ReactiveForwarding.cfg),
that determine application behavior:
- packetOutOfppTable - application will use OFPP_TABLE port in PacketOut message, sending packet back to the OpenFlow pipeline, instead of using switch port
- flowTimeout - configuring reactively installed flow timeout
- flowPriority - configuring reactively installed flow priority
- matchDstMacOnly - reactively installed flows will match only destination MAC address - behavior as legacy L2 switches. This options overrides all other options below.
- matchVlanId - reactively installed flows will match default condition with additionally with VLAN ID field
- matchIpv4Address - reactively installed flows will match default conditions, plus IPv4 address and Protocol field
- matchIpv4Dscp - reactively installed flows will match default condition, IPv4 + with IPv4 DSCP and ECN fields (need matchIPv4Address enabled)
- matchIpv6Address - reactively installed flows will match default condition with IPv6 address and NextHeader field
- matchIpv6FlowLabel - reactively installed flows will match default condition with IPv6 address and IPv6 Flow Label (need matchIPv6Address enabled)
- matchTcpUdpPorts - reactively installed flows will match default condition with IPv4 or IPv6 address and TCP/UDP ports (need matchIPv4Address or matchIPv6Address enabled)
- matchIcmpFields - reactively installed flows will match default condition with IPv4 or IPv6 address and ICMP type and code fields (need matchIPv4Address or matchIPv6Address enabled)
Change-Id: Ieef67a1a12f6341d4de3b07e1226affec66d361a
The subsystem no longer returns futures for tracking completion of work.
Notifications are explicitely returned via a call back mechanism. Also, the
subsystem is now asynchronous.
Change-Id: I1a4cef931c24820f9ae9ed9a5398f163f05dfbc9
more flowservice improvements
Change-Id: I5c9c1b6be4b2ebfa523b64f6f52e7634b7d3e05f
more flowservice impl
Change-Id: I05f6774460effb53ced8c36844bcda2f8f6c096f
Manager to store functional (at least i believe it)
Change-Id: I09b04989bd1004c98fe0bafed4c76714b9155d53
flow subsystem functional: need to fix unit tests
Change-Id: I1667f25b91320f625a03e5e1d5e92823184d9de0
flow subsystem functional
Change-Id: I429b3335c16d4fc16f5d55f233dd37c4d1d6111d
finished refactor of flow subsystem
Change-Id: I1899abc6ff6a974a2018d936cc555049c70a6804
fix for null flow provider to use new api
Change-Id: If2fd9bd5baf74d9c61c5c8085cef8bc2d204cbdc
- Added configuration parameters for order of instances.
- got rid of 'flicker' flag since it's redundant.
Reference: ONOS-890
Change-Id: I0217e17f2a55d85e0a1fc8f2b3ea8cb54cb87517
- Number of devices per ONOS instance.
- Number of ports on the devices. This value is global.
The islands created by each instances' providers are joined together
in a chain (circle).
Reference : ONOS-860
Change-Id: I875ad1fbc1d4441869373c25de2ae5b62838e0d4
currently chains null devices together in a linear topology.
The tunable parameters for this provider are:
- flicker = [default false] : flap the links by sending LinkEvents
- eventRate = [default 3000] : time between LinkEvents, in msec
Reference: ONOS-446
Change-Id: I865c1c43c3216d9b64d67bda7c118bb041d5b1c9
org.onosproject.fwd.ReactiveForwarding.cfg
------------------------------------------
ipv6Forwarding = true
will enable IPv6 forwarding in ReactiveForwarder.
ONOS-506: Updates for the comment.
* ReactiveForwarding.java
Line 133: Make the comment to concrete Javadoc.
Line 134: Method is changed to static.
Line 141: Catch ClassCastException instead of generic Exception.
* org.onosproject.fwd.ReactiveForwarding.cfg
Line 3: Fix typo ;-).
Line 7: Add comment: the option affects both IPv4 and IPv6.
Change-Id: Ie7fdc7fc26c7d36b9633bfc828dffe27015214f7
Modified Version.java to allow 3-segment version.
Changed onos-next to onos as default for ONOS_ROOT.
Change-Id: Ifbde9dfbc7af9a5891e9f41db6932859c0f59660
* The (deployed) Interface addresses configuration file "addresses.json"
from the apps/config application is expected to be found in the
/opt/onos/config directory
* The (deployed) SDN-IP configuration file "sdnip.json" is expected
to be found in the /opt/onos/config directory
* All configuration files (i.e., addresses.json and sdnip.json) should
be stored in the tools/package/config directory before deployment
(i.e., before running onos-config)
* Removed the apps/config/src/main/resources/config.json sample configuration
file, because it was incorrect, and replaced it with "addresses.json"
file in the same directory
* Updated the text in files tools/package/config/README and
apps/sdnip/src/main/resources/config-examples/README
* Minor code cleanup in SdnIpConfigReader.java and NetworkConfigReader.java
Change-Id: I8af75e62a94e4fb701e2c6a09cde93cd8461e255
