<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Wed Feb 22 2017 11:13:18 GMT-0500
(EST), Anil Venkata:<br>
</div>
<blockquote
cite="mid:CAP7mkkCm2fRcwOC-MRN0Tx6x3EmbvGQEDChBZk9XsKD9tLAYGA@mail.gmail.com"
type="cite">
<div dir="ltr"><span class=""></span><br>
<span class=""></span>
While relevant, I think this is not possible until br-int allows
to match the network a packet belongs to (the ovsdb port tags
don't let you do that until the packet leaves br-int with a
NORMAL action).<br>
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
Ajo has told me yesterday that the OVS firewall driver
uses registers precisely to do that. Making this generic
(and not specific to the OVS firewall driver) would be a
prerequisite before you can add ARP responder rules in
br-int.<br>
<br>
</blockquote>
<div> </div>
<div>[...] Spoke to Ajo on this. He said we can follow above
suggestion i.e do the same what firewall driver is doing
in br-int, or wait till OVS flow extension is
implemented(but this will take time as lack of resources)</div>
</div>
</div>
</div>
</blockquote>
<br>
I think using registers instead of ovsdb port tags should be seen as
a common pre-requisite for both ARP responder in br-int and doing
the OVS flow extension work.<br>
So waiting for resource on the later should not be seen as the
problem.. although you still need some resource to use register in
br-int...<br>
<br>
-Thomas<br>
</body>
</html>