[ovs-discuss] Internal ports do not accept broadcast packages without service restart
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
correctly.
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|2|daemon_unix(monitor)|INFO|pid 1047 died,
exit status 0, exiting
2017-10-02T15:45:03.535Z|1|vlog|INFO|opened log file
/var/log/openvswitch/ovs-vswitchd.log
2017-10-02T15:45:03.537Z|2|ovs_numa|INFO|Discovered 1 CPU cores on NUMA
node 0
2017-10-02T15:45:03.537Z|3|ovs_numa|INFO|Discovered 1 NUMA nodes and 1
CPU cores
2017-10-02T15:45:03.538Z|4|reconnect|INFO|unix:/var/run/openvswitch/db.sock:
connecting...
2017-10-02T15:45:03.538Z|5|reconnect|INFO|unix:/var/run/openvswitch/db.sock:
connected
2017-10-02T15:45:03.543Z|6|ofproto_dpif|INFO|system@ovs-system:
Datapath supports recirculation
2017-10-02T15:45:03.543Z|7|ofproto_dpif|INFO|system@ovs-system: MPLS
label stack length probed as 1
2017-10-02T15:45:03.543Z|8|ofproto_dpif|INFO|system@ovs-system:
Datapath supports unique flow ids
2017-10-02T15:45:03.543Z|9|ofproto_dpif|INFO|system@ovs-system:
Datapath supports ct_state
2017-10-02T15:45:03.543Z|00010|ofproto_dpif|INFO|system@ovs-system:
Datapath supports ct_zone
2017-10-02T15:45:03.543Z|00011|ofproto_dpif|INFO|system@ovs-system:
Datapath supports ct_mark
2017-10-02T15:45:03.543Z|00012|ofproto_dpif|INFO|system@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
aa_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
080027237657
2017-10-02T15:45:03.554Z|00030|connmgr|INFO|br0: added service controller
"punix:/var/run/openvswitch/External0.mgmt"
2017-10-02T15:45:03.568Z|00033|bridge|INFO|ovs-vswitchd (Open vSwitch) 2.5.0
2017-10-02T15:45:03.569Z|1|ofproto_dpif_upcall(handler6)|INFO|received
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:
#!/bin/bash
name="tz4"
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,
Tugrul
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] Ip grouping in openflow rule
Many thanks for your replies. I will study on OVN. > On Feb 20, 2017, at 12:46 AM, Tugrul Erdogan wrote: > > Hi all, > > I am working on Centos 7 with OVS. I have simple flow rules as stated below: > > ovs-ofctl add-flow ovs-brext "ip, nw_dst=10.3.4.6, actions=drop" > ovs-ofctl add-flow ovs-brext "ip, nw_dst=172.16.0.6, actions=drop" > > I want to group the destinations IP addresses in a structure ( like > netfilter:ipset ) so I can drop many of the IP addresses from > different subnets with one flow rule. I have searched this type of > structure in man page of ovs-ctl and ovs-ofctl but I could not find. > > I want take your suggestions about IP grouping structure in flow rules. As Ben mentioned, there's no such grouping mechanism using ovs-ofctl. Those tools are stateless, and OVS would normally expect that sort of state to be maintained by a controller. There is support for such groups in OVN (which acts as a controller), but that might be overkill for your application if you don't need full-blown network virtualization. I have thought about how using just the southbound components of OVN could make a more convenient method of programming OVS. I should do a talk around that at some point, because I think the OVN logical flows are better in a lot of ways than straight OpenFlow. --Justin ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
[ovs-discuss] Ip grouping in openflow rule
Hi all, I am working on Centos 7 with OVS. I have simple flow rules as stated below: ovs-ofctl add-flow ovs-brext "ip, nw_dst=10.3.4.6, actions=drop" ovs-ofctl add-flow ovs-brext "ip, nw_dst=172.16.0.6, actions=drop" I want to group the destinations IP addresses in a structure ( like netfilter:ipset ) so I can drop many of the IP addresses from different subnets with one flow rule. I have searched this type of structure in man page of ovs-ctl and ovs-ofctl but I could not find. I want take your suggestions about IP grouping structure in flow rules. Thanks for your replies, Best regards, Tugrul ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
