date:20180104

Re: [ovs-discuss] Any timeline on PISCES in the mainline OVS?

2018-01-04 Thread Ben Pfaff

On Wed, Jan 03, 2018 at 08:54:25PM +0100, Alan Kayahan wrote:
> I read about PISCES and watched its presentation. The presenter mentioned
> that the PISCES is expected to be in the mainline OVS. Is there any news
> regarding that, or regarding any kind of P4 integration?

It's a goal of mine for 2.10.

> Would it be appropriate to use this mailing list to ask questions about
> PISCES as its git looks rather dormant?

Sure.
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Re: [ovs-discuss] OVS configuration problem with Debian-Proxmox

2018-01-04 Thread Marc-Henri Pamiseux

Hi,

Thanks for your answer.

There have been some changes since my first email. Rather than testing
on the physical machine, I preferred to reproduce the error on a virtual
machine. It is on this virtual machine that I have these ping errors.

Scott Lowe replied that as part of an installation of OVS on a virtual
machine it is imperative to put the network interfaces in promiscuous
mode. Since I did that, the ping works correctly on the virtual machine.

So I reproduced this configuration on the physical machine and there, I
am dependent of my ISP's environment. It does not work but i'll try some
configurations before.

Thanks,
-- 
Marc-Henri Pamiseux - SARL Libricks - www.libricks.fr
6 rue Léonard de Vinci - CS 20119, 53001 LAVAL Cedex
Tel. : 02.30.96.15.24 / Mobile : 06.26.71.30.97

Le 04/01/2018 à 21:10, Blue Lang a écrit :
> Hey Marc,
> 
> There is too much going on to debug this via email. The first place I'd
> look is on the proxmox message boards. 
> 
> Is something else answering ARP for 192.168.72.125?
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Re: [ovs-discuss] OVS configuration problem with Debian-Proxmox

2018-01-04 Thread Blue Lang

Hey Marc,

There is too much going on to debug this via email. The first place I'd
look is on the proxmox message boards.

Is something else answering ARP for 192.168.72.125?

On Thu, Jan 4, 2018 at 8:57 AM, Marc-Henri Pamiseux <
marc-henri.pamis...@libricks.org> wrote:

> Hello,
>
> I am experiencing a very strange behavior of OVS with the previous
> configuration.
> In fact my interfaces manage to send an ICMP-> echo_request and receive
> an ICMP-> echo_reply only six times every fifty packets.
>
> Look, I start a ping from my computer just after restarting the server:
> $ ping 192.168.72.125
> PING 192.168.72.125 (192.168.72.125) 56(84) bytes of data.
> From 192.168.72.104 icmp_seq=10 Destination Host Unreachable
> From 192.168.72.104 icmp_seq=11 Destination Host Unreachable
> From 192.168.72.104 icmp_seq=12 Destination Host Unreachable
> 64 bytes from 192.168.72.125: icmp_seq=13 ttl=64 time=2003 ms
> 64 bytes from 192.168.72.125: icmp_seq=14 ttl=64 time=1003 ms
> 64 bytes from 192.168.72.125: icmp_seq=15 ttl=64 time=3.35 ms
> 64 bytes from 192.168.72.125: icmp_seq=16 ttl=64 time=0.262 ms
> 64 bytes from 192.168.72.125: icmp_seq=17 ttl=64 time=0.232 ms
> 64 bytes from 192.168.72.125: icmp_seq=18 ttl=64 time=0.133 ms
> 64 bytes from 192.168.72.125: icmp_seq=19 ttl=64 time=0.263 ms
> 64 bytes from 192.168.72.125: icmp_seq=20 ttl=64 time=0.254 ms
> -> Nothing beetween theses lines
> 64 bytes from 192.168.72.125: icmp_seq=78 ttl=64 time=0.720 ms
> 64 bytes from 192.168.72.125: icmp_seq=79 ttl=64 time=0.266 ms
> 64 bytes from 192.168.72.125: icmp_seq=80 ttl=64 time=0.247 ms
> 64 bytes from 192.168.72.125: icmp_seq=81 ttl=64 time=0.245 ms
> 64 bytes from 192.168.72.125: icmp_seq=82 ttl=64 time=0.248 ms
> 64 bytes from 192.168.72.125: icmp_seq=83 ttl=64 time=0.258 ms
> -> Nothing beetween theses lines
> 64 bytes from 192.168.72.125: icmp_seq=141 ttl=64 time=0.686 ms
> 64 bytes from 192.168.72.125: icmp_seq=142 ttl=64 time=0.265 ms
> 64 bytes from 192.168.72.125: icmp_seq=143 ttl=64 time=0.196 ms
> 64 bytes from 192.168.72.125: icmp_seq=144 ttl=64 time=0.232 ms
> 64 bytes from 192.168.72.125: icmp_seq=145 ttl=64 time=0.235 ms
> 64 bytes from 192.168.72.125: icmp_seq=146 ttl=64 time=0.263 ms
>
> strange is not it?
> --
> Marc-Henri Pamiseux - SARL Libricks - www.libricks.fr
> 6 rue Léonard de Vinci - CS 20119, 53001 LAVAL Cedex
> Tel. : 02.30.96.15.24 / Mobile : 06.26.71.30.97
> ___
> discuss mailing list
> disc...@openvswitch.org
> https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
>



-- 
Blue Lang
PM *| *Veracity

3423 Piedmont Rd NE

Suite 350

Atlanta, GA  30305
Cell:  (770) 265-1381 <+17702651381>
https://www.linkedin.com/in/bluelang/
b...@veracity.io
www.veracity.io
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Re: [ovs-discuss] interface can't be connected after attached to bridge

2018-01-04 Thread Vishal Deep Ajmera

Hi Greg,

Please refer to “Common Configuration Issues” page on OpenvSwitch. This issue 
is listed as very first one ☺.

http://docs.openvswitch.org/en/latest/faq/issues/

Warm Regards,
Vishal Ajmera

From: ovs-discuss-boun...@openvswitch.org 
[mailto:ovs-discuss-boun...@openvswitch.org] On Behalf Of Gregory Rose
Sent: Friday, December 29, 2017 10:53 PM
To: netsurfed ; ovs-discuss 
Subject: Re: [ovs-discuss] interface can't be connected after attached to bridge

On 12/26/2017 12:08 AM, netsurfed wrote:

Hi all,
  I have a physical interface with an IP, and can connect with another machine 
by "ping" cmd.
However, after adding to a ovs bridge, It can no longer be connected with any 
other machine by "ping" cmd, although the IP is still there.
  I wonder if this is normal ? And why not be connected by "ping" cmd ?
  THX.

I tried to monitor the interface with "tcpdump". The target machine has 
returned the ARP Reply, but the HWaddress in ARP is still incomplete.

My OVS version is "2.8.90", and OS is "Ubuntu 16.04.2 LTS".
root@node26:~# uname -a
Linux node26 4.4.0-62-generic #83-Ubuntu SMP Wed Jan 18 14:10:15 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

[cid:image001.png@01D385B0.10783CD0]




___

discuss mailing list

disc...@openvswitch.org

https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Once you assign a physical interface to a bridge, any bridge, not just OVS 
bridges, then you need to reassign the IP address to the bridge and remove it 
from the physical interface.

There is a lot of documentation out there on how to configure bridges.

https://help.ubuntu.com/community/NetworkConnectionBridge

Thanks,

- Greg
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Re: [ovs-discuss] Bridge not working..

2018-01-04 Thread Vishal Deep Ajmera

Hi Steven,

Could you please dump the “ip route” table of kernel on the host ? I am 
suspecting if gateway configuration (10.80.180.1) on kitbr0 is causing an 
issue. Can you try removing the gateway configuration and verify again ?

Warm Regards,
Vishal Ajmera

From: ovs-discuss-boun...@openvswitch.org 
[mailto:ovs-discuss-boun...@openvswitch.org] On Behalf Of Steven Pollock
Sent: Thursday, January 04, 2018 11:21 AM
To: ovs-discuss@openvswitch.org
Subject: [ovs-discuss] Bridge not working..

Hopefully this is the correct mailing list, there is no description on the 
admin page.

Running on Ubuntu 16.04 on top of vmware.

ens192 is connect to the 10.80.180.0/24 network
ens224 is connected to a standard vswitch4, and a windows machine is also 
connected to vswitch4

I expected packets from the windows machine 10.80.180.222 to pass through 
kitbr0 to any devices on the 10.80.180.0/24 network 
connected on ens192

Here is the /etc/network/interfaces


auto ens192

iface ens192 inet manual

auto ens224

iface ens224 inet manual



auto kitbr0

allow-ovs kitbr0

iface kitbr0 inet static

address 10.80.180.223

netmask 255.255.255.0

gateway 10.80.180.1

 ovs_type OVSBridge

 ovs_ports ens192 ens224


I also note that the mac address on the bridge and ens224 are the same.

The windows machine off ens224 can ping the bridge at 10.80.180.223
The devices off ens192 (the rest of the 10.80.180.x network) cannot ping 
10.80.180.223 however


ens192Link encap:Ethernet  HWaddr 00:50:56:ab:e2:5b

  inet6 addr: fe80::250:56ff:feab:e25b/64 Scope:Link

  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

  RX packets:74 errors:0 dropped:0 overruns:0 frame:0

  TX packets:369 errors:0 dropped:0 overruns:0 carrier:0

  collisions:0 txqueuelen:1000

  RX bytes:4964 (4.9 KB)  TX bytes:35695 (35.6 KB)



ens224Link encap:Ethernet  HWaddr 00:50:56:ab:46:85

  inet6 addr: fe80::250:56ff:feab:4685/64 Scope:Link

  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

  RX packets:289 errors:0 dropped:0 overruns:0 frame:0

  TX packets:166 errors:0 dropped:0 overruns:0 carrier:0

  collisions:0 txqueuelen:1000

  RX bytes:26138 (26.1 KB)  TX bytes:15431 (15.4 KB)



kitbr0Link encap:Ethernet  HWaddr 00:50:56:ab:46:85

  inet addr:10.80.180.223  Bcast:10.80.180.255  Mask:255.255.255.0

  inet6 addr: fe80::250:56ff:feab:4685/64 Scope:Link

  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

  RX packets:349 errors:0 dropped:37 overruns:0 frame:0

  TX packets:96 errors:0 dropped:0 overruns:0 carrier:0

  collisions:0 txqueuelen:1

  RX bytes:25386 (25.3 KB)  TX bytes:10749 (10.7 KB)



root@ovs:/etc/network# ovs-vsctl show

3a6b26a7-6e7a-44fd-8893-65f2c8fac4f2

Bridge "kitbr0"

Port "kitbr0"

Interface "kitbr0"

type: internal

Port "ens192"

Interface "ens192"

Port "ens224"

Interface "ens224"

ovs_version: "2.5.2"


Any clues about what is going are much appreciated. (I do not have a controller 
at this time)

thanks,

-Steve


___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Re: [ovs-discuss] Bridge not working..

2018-01-04 Thread Scott Lowe


> On Jan 3, 2018, at 10:51 PM, Steven Pollock  wrote:
> 
> Hopefully this is the correct mailing list, there is no description on the 
> admin page.
> 
> Running on Ubuntu 16.04 on top of vmware.
> 
> ens192 is connect to the 10.80.180.0/24 network
> ens224 is connected to a standard vswitch4, and a windows machine is also 
> connected to vswitch4
> 
> I expected packets from the windows machine 10.80.180.222 to pass through 
> kitbr0 to any devices on the 10.80.180.0/24 network connected on ens192
> 
> Here is the /etc/network/interfaces
> 
> auto ens192
> iface ens192 inet manual
> 
> auto ens224
> iface ens224 inet manual
> 
> auto kitbr0
> allow-ovs kitbr0
> iface kitbr0 inet static
> address 10.80.180.223
> netmask 255.255.255.0
> gateway 10.80.180.1
>  ovs_type OVSBridge
>  ovs_ports ens192 ens224
> 
> 
> I also note that the mac address on the bridge and ens224 are the same.
> 
> The windows machine off ens224 can ping the bridge at 10.80.180.223
> The devices off ens192 (the rest of the 10.80.180.x network) cannot ping 
> 10.80.180.223 however
> 
> ens192Link encap:Ethernet  HWaddr 00:50:56:ab:e2:5b
>   inet6 addr: fe80::250:56ff:feab:e25b/64 Scope:Link
>   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>   RX packets:74 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:369 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:1000
>   RX bytes:4964 (4.9 KB)  TX bytes:35695 (35.6 KB)
> 
> ens224Link encap:Ethernet  HWaddr 00:50:56:ab:46:85
>   inet6 addr: fe80::250:56ff:feab:4685/64 Scope:Link
>   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>   RX packets:289 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:166 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:1000
>   RX bytes:26138 (26.1 KB)  TX bytes:15431 (15.4 KB)
> 
> kitbr0Link encap:Ethernet  HWaddr 00:50:56:ab:46:85
>   inet addr:10.80.180.223  Bcast:10.80.180.255  Mask:255.255.255.0
>   inet6 addr: fe80::250:56ff:feab:4685/64 Scope:Link
>   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>   RX packets:349 errors:0 dropped:37 overruns:0 frame:0
>   TX packets:96 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:1
>   RX bytes:25386 (25.3 KB)  TX bytes:10749 (10.7 KB)
> 
> 
> root@ovs:/etc/network# ovs-vsctl show
> 3a6b26a7-6e7a-44fd-8893-65f2c8fac4f2
> Bridge "kitbr0"
> Port "kitbr0"
> Interface "kitbr0"
> type: internal
> Port "ens192"
> Interface "ens192"
> Port "ens224"
> Interface "ens224"
> ovs_version: "2.5.2"
> 
> 
> Any clues about what is going are much appreciated. (I do not have a 
> controller at this time)


When running OVS in a VM on top of vSphere, you'll need to allow the NICs added 
to the OVS bridge to be in promiscuous mode. This is a setting on the vSwitch 
(IIRC it's called "Allow promiscuous mode"). Set that on the portgroup(s) where 
your interfaces are connected, and this should take care of it.

--
Scott



signature.asc
Description: Message signed with OpenPGP
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Re: [ovs-discuss] OVS configuration problem with Debian-Proxmox

2018-01-04 Thread Marc-Henri Pamiseux

Hello,

I am experiencing a very strange behavior of OVS with the previous
configuration.
In fact my interfaces manage to send an ICMP-> echo_request and receive
an ICMP-> echo_reply only six times every fifty packets.

Look, I start a ping from my computer just after restarting the server:
$ ping 192.168.72.125
PING 192.168.72.125 (192.168.72.125) 56(84) bytes of data.
From 192.168.72.104 icmp_seq=10 Destination Host Unreachable
From 192.168.72.104 icmp_seq=11 Destination Host Unreachable
From 192.168.72.104 icmp_seq=12 Destination Host Unreachable
64 bytes from 192.168.72.125: icmp_seq=13 ttl=64 time=2003 ms
64 bytes from 192.168.72.125: icmp_seq=14 ttl=64 time=1003 ms
64 bytes from 192.168.72.125: icmp_seq=15 ttl=64 time=3.35 ms
64 bytes from 192.168.72.125: icmp_seq=16 ttl=64 time=0.262 ms
64 bytes from 192.168.72.125: icmp_seq=17 ttl=64 time=0.232 ms
64 bytes from 192.168.72.125: icmp_seq=18 ttl=64 time=0.133 ms
64 bytes from 192.168.72.125: icmp_seq=19 ttl=64 time=0.263 ms
64 bytes from 192.168.72.125: icmp_seq=20 ttl=64 time=0.254 ms
-> Nothing beetween theses lines
64 bytes from 192.168.72.125: icmp_seq=78 ttl=64 time=0.720 ms
64 bytes from 192.168.72.125: icmp_seq=79 ttl=64 time=0.266 ms
64 bytes from 192.168.72.125: icmp_seq=80 ttl=64 time=0.247 ms
64 bytes from 192.168.72.125: icmp_seq=81 ttl=64 time=0.245 ms
64 bytes from 192.168.72.125: icmp_seq=82 ttl=64 time=0.248 ms
64 bytes from 192.168.72.125: icmp_seq=83 ttl=64 time=0.258 ms
-> Nothing beetween theses lines
64 bytes from 192.168.72.125: icmp_seq=141 ttl=64 time=0.686 ms
64 bytes from 192.168.72.125: icmp_seq=142 ttl=64 time=0.265 ms
64 bytes from 192.168.72.125: icmp_seq=143 ttl=64 time=0.196 ms
64 bytes from 192.168.72.125: icmp_seq=144 ttl=64 time=0.232 ms
64 bytes from 192.168.72.125: icmp_seq=145 ttl=64 time=0.235 ms
64 bytes from 192.168.72.125: icmp_seq=146 ttl=64 time=0.263 ms

strange is not it?
-- 
Marc-Henri Pamiseux - SARL Libricks - www.libricks.fr
6 rue Léonard de Vinci - CS 20119, 53001 LAVAL Cedex
Tel. : 02.30.96.15.24 / Mobile : 06.26.71.30.97
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Re: [ovs-discuss] Any timeline on PISCES in the mainline OVS?

Re: [ovs-discuss] OVS configuration problem with Debian-Proxmox

Re: [ovs-discuss] OVS configuration problem with Debian-Proxmox

Re: [ovs-discuss] interface can't be connected after attached to bridge

Re: [ovs-discuss] Bridge not working..

Re: [ovs-discuss] Bridge not working..

Re: [ovs-discuss] OVS configuration problem with Debian-Proxmox

7 matches

Site Navigation

Mail list logo

Footer information