Hi Alin, I don't see a big value from this patch if I understand it correctly.
Firstly, your commit is not clear about what it means when it says "typing it
later on". Are you referring to typing it later on in the documentation?
Secondly, since Hyper-V has different switch types such as
Commit d183efc22b2b ("This commit adds the windows installer to the
OVS tree.) added the .gitignore file to the distributed files but this
file shouldn't be part of the distributed archive.
Cc: Alin Gabriel Serdean
Signed-off-by: Markos Chandras
Hi, what’s the OvS version you tested. I didn’t get the crash with master
version.
The test script is described as below.
ovs-vsctl add-br br0
ovs-vsctl add-port br0 eth1
for i in `seq 0 1000`;
do
ovs-vsctl add-port br0 eth2
ovs-vsctl del-port br0 eth2
done
Thanks.
Nick
> On Feb 4,
Hello all
I 'm totally new in OVS. I want my open flow virtual switch to pars the
packets of a specific protocol to the application layer. I want to extract
some information of the packets. Is there any way in the OVS to do that?
any modules should be modified?!
Or may be I should use a dpi
Can we talk
___
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev
Use shorter name for the Hyper-V vSwitch for simplicity of typing it
later on.
Signed-off-by: Alin Gabriel Serdean
---
Documentation/intro/install/windows.rst | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git
Hard dependancy on default internal port (AllowManagementOS) has been
removed.
Software checksums are part of the windows datapath.
Disconnecting/Connecting the VIF is no longer required.
Unit tests are enabled and passing for some time now...
The option to create a MSI has been added.
At the beginning of the document we talk about the NIC 'Ethernet 1'
after 'Ethernet0', followed by 'Ethernet0 2'.
Although just names it seems better to have a single way of defining them:
'Ethernet(*)'
Signed-off-by: Alin Gabriel Serdean
---