From 6398dd9766e41a8e3a70687d6c720b79f3e8b5f0 Mon Sep 17 00:00:00 2001 From: evvy Date: Fri, 12 Jun 2015 02:12:57 +0530 Subject: [PATCH] Separation of ARP Responder from config.ini. It is an l3.fwd associated feature enabled by default Change-Id: Ie29a751bcb372ef2f3dfd6b8f5e3ca7531359310 Signed-off-by: evvy --- .../src/main/resources/etc/custom.properties | 3 +++ 1 file changed, 3 insertions(+) diff --git a/karaf/opendaylight-karaf-resources/src/main/resources/etc/custom.properties b/karaf/opendaylight-karaf-resources/src/main/resources/etc/custom.properties index a21e20ee03..fe4cd42afe 100644 --- a/karaf/opendaylight-karaf-resources/src/main/resources/etc/custom.properties +++ b/karaf/opendaylight-karaf-resources/src/main/resources/etc/custom.properties @@ -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. -- 2.36.6