<html><head></head><body><div style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:13px;"><div></div>
            <div>Indeed, with 4.15 it works</div><div>In my former kernel 4.9, the net.ipv4.tcp_l3mdev_accept was missing. </div><div><br></div><div>That's the cause or 4.15 has another vrf implementation?<br></div><div><br></div><div><br></div><div><br></div>
            
            <div id="ydp4b77a2b9yahoo_quoted_0606331805" class="ydp4b77a2b9yahoo_quoted">
                <div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
                    
                    <div>
                        On Friday, March 9, 2018, 12:31:12 AM GMT+2, Ondrej Zajicek <santiago@crfreenet.org> wrote:
                    </div>
                    <div><br></div>
                    <div><br></div>
                    <div>On Thu, Mar 08, 2018 at 09:55:03PM +0000, Ticlea Alexandru wrote:<br clear="none">> Hello <br clear="none">> Is possible to run ospf instance over an interface which is part of an VRF?I make a config but I see I see no package from local instance on VRF interfaceThe log shows the Hello package are sent out using physical interface<br clear="none">> Config is like <br clear="none"><br clear="none">Hello<br clear="none"><br clear="none">It should work, but require recent kernel. Works for me on 4.14.13,<br clear="none">i think (but not sure) it would work on 4.13, but not older.<br clear="none"><br clear="none"><br clear="none">> ipv4 table vrf_private;<br clear="none">> <br clear="none">> protocol kernel kernel_vrf_private  {<br clear="none">>         scan time 1;<br clear="none">>         vrf "vrf-private";<br clear="none">>         #kernel table 200;<br clear="none"><br clear="none">You should specify the kernel table associated with the VRF.<div class="ydp4b77a2b9yqt9882488520" id="ydp4b77a2b9yqtfd12512"><br clear="none"><br clear="none"><br clear="none">> protocol ospf ospf_local_core  {<br clear="none">>                 vrf "vrf-private";<br clear="none">>                 ipv4 {<br clear="none">>                         table vrf_private;<br clear="none">>                         import all;<br clear="none">>                         export all;<br clear="none">>                 };<br clear="none">>                 disabled off;<br clear="none">>                 instance id 0;<br clear="none">>                 debug {<br clear="none">>                       states,<br clear="none">>                       routes,<br clear="none">>                       filters,<br clear="none">>                       interfaces,<br clear="none">>                       events,<br clear="none">>                       packets<br clear="none">>                         };<br clear="none">>                 area 0.0.0.0 {<br clear="none">>                         interface  1.2.3.0/24, "ens256", "vrf-private" , 172.31.254.0/24 {</div><br clear="none"><br clear="none">I would not add "vrf-private" interface as an active OSPF interface. Just<br clear="none">the regular interfaces that are a part of the VRF.<br clear="none"><br clear="none">-- <br clear="none">Elen sila lumenn' omentielvo<br clear="none"><br clear="none">Ondrej 'Santiago' Zajicek (email: <a shape="rect" href="mailto:santiago@crfreenet.org" rel="nofollow" target="_blank">santiago@crfreenet.org</a>)<br clear="none">OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net)<br clear="none">"To err is human -- to blame it on a computer is even more so."</div>
                </div>
            </div></div></body></html>