<div dir="ltr">I believe that is what Ben was saying. The link state is only for the internal interface and not the actual bridge itself.</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, May 28, 2019 at 1:24 PM Dan Sneddon <<a href="mailto:dsneddon@redhat.com">dsneddon@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="auto"><div dir="auto"><div dir="auto">Is this a case of confusion between the switch named br0 and an internal port on the switch named br0? I have found that many people are confused about that distinction, especially since ovs-vsctl will create the internal port automatically with the same name as the bridge.</div></div><div dir="auto"><br></div><div dir="auto">Shutting down the internal port does not shut down the bridge.</div><div dir="auto"><br></div><div dir="auto">In these steps from the original post:</div><div dir="auto"><br></div></div><blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px"><div>4) sudo ovs-vsctl add-br br0 -- add-port br0 eth0 -- add-port br0 intern-extern -- set interface intern-extern type=internal</div><div>5) sudo ip addr flush dev eth0 && sudo dhclient intern-extern</div><div>6) sudo ip link set down dev br0</div></blockquote><br><div>Step 4 creates bridge br0, and ovs-vsctl automatically creates internal port br0 on the switch, and exposes that port to the OS networking stack as a device. Step 6 shuts down that internal port, leaving the bridge still operational. There are use cases for operating a bridge without an internal interface, especially when using DPDK to avoid sending traffic to the kernel.</div><div><br></div><div>Please correct me if I have any of the above wrong, it's still somewhat confusing to me too, and I've been working with OVS for a long time.</div></div><div><div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, May 2, 2019 at 2:09 PM Ben Pfaff <<a href="mailto:blp@ovn.org" target="_blank">blp@ovn.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">OK.<br>
<br>
The problem here is conceptual. br0 is just a port on your virtual<br>
switch. It isn't along the path of your packet. It's like<br>
disconnecting the Ethernet cable from the management port of a physical<br>
switch: it doesn't disable traffic from flowing through the other ports.<br>
<br>
On Thu, May 02, 2019 at 03:49:22PM -0500, Christopher Seeley wrote:<br>
> I am pinging from another server connected to the same switch. I can ping<br>
> from inside of an LXC container > br0 > eth0 > physical switch > eth0 (on<br>
> the other server) > br0 (on the other server) > an LXC container (on the<br>
> other server). I have done this from both servers and it goes through no<br>
> matter the state of br0 on either of them.<br>
> <br>
> On Thu, May 2, 2019 at 3:32 PM Ben Pfaff <<a href="mailto:blp@ovn.org" target="_blank">blp@ovn.org</a>> wrote:<br>
> <br>
> > Please stop dropping the mailing list. I don't help off-list.<br>
> ><br>
> > On Thu, May 02, 2019 at 03:15:19PM -0500, Christopher Seeley wrote:<br>
> > > That is the problem. It's not the wrong traffic, just getting traffic<br>
> > when<br>
> > > the bridge is supposed to be down. Does an Open-vSwitch ever come down?<br>
> > The<br>
> > > interface state changes but the bridge state does not.<br>
> ><br>
> > You didn't answer my question. How is the ICMP traffic arriving? What<br>
> > command are you running?<br>
> ><br>
> <br>
> <br>
> -- <br>
> Christopher Seeley<br>
> Software Developer<br>
> M: (618) 975-6324<br>
> [image:<br>
> <a href="https://ci4.googleusercontent.com/proxy/N6FGWffGoRzwldCSUGY-TdS5283f1qufOUeSehWDEk0uSdTmwAA_U1NgdVoRvGNVWfWD0QpLQ4RcZ-UwUP30TUtlCy-HzoMxZUua7hmgR_NZwQTVmRIezA=s0-d-e1-ft#http://cybercents.com/assets/img/cybercents_logo_dark-ab5b14ef.png" rel="noreferrer" target="_blank">https://ci4.googleusercontent.com/proxy/N6FGWffGoRzwldCSUGY-TdS5283f1qufOUeSehWDEk0uSdTmwAA_U1NgdVoRvGNVWfWD0QpLQ4RcZ-UwUP30TUtlCy-HzoMxZUua7hmgR_NZwQTVmRIezA=s0-d-e1-ft#http://cybercents.com/assets/img/cybercents_logo_dark-ab5b14ef.png</a>]<br>
> 1472 North Green Mount Road<br>
> O'Fallon, IL 62269<br>
<br>
<br>
_______________________________________________<br>
discuss mailing list<br>
<a href="mailto:discuss@openvswitch.org" target="_blank">discuss@openvswitch.org</a><br>
<a href="https://mail.openvswitch.org/mailman/listinfo/ovs-discuss" rel="noreferrer" target="_blank">https://mail.openvswitch.org/mailman/listinfo/ovs-discuss</a><br>
</blockquote></div></div>
</div>
</div>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr">Christopher Seeley<div>Software Developer</div><div><span style="font-size:12.8px">M: (618) 975-6324</span><br></div><div><img src="cid:image002.png@01D2CA62.B546D690" alt="https://ci4.googleusercontent.com/proxy/N6FGWffGoRzwldCSUGY-TdS5283f1qufOUeSehWDEk0uSdTmwAA_U1NgdVoRvGNVWfWD0QpLQ4RcZ-UwUP30TUtlCy-HzoMxZUua7hmgR_NZwQTVmRIezA=s0-d-e1-ft#http://cybercents.com/assets/img/cybercents_logo_dark-ab5b14ef.png"><br></div><div><div style="font-size:12.8px">1472 North Green Mount Road</div><div style="font-size:12.8px">O'Fallon, IL 62269</div></div></div></div>