[ovs-discuss] Internal ports do not accept broadcast packages without service restart

Tugrul Erdogan h.tugrul.erdogan at gmail.com
Fri Oct 6 14:42:42 UTC 2017

Hi all,

I want to take your helps about my openvswitch bridged network
configuration. I want to use ovs internal ports to split traffic. Except
inserting a new ovs internal port to existing ovs bridge, everything works

My problem is that whenever insert a new ovs internal port to the existing
ovs bridge, the boadcast packages (arp requests etc..) do not forward to
the new internal ovs port. On that time I can see that the broadcast
packages are being forwarded to earlier ovs internal ports.

If I restart the openvswitch service, the broadcast packages are forwarded
to the new ovs internal port. The restart logs can be seen at the below:

2017-10-02T15:45:03.350Z|00002|daemon_unix(monitor)|INFO|pid 1047 died,
exit status 0, exiting
2017-10-02T15:45:03.535Z|00001|vlog|INFO|opened log file
2017-10-02T15:45:03.537Z|00002|ovs_numa|INFO|Discovered 1 CPU cores on NUMA
node 0
2017-10-02T15:45:03.537Z|00003|ovs_numa|INFO|Discovered 1 NUMA nodes and 1
CPU cores
2017-10-02T15:45:03.543Z|00006|ofproto_dpif|INFO|system at ovs-system:
Datapath supports recirculation
2017-10-02T15:45:03.543Z|00007|ofproto_dpif|INFO|system at ovs-system: MPLS
label stack length probed as 1
2017-10-02T15:45:03.543Z|00008|ofproto_dpif|INFO|system at ovs-system:
Datapath supports unique flow ids
2017-10-02T15:45:03.543Z|00009|ofproto_dpif|INFO|system at ovs-system:
Datapath supports ct_state
2017-10-02T15:45:03.543Z|00010|ofproto_dpif|INFO|system at ovs-system:
Datapath supports ct_zone
2017-10-02T15:45:03.543Z|00011|ofproto_dpif|INFO|system at ovs-system:
Datapath supports ct_mark
2017-10-02T15:45:03.543Z|00012|ofproto_dpif|INFO|system at ovs-system:
Datapath supports ct_label
2017-10-02T15:45:03.553Z|00013|bridge|INFO|bridge br0: added interface
External0 on port 65534
2017-10-02T15:45:03.553Z|00014|bridge|INFO|bridge br0: added interface
testtt_ext on port 2
2017-10-02T15:45:03.553Z|00015|bridge|INFO|bridge br0: added interface
tz_ext on port 5
2017-10-02T15:45:03.553Z|00016|bridge|INFO|bridge br0: added interface
tz3_ext on port 7
2017-10-02T15:45:03.553Z|00017|bridge|INFO|bridge br0: added interface
tz2_ext on port 6
2017-10-02T15:45:03.553Z|00018|bridge|INFO|bridge br0: added interface
aaaaaa_ext on port 3
2017-10-02T15:45:03.553Z|00019|bridge|INFO|bridge br0: added interface
enp0s8 on port 1
2017-10-02T15:45:03.553Z|00020|bridge|INFO|bridge br0: added interface
test3_ext on port 4
2017-10-02T15:45:03.554Z|00029|bridge|INFO|bridge br0: using datapath ID
2017-10-02T15:45:03.554Z|00030|connmgr|INFO|br0: added service controller
2017-10-02T15:45:03.568Z|00033|bridge|INFO|ovs-vswitchd (Open vSwitch) 2.5.0
packet on unassociated datapath port 0
2017-10-02T15:45:13.571Z|00034|memory|INFO|36092 kB peak resident set size
after 10.0 seconds
2017-10-02T15:45:13.571Z|00035|memory|INFO|handlers:1 ports:16
revalidators:1 rules:10 udpif keys:2
2017-10-02T15:45:33.585Z|00036|stp|INFO|External0: detected topology change.

And my test script:



ovs-vsctl add-port br0 ${name}  -- set Interface ${name} type=internal
ovs-vsctl mod-port br0 ${name} up

ifconfig ${name} up
ifconfig br0 up

How can I provide broadcast packet forwarding to the just inserted ovs
internal bridge without resarting openvswitch service.

Thanks for your helps,

Best Regards,

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openvswitch.org/pipermail/ovs-discuss/attachments/20171006/7aa1ea01/attachment.html>

More information about the discuss mailing list