Separation of ARP Responder from config.ini. It is an l3.fwd associated feature enabl... 56/22056/5
authorevvy <dhiraviam.natarajan@gmail.com>
Thu, 11 Jun 2015 20:42:57 +0000 (02:12 +0530)
committerGerrit Code Review <gerrit@opendaylight.org>
Wed, 5 Aug 2015 17:51:40 +0000 (17:51 +0000)
Change-Id: Ie29a751bcb372ef2f3dfd6b8f5e3ca7531359310
Signed-off-by: evvy <dhiraviam.natarajan@gmail.com>
karaf/opendaylight-karaf-resources/src/main/resources/etc/custom.properties

index a21e20ee035fc1c4902c85709d423d59b6184f8c..fe4cd42afe55f7f5ea7b377701ccc2aaffd99c78 100644 (file)
@@ -85,6 +85,9 @@ ovsdb.listenPort=6640
 # disabled by default.
 # ovsdb.l3.fwd.enabled=yes
 
+# ovsdb can be configured with ml2 to perform arp responder, enabled by default.
+ovsdb.l3.arp.responder.disabled=no
+
 # ovsdb can be configured with ml2 to perform l3 forwarding. When used in that scenario, the mac address of the default
 # gateway --on the external subnet-- is expected to be resolved from its inet address. The config below overrides that
 # specific arp/neighDiscovery lookup.