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<http://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<http://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

[ovs-discuss] Bridge not working..

2018-01-03 Thread Steven Pollock 
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