[ovs-discuss] Router not allowing traffic in reverse
I have setup OpenStack with OVS. I have a single Hyper-V server running the controller and three CentOS instances(10.0.0.x) on a private subnet. I created a router in OpenStack with SNAT disabled, as I only want it to route traffic between the private subnet(10.0.0.x) and the external subnet(172.16.1.x)/internet. All of the instances can ping each other along with the external network(172.16.1.x). From the external network, I can ping the interface of the ovs router on the external network. I can not though ping inside the private network. A trace route stops at the IP of the OVS router. With wireshark, I do not see anything coming from the external pcs IP. If I trace route it, I see packets making all the way to the OVS router and then stop. Since I can ping one way, and not the other; I believe there is something in the router/OVS that is stopping the packets to route into the private subnet. What do I need to look at? (I have disabled all firewalls on all OSes involved.) Here is a sudo design of the setup. Does respond to ping VMOVS Router priv intOVS Router ext intExternal PC 10.0.0.14 -> 10.0.0.1-> 172.16.1.1 -> 172.16.1.10 Does not respond to ping External PCOVS Router ext intOVS Router priv int VM 172.16.1.10 -> 172.16.1.1 -> 10.0.0.1-> 10.0.0.14 ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
[ovs-discuss] Open vSwitch 2.11.0 Available
The Open vSwitch team is pleased to announce the release of Open vSwitch 2.11.0: http://openvswitch.org/releases/openvswitch-2.11.0.tar.gz A few other feature highlights of 2.11.0 include: - OVN support for encrypted tunnels between hypervisors. - Improved IPAM support in OVN. - New OpenFlow feature support. - Support for DPDK 18.11. - Linux kernel support up to 4.18. - And many others. See the full change log here: http://openvswitch.org/releases/NEWS-2.11.0 Enjoy! --The Open vSwitch Team Open vSwitch is a production quality, multilayer open source virtual switch. It is designed to enable massive network automation through programmatic extension, while still supporting standard management interfaces. Open vSwitch can operate both as a soft switch running within the hypervisor, and as the control stack for switching silicon. It has been ported to multiple virtualization platforms and switching chipsets. ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] How to send information from ovs to controller through Openflow
On Thu, Feb 28, 2019 at 12:49:27AM +0700, Tuyen Dinh wrote: > I'm doing a project that need to modify ovs source code to do some > statistics about the packets (which I can't get that information from flow > tables). After get that statistics , I need to send them to the controller. > As far as I know, Openvswitch has the vswitchd deamon which communicate > with the controller through Openflow protocol. How can I add a new type of > Openflow message or modify an available message to attach that information > and send to the controller? Where is the function or module in Openvswitch > responsible for that job? This is in the FAQ. ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
[ovs-discuss] How to send information from ovs to controller through Openflow
Hi, I'm doing a project that need to modify ovs source code to do some statistics about the packets (which I can't get that information from flow tables). After get that statistics , I need to send them to the controller. As far as I know, Openvswitch has the vswitchd deamon which communicate with the controller through Openflow protocol. How can I add a new type of Openflow message or modify an available message to attach that information and send to the controller? Where is the function or module in Openvswitch responsible for that job? Any help would be appreciated. ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] ovs-ofctl fails occasionally
On Wed, Feb 27, 2019 at 12:45:58PM +, Ken Ajiro wrote:
>
> Hello,
>
> When I use ovs-ofctl on OVS 2.10.1, it failed occasionally by error:
>
> ovs-ofctl: br0: failed to connect to socket (Broken pipe)
>
> This error is possible to be reproduced with:
>
> # while :; do /opt/nec/pf/ds/bin/ovs-ofctl --timeout=5 dump-flows br0 >
> /tmp/log || break; done; cat /tmp/log
> ovs-ofctl: br0: failed to connect to socket (Broken pipe)
>
> Also I tried with OVS 2.4.1 and could not reproduce this error.
>
> I think that recently rconn.c was modified on commit
> 476d2551abd2871696a64203f78d658ac2d7f32c
> and the connection for ofctl was changed it begins on state S_CONNECTING
> instead of S_ACTIVE.
> So timeout_CONNECTING will be applied for ofctl connection, however
> timeout_CONNECTING is 1
> and this is too short (e.g. if transition time of CONNCTING was
> 12:00:00.999, it will be timed out
> after 1ms). I think that this is cause of occasionally disconnection of
> ofctl.
Thanks for the report.
It seems to me that the right long-term fix is to use higher resolution
(e.g. millisecond resolution) to measure the timeouts. However, that
will be a relatively large fix.
The following stopgap appears to fix the problem on master. I suspect
it could be easily backported as far as necessary. Does it work for you
too?
diff --git a/lib/rconn.c b/lib/rconn.c
index 48ae8c6a72e5..8ca23cbcfe90 100644
--- a/lib/rconn.c
+++ b/lib/rconn.c
@@ -502,7 +502,7 @@ static unsigned int
timeout_CONNECTING(const struct rconn *rc)
OVS_REQUIRES(rc->mutex)
{
-return MAX(1, rc->backoff);
+return MAX(2, rc->backoff);
}
static void
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
[ovs-discuss] ovs-vswitch.log miss_upcall and ARP reply issue
Hi All, Just wondering where to start looking for a answer to the following issue: When performing an ARP request on a specific host (11.0.0.1) we're seeing the responses returned on the expected virtual NIC via tcpdump. However the ARP request isn't been passed up to the controller. The switch and controller are running inside a qemu VM running under GNS3. The 11.0.0.1 host VM is running an FRR. Other containers connected to the switch seem to behave as expected. Enabling debugging in the vswitchd logs we're seeing the following entry every time an arp request is made. 019-02-27T04:01:14.457Z|00070|dpif(handler7)|DBG|system@ovs-system: miss upcall: recirc_id(0),dp_hash(0),skb_priority(0),in_port(3),skb_mark(0),ct_state(0),ct_zone(0),ct_mark(0),ct_label(0),eth(src=0c:78:0a:9a:65:00,dst=0c:20:35:97:6b:00),eth_type(0x0806),arp(sip=11.0.0.1,tip=11.0.0.2,op=2,sha=0c:78:0a:9a:65:00,tha=0c:20:35:97:6b:00) arp,vlan_tci=0x,dl_src=0c:78:0a:9a:65:00,dl_dst=0c:20:35:97:6b:00,arp_spa=11.0.0.1,arp_tpa=11.0.0.2,arp_op=2,arp_sha=0c:78:0a:9a:65:00,arp_tha=0c:20:35:97:6b:00 I'm guessing this is the issue but what could cause the upcall to be missed? We're running ovs 2.8.1 under Fedora 28. Thanks Leigh ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
[ovs-discuss] ovs-ofctl fails occasionally
Hello, When I use ovs-ofctl on OVS 2.10.1, it failed occasionally by error: ovs-ofctl: br0: failed to connect to socket (Broken pipe) This error is possible to be reproduced with: # while :; do /opt/nec/pf/ds/bin/ovs-ofctl --timeout=5 dump-flows br0 > /tmp/log || break; done; cat /tmp/log ovs-ofctl: br0: failed to connect to socket (Broken pipe) Also I tried with OVS 2.4.1 and could not reproduce this error. I think that recently rconn.c was modified on commit 476d2551abd2871696a64203f78d658ac2d7f32c and the connection for ofctl was changed it begins on state S_CONNECTING instead of S_ACTIVE. So timeout_CONNECTING will be applied for ofctl connection, however timeout_CONNECTING is 1 and this is too short (e.g. if transition time of CONNCTING was 12:00:00.999, it will be timed out after 1ms). I think that this is cause of occasionally disconnection of ofctl. Thanks, -- Ken Ajiro ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
