On Mon, Apr 17, 2023 at 1:44 PM Alin Serdean <alinserd...@gmail.com> wrote:

> Hi,
>
> The issue you are facing might be because the name of the network adapters
> is the same.
>
> I wanted to emphasize the importance of the following step:
> https://docs.openvswitch.org/en/latest/intro/install/windows/#add-virtual-interfaces-vifs
>

I followed your advice! I am able to add both Ubuntus to the bridge.
However, the ping does. not work. (The details are attached to this email).
I think the issue is attaching the correct VM ports? Am I missing something?

Abu Rasheda

This is something particularly important for Windows and not the same under
> other OS.
>
> Alin.
>
> Sent from phone
>
> On 17 Apr 2023, at 20:33, Abu Rasheda via discuss <
> ovs-discuss@openvswitch.org> wrote:
>
> 
> Do you have any ideas, or if this is the wrong list, the recommendation
> for another one?
>
> On Thu, Apr 13, 2023 at 7:14 PM Abu Rasheda via discuss <
> ovs-discuss@openvswitch.org> wrote:
>
>> Hello!
>>
>> On Windows Server 2019, compiled, and loaded OVS kernel module.
>> Commands like ovs-vsctl & ovs-dpctl are running fine.
>>
>> I have two VMs (both running Ubuntu) under Hyper-V and have OVS
>> extended switch setup as described in
>> https://docs.openvswitch.org/en/latest/intro/install/windows/
>>
>> I can connect one Ubuntu VM to the OVS switch, under the "Network
>> Adaptor" setting for the virtual machine. When I try to ping an IP
>> address get prints from the OVS datapath in the kernel! This led me to
>> believe that OVS is installed and configured (I am from a Linux
>> background and Windows is new for me :)).
>>
>> However, when I try to add another Ubuntu VM to the OVS switch, I get
>> the following error:
>>
>> Synthetic Ethernet Port (Instance ID ..): Error '{Data Not Accepted}
>> The TDI client could not handle the data received during an
>> indication.'
>>
>> Failed to allocate resources while connecting to a virtual network.
>> The Ethernet switch may not exit.
>>
>> Can OVS Extended switch only connect to a single VM? (on the same host),
>>
>> I can connect these two machines to Windows virtual switch and ping
>> them. So either my setup has issues for OVS or there is a limitation
>> on OVS.
>> _______________________________________________
>> discuss mailing list
>> disc...@openvswitch.org
>> https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
>>
> _______________________________________________
> discuss mailing list
> disc...@openvswitch.org
> https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
>
>
======================================================================================================================
PS C:\OVS-Compiled> Get-NetAdapter

Name                      InterfaceDescription                    ifIndex 
Status       MacAddress             LinkSpeed
----                      --------------------                    ------- 
------       ----------             ---------
NIC1                      Broadcom NetXtreme Gigabit Ethernet #2       17 Up    
       18-66-DA-A2-62-6C         1 Gbps
br-int                    Hyper-V Virtual Ethernet Adapter #2          32 
Disabled     00-15-5D-72-76-09         1 Gbps
vEthernet (OVS Extende... Hyper-V Virtual Ethernet Adapter             30 Up    
       18-66-DA-A2-62-6C         1 Gbps
NIC2                      Broadcom NetXtreme Gigabit Ethernet          11 
Disconnected 18-66-DA-A2-62-6D          0 bps
br-pif                    Hyper-V Virtual Ethernet Adapter #3          34 
Disabled     00-15-5D-72-76-0A         1 Gbps

======================================================================================================================
PS C:\OVS-Compiled> ovs-vsctl.exe show
ca9219b1-ceca-435e-b42a-b3e094237045
    Bridge br-int
        Port ovs-port-a
            Interface ovs-port-a
        Port br-int
            Interface br-int
                type: internal
    Bridge br-pif
        Port NIC1
            Interface NIC1
        Port br-pif
            Interface br-pif
                type: internal

======================================================================================================================
PS C:\OVS-Compiled> ovs-dpctl.exe show
2023-04-20T00:21:40Z|00001|dpif_netlink|INFO|The kernel module does not support 
meters.
2023-04-20T00:21:40Z|00002|dpif_netlink|INFO|Kernel does not correctly support 
feature negotiation. Using standard features.
system@ovs-system:
  lookups: hit:54 missed:381697 lost:0
  flows: 1
  port 1: br-int (internal)
  port 2: br-pif (internal)
  port 3: NIC1
  port 4: ovs-port-a

======================================================================================================================
There are two VMs running under Hyper-V, both are 18.04, one of them is called 
left and the other one called right

OVS Extended Switch
 Broadcom NetXtreme Gigabit Ethernet #2
 ---> Open vSwitch Extension  - Forward
 ---> Microsoft NDIS Capture  - Monitoring
br-int
On left VM (running on Hyper-V) Network Adapter ---> OVS Extended Switch
On right VM (running on Hyper-V) Network Adapter ---> OVS Extended Switch

======================================================================================================================
PS C:\OVS-Compiled> ovs-ofctl dump-flows br-pif
 cookie=0x0, duration=98602.729s, table=0, n_packets=0, n_bytes=0, priority=0 
actions=NORMAL
PS C:\OVS-Compiled> ovs-ofctl dump-flows br-int
 cookie=0x0, duration=98622.988s, table=0, n_packets=1542, n_bytes=481050, 
priority=0 actions=NORMAL

======================================================================================================================
PS C:\OVS-Compiled> ovs-appctl bridge/dump-flows br-int
duration=128549s, n_packets=2017, n_bytes=634786, priority=0,actions=NORMAL
table_id=254, duration=128549s, n_packets=0, n_bytes=0, 
priority=2,recirc_id=0,actions=drop
table_id=254, duration=128549s, n_packets=0, n_bytes=0, 
priority=0,reg0=0x1,actions=controller(reason=)
table_id=254, duration=128549s, n_packets=0, n_bytes=0, 
priority=0,reg0=0x2,actions=drop
table_id=254, duration=128549s, n_packets=0, n_bytes=0, 
priority=0,reg0=0x3,actions=drop
PS C:\OVS-Compiled> ovs-appctl bridge/dump-flows br-pif

======================================================================================================================
duration=128557s, n_packets=0, n_bytes=0, priority=0,actions=NORMAL
table_id=254, duration=128557s, n_packets=0, n_bytes=0, 
priority=2,recirc_id=0,actions=drop
table_id=254, duration=128557s, n_packets=0, n_bytes=0, 
priority=0,reg0=0x1,actions=controller(reason=)
table_id=254, duration=128557s, n_packets=0, n_bytes=0, 
priority=0,reg0=0x2,actions=drop
table_id=254, duration=128557s, n_packets=0, n_bytes=0, 
priority=0,reg0=0x3,actions=drop

======================================================================================================================
PS C:\OVS-Compiled> ovs-ofctl.exe dump-ports br-int
OFPST_PORT reply (xid=0x2): 2 ports
  port LOCAL: rx pkts=?, bytes=?, drop=?, errs=?, frame=?, over=?, crc=?
           tx pkts=?, bytes=?, drop=?, errs=?, coll=?
  port  "ovs-port-a": rx pkts=?, bytes=?, drop=?, errs=?, frame=?, over=?, crc=?
           tx pkts=?, bytes=?, drop=?, errs=?, coll=?
======================================================================================================================

PS C:\OVS-Compiled> ovs-ofctl.exe dump-ports br-pif
OFPST_PORT reply (xid=0x2): 2 ports
  port LOCAL: rx pkts=?, bytes=?, drop=?, errs=?, frame=?, over=?, crc=?
           tx pkts=?, bytes=?, drop=?, errs=?, coll=?
  port  NIC1: rx pkts=?, bytes=?, drop=?, errs=?, frame=?, over=?, crc=?
           tx pkts=?, bytes=?, drop=?, errs=?, coll=?
_______________________________________________
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Reply via email to