subject:"\[ovs\-discuss\] about "

Re: [ovs-discuss] about metadata can persist value across some hops across OpenFlow switches

2024-09-02 Thread Eelco Chaudron via discuss


Hi,

I’m not an expert in this area, but I can see the metadata is 
explicitly cleared when traffic goes over a patch port.


https://github.com/openvswitch/ovs/blob/0051785f00c52cbbc2897989a454a5512e82dce0/ofproto/ofproto-dpif-xlate.c#L4131

If I go over the Git history, I can see this has always been the case 
since the introduction in commit 0a740f48293e.


It also explicitly mentions this:

/* If 'struct flow' gets additional metadata, we'll need to zero it 
out

 * before traversing a patch port. */

So I assume the documentation might be off, or the commit was wrong (and 
it’s a bug), or there is another reason. Maybe Ilya or others know, as 
this was done 12 years ago :)


Cheers,

Eelco


On 30 Aug 2024, at 4:27, 征途 via discuss wrote:

hello，In the ovs fields documentation, it says that metadata can 
retain values across the ovs bridge



https://man7.org/linux/man-pages/man7/ovs-fields.7.html#METADATA_FIELDS









But in my tests, it doesn't seem to retain the value, can you help us 
to answer the design in the first place?
Does metadata support retention of values across the ovs bridge or 
not？thanks.



___
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

Re: [ovs-discuss] about mac learning

2024-08-30 Thread Flavio Leitner via discuss

On Wed, 28 Aug 2024 07:33:42 +
"Wangyunjian\(wangyunjian, TongTu\) via discuss"
 wrote:

> Hi
> In our scenario, there are two hosts attached to the OVS. The active
> host1 and the standby host2 have same MAC. When switching from host1
> to host2, the flow of host1 in revalidator update the mac entry of
> the host2. I think this is not exactly. How do you think?


It looks like the test can race pings from the two sources and
the last one might run before the first, leaving the original one
in the fdb.

What happens if you ping one address and then ping the other manually?


 
> Another question: I think the upcall thread update the mac learning
> table is enough why the revalidator thread do this?

Because some changes may affect the flows in the datapath as well.

fbl

> 
> 
> Here are some logs:
> # ovs-appctl fdb/show br-2
> port  VLAN  MAC    Age
>     6 0  de:ca:44:38:17:41    4
>     2 0  de:ca:44:38:17:42    4   // The
> port no should be 6 6 0  de:ca:44:38:17:45    4
>     6 0  de:ca:44:38:17:43    4
>     6 0  de:ca:44:38:17:44    4
> # ovs-appctl fdb/show br-3
> port  VLAN  MAC    Age
>     6 0  de:ca:44:38:17:41    4   // The port no should
> be 1 2 0  de:ca:44:38:17:42    4
>     5 0  de:ca:44:38:17:45    4
>     3 0  de:ca:44:38:17:43    4
>     4 0  de:ca:44:38:17:44    4
> CI-EVS-9-31-3-95:/Images/linhf # ovs-dpctl dump-flows --names
> recirc_id(0),in_port(hnic2.5),eth(src=de:ca:44:38:17:45,dst=de:ca:44:38:17:55),eth_type(0x0800),ipv4(frag=no),
> packets:9, bytes:882, used:4.112s,
> actions:br-2,hnic2.1,hnic2.2,hnic2.3,hnic2.4,veth2.1
> 
> recirc_id(0),in_port(hnic2.1),eth(src=de:ca:44:38:17:41,dst=de:ca:44:38:17:51),eth_type(0x0800),ipv4(frag=no),
> packets:9, bytes:882, used:4.145s,
> actions:br-2,hnic2.2,hnic2.3,hnic2.4,hnic2.5,veth2.1
> recirc_id(0),in_port(veth3.1),eth(src=de:ca:44:38:17:41,dst=de:ca:44:38:17:51),eth_type(0x0800),ipv4(frag=no),
> packets:9, bytes:882, used:4.145s,
> actions:br-3,hnic3.1,hnic3.2,hnic3.3,hnic3.4,hnic3.5
> recirc_id(0),in_port(hnic3.1),eth(src=de:ca:44:38:17:41,dst=de:ca:44:38:17:61),eth_type(0x0800),ipv4(frag=no),
> packets:4, bytes:392, used:4.053s,
> actions:br-3,hnic3.2,hnic3.3,hnic3.4,hnic3.5,veth3.1
> recirc_id(0),in_port(veth2.1),eth(src=de:ca:44:38:17:41,dst=de:ca:44:38:17:61),eth_type(0x0800),ipv4(frag=no),
> packets:4, bytes:392, used:4.053s,
> actions:br-2,hnic2.1,hnic2.2,hnic2.3,hnic2.4,hnic2.5
> 
> recirc_id(0),in_port(hnic2.2),eth(src=de:ca:44:38:17:42,dst=de:ca:44:38:17:52),eth_type(0x0800),ipv4(frag=no),
> packets:9, bytes:882, used:4.145s,
> actions:br-2,hnic2.1,hnic2.3,hnic2.4,hnic2.5,veth2.1
> recirc_id(0),in_port(veth3.1),eth(src=de:ca:44:38:17:42,dst=de:ca:44:38:17:52),eth_type(0x0800),ipv4(frag=no),
> packets:9, bytes:882, used:4.145s,
> actions:br-3,hnic3.1,hnic3.2,hnic3.3,hnic3.4,hnic3.5
> recirc_id(0),in_port(hnic3.2),eth(src=de:ca:44:38:17:42,dst=de:ca:44:38:17:62),eth_type(0x0800),ipv4(frag=no),
> packets:4, bytes:392, used:4.049s,
> actions:br-3,hnic3.1,hnic3.3,hnic3.4,hnic3.5,veth3.1
> recirc_id(0),in_port(veth2.1),eth(src=de:ca:44:38:17:42,dst=de:ca:44:38:17:62),eth_type(0x0800),ipv4(frag=no),
> packets:4, bytes:392, used:4.049s,
> actions:br-2,hnic2.1,hnic2.2,hnic2.3,hnic2.4,hnic2.5
> 
> recirc_id(0),in_port(veth3.1),eth(src=de:ca:44:38:17:43,dst=de:ca:44:38:17:53),eth_type(0x0800),ipv4(frag=no),
> packets:9, bytes:882, used:4.145s,
> actions:br-3,hnic3.1,hnic3.2,hnic3.3,hnic3.4,hnic3.5
> recirc_id(0),in_port(hnic3.5),eth(src=de:ca:44:38:17:45,dst=de:ca:44:38:17:65),eth_type(0x0800),ipv4(frag=no),
> packets:4, bytes:392, used:4.017s,
> actions:br-3,hnic3.1,hnic3.2,hnic3.3,hnic3.4,veth3.1
> recirc_id(0),in_port(hnic2.4),eth(src=de:ca:44:38:17:44,dst=de:ca:44:38:17:54),eth_type(0x0800),ipv4(frag=no),
> packets:9, bytes:882, used:4.113s,
> actions:br-2,hnic2.1,hnic2.2,hnic2.3,hnic2.5,veth2.1
> recirc_id(0),in_port(hnic2.3),eth(src=de:ca:44:38:17:43,dst=de:ca:44:38:17:53),eth_type(0x0800),ipv4(frag=no),
> packets:9, bytes:882, used:4.145s,
> actions:br-2,hnic2.1,hnic2.2,hnic2.4,hnic2.5,veth2.1
> recirc_id(0),in_port(veth3.1),eth(src=de:ca:44:38:17:45,dst=de:ca:44:38:17:55),eth_type(0x0800),ipv4(frag=no),
> packets:9, bytes:882, used:4.113s,
> actions:br-3,hnic3.1,hnic3.2,hnic3.3,hnic3.4,hnic3.5
> recirc_id(0),in_port(veth2.1),eth(src=de:ca:44:38:17:45,dst=de:ca:44:38:17:65),eth_type(0x0800),ipv4(frag=no),
> packets:4, bytes:392, used:4.017s,
> actions:br-2,hnic2.1,hnic2.2,hnic2.3,hnic2.4,hnic2.5
> recirc_id(0),in_port(hnic3.3),eth(src=de:ca:44:38:17:43,dst=de:ca:44:38:17:63),eth_type(0x0800),ipv4(frag=no),
> packets:4, bytes:392, used:4.017s,
> actions:br-3,hnic3.1,hnic3.2,hnic3.4,hnic3.5,veth3.1
> recirc_id(0),in_port(veth3.1),eth(src=de:ca:44:38:17:44,dst=de:ca:44:38:17:54),eth_type(0x0800),ipv4(frag=no),
> packets:9, bytes:882, used:4.113s,
> actions:br-3,hnic3.1,hnic3.2,hnic3.3,hnic3.4,hnic3.5
> recirc_id(0),in_port(ve

[ovs-discuss] about mac learning

2024-08-28 Thread Wangyunjian(wangyunjian, TongTu) via discuss

Hi
In our scenario, there are two hosts attached to the OVS. The active host1 and 
the standby host2 have same MAC.
When switching from host1 to host2, the flow of host1 in revalidator update the 
mac entry of the host2. I think this is not exactly. How do you think?

Another question: I think the upcall thread update the mac learning table is 
enough why the revalidator thread do this?


Here are some logs:
# ovs-appctl fdb/show br-2
port  VLAN  MAC    Age
    6 0  de:ca:44:38:17:41    4
    2 0  de:ca:44:38:17:42    4   // The port no 
should be 6
    6 0  de:ca:44:38:17:45    4
    6 0  de:ca:44:38:17:43    4
    6 0  de:ca:44:38:17:44    4
# ovs-appctl fdb/show br-3
port  VLAN  MAC    Age
    6 0  de:ca:44:38:17:41    4   // The port no should be 1
    2 0  de:ca:44:38:17:42    4
    5 0  de:ca:44:38:17:45    4
    3 0  de:ca:44:38:17:43    4
    4 0  de:ca:44:38:17:44    4
CI-EVS-9-31-3-95:/Images/linhf # ovs-dpctl dump-flows --names
recirc_id(0),in_port(hnic2.5),eth(src=de:ca:44:38:17:45,dst=de:ca:44:38:17:55),eth_type(0x0800),ipv4(frag=no),
 packets:9, bytes:882, used:4.112s, 
actions:br-2,hnic2.1,hnic2.2,hnic2.3,hnic2.4,veth2.1

recirc_id(0),in_port(hnic2.1),eth(src=de:ca:44:38:17:41,dst=de:ca:44:38:17:51),eth_type(0x0800),ipv4(frag=no),
 packets:9, bytes:882, used:4.145s, 
actions:br-2,hnic2.2,hnic2.3,hnic2.4,hnic2.5,veth2.1
recirc_id(0),in_port(veth3.1),eth(src=de:ca:44:38:17:41,dst=de:ca:44:38:17:51),eth_type(0x0800),ipv4(frag=no),
 packets:9, bytes:882, used:4.145s, 
actions:br-3,hnic3.1,hnic3.2,hnic3.3,hnic3.4,hnic3.5
recirc_id(0),in_port(hnic3.1),eth(src=de:ca:44:38:17:41,dst=de:ca:44:38:17:61),eth_type(0x0800),ipv4(frag=no),
 packets:4, bytes:392, used:4.053s, 
actions:br-3,hnic3.2,hnic3.3,hnic3.4,hnic3.5,veth3.1
recirc_id(0),in_port(veth2.1),eth(src=de:ca:44:38:17:41,dst=de:ca:44:38:17:61),eth_type(0x0800),ipv4(frag=no),
 packets:4, bytes:392, used:4.053s, 
actions:br-2,hnic2.1,hnic2.2,hnic2.3,hnic2.4,hnic2.5

recirc_id(0),in_port(hnic2.2),eth(src=de:ca:44:38:17:42,dst=de:ca:44:38:17:52),eth_type(0x0800),ipv4(frag=no),
 packets:9, bytes:882, used:4.145s, 
actions:br-2,hnic2.1,hnic2.3,hnic2.4,hnic2.5,veth2.1
recirc_id(0),in_port(veth3.1),eth(src=de:ca:44:38:17:42,dst=de:ca:44:38:17:52),eth_type(0x0800),ipv4(frag=no),
 packets:9, bytes:882, used:4.145s, 
actions:br-3,hnic3.1,hnic3.2,hnic3.3,hnic3.4,hnic3.5
recirc_id(0),in_port(hnic3.2),eth(src=de:ca:44:38:17:42,dst=de:ca:44:38:17:62),eth_type(0x0800),ipv4(frag=no),
 packets:4, bytes:392, used:4.049s, 
actions:br-3,hnic3.1,hnic3.3,hnic3.4,hnic3.5,veth3.1
recirc_id(0),in_port(veth2.1),eth(src=de:ca:44:38:17:42,dst=de:ca:44:38:17:62),eth_type(0x0800),ipv4(frag=no),
 packets:4, bytes:392, used:4.049s, 
actions:br-2,hnic2.1,hnic2.2,hnic2.3,hnic2.4,hnic2.5

recirc_id(0),in_port(veth3.1),eth(src=de:ca:44:38:17:43,dst=de:ca:44:38:17:53),eth_type(0x0800),ipv4(frag=no),
 packets:9, bytes:882, used:4.145s, 
actions:br-3,hnic3.1,hnic3.2,hnic3.3,hnic3.4,hnic3.5
recirc_id(0),in_port(hnic3.5),eth(src=de:ca:44:38:17:45,dst=de:ca:44:38:17:65),eth_type(0x0800),ipv4(frag=no),
 packets:4, bytes:392, used:4.017s, 
actions:br-3,hnic3.1,hnic3.2,hnic3.3,hnic3.4,veth3.1
recirc_id(0),in_port(hnic2.4),eth(src=de:ca:44:38:17:44,dst=de:ca:44:38:17:54),eth_type(0x0800),ipv4(frag=no),
 packets:9, bytes:882, used:4.113s, 
actions:br-2,hnic2.1,hnic2.2,hnic2.3,hnic2.5,veth2.1
recirc_id(0),in_port(hnic2.3),eth(src=de:ca:44:38:17:43,dst=de:ca:44:38:17:53),eth_type(0x0800),ipv4(frag=no),
 packets:9, bytes:882, used:4.145s, 
actions:br-2,hnic2.1,hnic2.2,hnic2.4,hnic2.5,veth2.1
recirc_id(0),in_port(veth3.1),eth(src=de:ca:44:38:17:45,dst=de:ca:44:38:17:55),eth_type(0x0800),ipv4(frag=no),
 packets:9, bytes:882, used:4.113s, 
actions:br-3,hnic3.1,hnic3.2,hnic3.3,hnic3.4,hnic3.5
recirc_id(0),in_port(veth2.1),eth(src=de:ca:44:38:17:45,dst=de:ca:44:38:17:65),eth_type(0x0800),ipv4(frag=no),
 packets:4, bytes:392, used:4.017s, 
actions:br-2,hnic2.1,hnic2.2,hnic2.3,hnic2.4,hnic2.5
recirc_id(0),in_port(hnic3.3),eth(src=de:ca:44:38:17:43,dst=de:ca:44:38:17:63),eth_type(0x0800),ipv4(frag=no),
 packets:4, bytes:392, used:4.017s, 
actions:br-3,hnic3.1,hnic3.2,hnic3.4,hnic3.5,veth3.1
recirc_id(0),in_port(veth3.1),eth(src=de:ca:44:38:17:44,dst=de:ca:44:38:17:54),eth_type(0x0800),ipv4(frag=no),
 packets:9, bytes:882, used:4.113s, 
actions:br-3,hnic3.1,hnic3.2,hnic3.3,hnic3.4,hnic3.5
recirc_id(0),in_port(veth2.1),eth(src=de:ca:44:38:17:43,dst=de:ca:44:38:17:63),eth_type(0x0800),ipv4(frag=no),
 packets:4, bytes:392, used:4.017s, 
actions:br-2,hnic2.1,hnic2.2,hnic2.3,hnic2.4,hnic2.5
recirc_id(0),in_port(hnic3.4),eth(src=de:ca:44:38:17:44,dst=de:ca:44:38:17:64),eth_type(0x0800),ipv4(frag=no),
 packets:4, bytes:392, used:4.017s, 
actions:br-3,hnic3.1,hnic3.2,hnic3.3,hnic3.5,veth3.1
recirc_id(0),in_port(veth2.1),eth(src=de:ca:44:38:17:44,dst=de:ca:44:38:17:64),eth_type(0x0800),ipv4(frag=no),
 packets:

[ovs-discuss] about GRE

2023-01-10 Thread 信令





1.https://docs.openvswitch.org/en/latest/howto/tunneling/?highlight=gre#connecting-vms-using-tunnels




2.I follow the example above and implement it. But there was a problem：The dhcp 
response sent by the mobile phone cannot be received（Eth0 packet capture is 
responded by dhcp）


3.cmd:(Attachment is network card packet capture)
insmod /vport-gre.ko

ovs-vsctl add-br br-lan0_gre
ovs-vsctl add-port br-lan0_gre  gre1 -- set interface gre1 type=gre 
option:remote_ip=192.168.131.210 

ovs-vsctl del-port  br-lan0_zone0 ath1
ovs-vsctl add-port br-lan0_gre ath1

ovs-vsctl del-port  br-lan0_ex eth0
ovs-vsctl add-port br-lan0_gre eth0

#delete ens224 ip(no used)  
ip addr del 192.168.131.209/24 dev   br-lan0_ex

#ip link set br-lan0_gre up
ifconfig eth0 192.168.131.209

route add default gw 192.168.131.1








此致,
敬礼!
姓名 宋伟

信令部 软件工程师 
邮箱:ws...@grandstream.cn 
电话:0571-86849591-3618















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

[ovs-discuss] about GRE

2023-01-10 Thread 信令




1.https://docs.openvswitch.org/en/latest/howto/tunneling/?highlight=gre#connecting-vms-using-tunnels




2.I follow the example above and implement it. But there was a problem：The dhcp 
response sent by the mobile phone cannot be received（Eth0 packet capture is 
responded by dhcp）


3.cmd:(Attachment is network card packet capture)
insmod /vport-gre.ko

ovs-vsctl add-br br-lan0_gre
ovs-vsctl add-port br-lan0_gre  gre1 -- set interface gre1 type=gre 
option:remote_ip=192.168.131.210 

ovs-vsctl del-port  br-lan0_zone0 ath1
ovs-vsctl add-port br-lan0_gre ath1

ovs-vsctl del-port  br-lan0_ex eth0
ovs-vsctl add-port br-lan0_gre eth0

#delete ens224 ip(no used)  
ip addr del 192.168.131.209/24 dev   br-lan0_ex

#ip link set br-lan0_gre up
ifconfig eth0 192.168.131.209

route add default gw 192.168.131.1








此致,
敬礼!
姓名 宋伟

信令部 软件工程师 
邮箱:ws...@grandstream.cn 
电话:0571-86849591-3618













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

[ovs-discuss] About creating new QoS queues

2022-02-22 Thread Santiago Torres Borda

Good afternoon,

I’m trying to use tc to experiment with the multiple QDISC’s it offers. For 
that purpose I’m using mininet and by extension openvswitch. By default if I 
check the queues available, only one queue is shown for both tx and rx on the 
switch side for a given port. 

MININET> S1 LS /SYS/CLASS/NET/S1-ETH2/QUEUES/
RX-0  TX-0

By trying to follow the documentation, I have tried in numerous ways but the 
queues shown are always the same from the output above. The command I’m using 
at the moment is the following:

 SUDO OVS-VSCTL SET PORT S1-ETH3 QOS=@NEWQOS -- \
            --ID=@NEWQOS CREATE QOS TYPE=LINUX_HTB \
            
QUEUES=0=@NEW0,1=@NEW1,2=@NEW2,3=@NEW3,4=@NEW4,5=@NEW5,6=@NEW6,7=@NEW7 -- \
            --ID=@NEW0 CREATE QUEUE \
            --ID=@NEW1 CREATE QUEUE \
            --ID=@NEW2 CREATE QUEUE \
            --ID=@NEW3 CREATE QUEUE \
            --ID=@NEW4 CREATE QUEUE \
            --ID=@NEW5 CREATE QUEUE \
            --ID=@NEW6 CREATE QUEUE \
            --ID=@NEW7 CREATE QUEUE \

Where 8 queues is of importance to my use case. 

Does any one know why this happens, am I misinterpreting the documentation? 
Since I will be doing the shaping with tc I don’t need to use the rate limiting 
features shown in the documentation.

Thanks,
--
Santiago Torres Borda


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

[ovs-discuss] About the performance of ct nat

2020-09-11 Thread a*****

Hi, all


Why is conntrack always needed query here?


int ovs_ct_execute(struct net *net, struct sk_buff *skb,
   struct sw_flow_key *key,
   const struct ovs_conntrack_info *info)
{
．．


if (info->commit)
err = ovs_ct_commit(net, key, info, skb);
else
err = ovs_ct_lookup(net, key, info, skb);


．．
}




I compare the performance of ct nat and learn nat, the performance of ct nat is 
not very satisfactory！




After the nat connection is established, I try to manually add a rule to bypass 
the query conntrack, and then the performance will increase．




--

Any feedback is very much appreciated :)
Thanks,
Albert___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Re: [ovs-discuss] About VXLAN connecting container and physical machine

2020-09-06 Thread i_j_e_...@yahoo.co.jp

Hi.

Thanks for reply. I added some flow controls but the result is not effective. 
Here's the detail.

To see dump of vxlan packets on the ovs whose port has physical connection to 
34:95:db:28:4a:5e,
it was found that the arp reply arrived to the ovs.

[machine4]
2020-09-07 02:08:34.471064 Out 34:95:db:28:4a:5e ethertype ARP (0x0806）,
  length 44: Request who-has 172.20.0.21 tell 172.20.0.100, length 28

[machien1]
2020-09-07 02:08:34.471727 Out 70:85:c2:44:70:37 ethertype IPv4 (0x0800）,
  length 112: 192.168.1.2.34064 > 192.168.1.30.4789: VXLAN, flags [I] (0x08), 
vni 1025
  34:95:db:28:4a:5e > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806）,
  length 60: Request who-has 172.20.0.21 tell 172.20.0.100, length 46
2020-09-07 02:08:34.471749 Out 70:85:c2:44:70:37 ethertype IPv4 (0x0800）,
  length 112: 192.168.1.2.34064 > 192.168.64.1.4789: VXLAN, flags [I] (0x08), 
vni 1025
  34:95:db:28:4a:5e > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806）,
  length 60: Request who-has 172.20.0.21 tell 172.20.0.100, length 46
2020-09-07 02:08:34.477723  In 08:00:27:c2:5a:9f ethertype IPv4 (0x0800）,
  length 94: 192.168.1.30.50525 > 192.168.1.2.4789: VXLAN, flags [I] (0x08), 
vni 1025
  e6:c2:22:f9:1c:41 > 34:95:db:28:4a:5e, ethertype ARP (0x0806）,
  length 42: Reply 172.20.0.21 is-at e6:c2:22:f9:1c:41, length 28

Since it is necessary for the ovs to transfer arp reply to the destination, I 
added the following.

  # ovs-ofctl add-flow ovsbr0 
dl_type=0x0806,nw_proto=2,dl_dst=34:95:db:28:4a:5e,actions=output:15

However, the arp replies are not transferred to machine4.

  # ovs-ofctl dump-flows ovsbr0
  cookie=0x0, duration=172.977s, table=0, n_packets=0, n_bytes=0, 
arp,dl_dst=34:95:db:28:4a:5e,arp_op=2 actions=output:enp1s0f2
  cookie=0x0, duration=253.776s, table=0, n_packets=10, n_bytes=670, priority=0 
actions=NORMAL

Let me know what's wrong with the configuration. 

Regards,

> 2020/08/31 10:50、Heim, Dennis のメール:
> 
> When I have done VXLAN, I did it with a controller. Remember VXLAN defines 
> the data plane, but not the control plane (Mac address, etc).
> 
> -Original Message-
> From: discuss  On Behalf Of 
> i_j_e_...@yahoo.co.jp
> Sent: Sunday, August 30, 2020 1:17 PM
> To: ovs-discuss@openvswitch.org
> Subject: [ovs-discuss] About VXLAN connecting container and physical machine
> 
> Hi.
> 
> I tried to establish L2 network between a docker container and a physical 
> machine by using vxlan of OVS. The container host is different from the 
> physical machine. So far, it is not successful. I'd like to have comments on 
> how to do this.
> 
> Here's the detail.
> 
> As shown in the figure and description below, there are five physical 
> machines, machine1, machine2, machine3, machine4, and machine5. On all of 
> them are running linux. Each of machine1, machine2 and machine3 has a OVS 
> bridge.
> 
> Connection between docker2 and docker3 works fine. Connection between 
> machine4 and machine5 also works fine. When ovsbr1 is down, machine4 and 
> machine5 connection fails. Therefore, it is sure that ovsbr1 is forwarding 
> packets between machine4 and machine5.
> 
> However, connection between docker2 and machine4 is not established. Ping 
> never reaches between these. I dumped packets and found the following.
> 
> Docker2 ping to machine4 did not succeed, during which
>  a) arp requests arriveed on machine1 via the vxlan channel.
>  b) no arp request arrived on machine4.
> Docker2 ping to docker3 succeeded, during which
>  c) arp requests arrived on machine3 via the vxlan channel.
>  d) arp requests arrived on docker3 and docker3 replied.
> 
> To summerize, OVS does not forward arp request comming from vxlan to its 
> connected physical ports in this configuration.
> 
> Please let me know how to establish connection between docker2 and machine4 
> in this configuration.
> 
> Regards,
> 
>   +---+ +---+
>   |docker2| |docker3|
>   +--++ +--++
>  |eth2 |eth3
>  | |
> ovsbr2+--+--+ ovsbr3+--+--+
>  +-+ +-+   +-+
>  | machine1| |   machine2  |   |   machine3  |
>  +---+-+ +++   +++
> ovsbr1+-+--+ || |
> |  | || |
> enp1s0f0+  +enp1s0f1 |enp3s0enp0s3|   enp0s3|
> |   \++-+
> |\ physical switch
> | \

Re: [ovs-discuss] About VXLAN connecting container and physical machine

2020-08-30 Thread Heim, Dennis

When I have done VXLAN, I did it with a controller. Remember VXLAN defines the 
data plane, but not the control plane (Mac address, etc).

-Original Message-
From: discuss  On Behalf Of 
i_j_e_...@yahoo.co.jp
Sent: Sunday, August 30, 2020 1:17 PM
To: ovs-discuss@openvswitch.org
Subject: [ovs-discuss] About VXLAN connecting container and physical machine

Hi.

I tried to establish L2 network between a docker container and a physical 
machine by using vxlan of OVS. The container host is different from the 
physical machine. So far, it is not successful. I'd like to have comments on 
how to do this.

Here's the detail.

As shown in the figure and description below, there are five physical machines, 
machine1, machine2, machine3, machine4, and machine5. On all of them are 
running linux. Each of machine1, machine2 and machine3 has a OVS bridge.

Connection between docker2 and docker3 works fine. Connection between machine4 
and machine5 also works fine. When ovsbr1 is down, machine4 and machine5 
connection fails. Therefore, it is sure that ovsbr1 is forwarding packets 
between machine4 and machine5.

However, connection between docker2 and machine4 is not established. Ping never 
reaches between these. I dumped packets and found the following.

Docker2 ping to machine4 did not succeed, during which
  a) arp requests arriveed on machine1 via the vxlan channel.
  b) no arp request arrived on machine4.
Docker2 ping to docker3 succeeded, during which
  c) arp requests arrived on machine3 via the vxlan channel.
  d) arp requests arrived on docker3 and docker3 replied.

To summerize, OVS does not forward arp request comming from vxlan to its 
connected physical ports in this configuration.

Please let me know how to establish connection between docker2 and machine4 in 
this configuration.

Regards,

   +---+ +---+
   |docker2| |docker3|
   +--++ +--++
  |eth2 |eth3
  | |
 ovsbr2+--+--+ ovsbr3+--+--+
  +-+ +-+   +-+
  | machine1| |   machine2  |   |   machine3  |
  +---+-+ +++   +++
 ovsbr1+-+--+ || |
 |  | || |
 enp1s0f0+  +enp1s0f1 |enp3s0enp0s3|   enp0s3|
 |   \++-+
 |\ physical switch
 | \
 |eth4  \eth5
   +-++  +--+
   | machine4 |  | machine5 |
   +--+  +--+

Machine1:
  Three physical ports, enp1s0f0, enp1s0f1 and enp3s0.
  A ovs switch named ovsbr1.
  Enp1s0f[01] are logically connected to ovsbr1.
  Enp1s0f0 is physically connected to machine4.
  Enp1s0f1 is physically connected to machine5.
  Enp3s0 is physically connected to the physical switch.

Machine2:
  One physical port, enp0s3 which is connected to the physical switch.
  One ovs switch named ovsbr2.
  One docker container, named Docker0 on the machine, is connected to ovsbr2.

Machine3:
  One physical port, enp0s3 which is connected to the physical switch.
  One ovs switch named ovsbr3.
  One docker container, named Docker1 on the machine, is connected to ovsbr3.

Machine4, Machine5:
  Each has one physical port, whose names are eth4 and eth5 respectivly.
  Eth4 is physically connect to enp1s0f0.
  Eth5 is physically connect to enp1s0f1.

Ovsbr1 has a VXLAN port whose remote is ovsbr2.
Ovsbr2 has two VXLAN ports whose remote are ovsbr1 and ovsbr3.
Ovsbr3 has a VXLAN port whose remote is ovsbr2.

IPv4:
  machine1:enp3s0  192.168.1.1/24
  machine2:enp0s3  192.168.1.2/24
  machine3:enp0s3  192.168.1.3/24
  docker0:eth2 172.20.0.2/24
  docker1:eth3 172.20.0.3/24
  machine4:eth4172.20.0.4/24
  machine5:eth5172.20.0.5/24

machine1# ovs-vsctl show
Bridge ovsbr0
Port vxlan1025.2
Interface vxlan1025.2
type: vxlan
options: {key="1025", remote_ip="192.168.1.2"}
Port ovsbr0
Interface ovsbr1
type: internal
Port enp1s0f1
Interface enp1s0f1
Port enp1s0f0
Interface enp1s0f0
ovs_version: "2.13.1"

machine2# ovs-vsctl show
Bridge ovsbr0
Port ovsbr0
Interface ovsbr0
type: internal
Port vxlan1025.1
Interface vxlan1025.1
type: vxlan
options: {key="1025", remote_ip="192.168.1.1"}
Port vxlan1025.3
Interface vxlan1025.3
type: vxlan

[ovs-discuss] About VXLAN connecting container and physical machine

2020-08-30 Thread i_j_e_...@yahoo.co.jp

Hi.

I tried to establish L2 network between a docker container and a physical 
machine by using
vxlan of OVS. The container host is different from the physical machine. So 
far, it is
not successful. I'd like to have comments on how to do this.

Here's the detail.

As shown in the figure and description below, there are five physical machines, 
machine1, machine2,
machine3, machine4, and machine5. On all of them are running linux. Each of 
machine1, machine2
and machine3 has a OVS bridge.

Connection between docker2 and docker3 works fine. Connection between machine4 
and machine5
also works fine. When ovsbr1 is down, machine4 and machine5 connection fails. 
Therefore, it is sure
that ovsbr1 is forwarding packets between machine4 and machine5.

However, connection between docker2 and machine4 is not established. Ping never 
reaches between
these. I dumped packets and found the following.

Docker2 ping to machine4 did not succeed, during which
  a) arp requests arriveed on machine1 via the vxlan channel.
  b) no arp request arrived on machine4.
Docker2 ping to docker3 succeeded, during which
  c) arp requests arrived on machine3 via the vxlan channel.
  d) arp requests arrived on docker3 and docker3 replied.

To summerize, OVS does not forward arp request comming from vxlan to its 
connected physical ports
in this configuration.

Please let me know how to establish connection between docker2 and machine4 in 
this configuration.

Regards,

   +---+ +---+
   |docker2| |docker3|
   +--++ +--++
  |eth2 |eth3
  | |
 ovsbr2+--+--+ ovsbr3+--+--+
  +-+ +-+   +-+
  | machine1| |   machine2  |   |   machine3  |
  +---+-+ +++   +++
 ovsbr1+-+--+ || |
 |  | || |
 enp1s0f0+  +enp1s0f1 |enp3s0enp0s3|   enp0s3|
 |   \++-+
 |\ physical switch
 | \
 |eth4  \eth5
   +-++  +--+
   | machine4 |  | machine5 |
   +--+  +--+


Machine1:
  Three physical ports, enp1s0f0, enp1s0f1 and enp3s0.
  A ovs switch named ovsbr1.
  Enp1s0f[01] are logically connected to ovsbr1.
  Enp1s0f0 is physically connected to machine4.
  Enp1s0f1 is physically connected to machine5.
  Enp3s0 is physically connected to the physical switch.

Machine2:
  One physical port, enp0s3 which is connected to the physical switch.
  One ovs switch named ovsbr2.
  One docker container, named Docker0 on the machine, is connected to ovsbr2.

Machine3:
  One physical port, enp0s3 which is connected to the physical switch.
  One ovs switch named ovsbr3.
  One docker container, named Docker1 on the machine, is connected to ovsbr3.

Machine4, Machine5:
  Each has one physical port, whose names are eth4 and eth5 respectivly.
  Eth4 is physically connect to enp1s0f0.
  Eth5 is physically connect to enp1s0f1.
  
Ovsbr1 has a VXLAN port whose remote is ovsbr2.
Ovsbr2 has two VXLAN ports whose remote are ovsbr1 and ovsbr3.
Ovsbr3 has a VXLAN port whose remote is ovsbr2.

   
IPv4:
  machine1:enp3s0  192.168.1.1/24
  machine2:enp0s3  192.168.1.2/24
  machine3:enp0s3  192.168.1.3/24
  docker0:eth2 172.20.0.2/24
  docker1:eth3 172.20.0.3/24
  machine4:eth4172.20.0.4/24
  machine5:eth5172.20.0.5/24

machine1# ovs-vsctl show
Bridge ovsbr0
Port vxlan1025.2
Interface vxlan1025.2
type: vxlan
options: {key="1025", remote_ip="192.168.1.2"}
Port ovsbr0
Interface ovsbr1
type: internal
Port enp1s0f1
Interface enp1s0f1
Port enp1s0f0
Interface enp1s0f0
ovs_version: "2.13.1"

machine2# ovs-vsctl show
Bridge ovsbr0
Port ovsbr0
Interface ovsbr0
type: internal
Port vxlan1025.1
Interface vxlan1025.1
type: vxlan
options: {key="1025", remote_ip="192.168.1.1"}
Port vxlan1025.3
Interface vxlan1025.3
type: vxlan
options: {key="1025", remote_ip="192.168.1.3"}
Port ba1e1f0927484_l
Interface ba1e1f0927484_l
ovs_version: "2.13.0"

machine3# ovs-vsctl show
Bridge ovsbr0
Port a2cedfb6beb34_l
Interface a2cedfb6beb34_l
Port vxlan1025
Interface vxlan1025.2
type: vxlan
options: {key="1025", remote_ip="192.168.1.2"}
Port ovsbr0
In

[ovs-discuss] about OVS how to make with .so file

2020-08-08 Thread 18754634560

Hi.Recently,i wanna test some function that use code of golang in OVS. And i 
built the .so file and .h head file. I put them in ofproto and i include the 
head file, but i don't know where should i add .so arg when i try to use make 
install.  if i just run it, it will show that cannot find XXX like this 
sentence.  Is there any way i can use to fix it? Looking forward to reply.
I Appreciate it
Archer
August 8,2020

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

Re: [ovs-discuss] About the hash of the group

2019-12-16 Thread Ben Pfaff

On Mon, Dec 16, 2019 at 06:49:47PM +0800, 贾乘 wrote:
> I have one question about the hash of the group.  From the doc, 
> 
> 
> 
> The hash is symmetric. Is it the same key , when I used the src ip and
> src port , and used the dst ip and dst port if the src ip == dst ip,
> src port == dst port.  Thanks.

OVS makes hashes symmetric by using XOR to combine source and
destination fields.  I don't know whether this answers your question
(because I don't understand the question).
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Re: [ovs-discuss] About ovs_vport_init() error

2019-01-22 Thread Gregory Rose




On 1/22/2019 1:13 AM, Ken Ajiro wrote:
However I think that inet6_add_protocol() never return -EEXIST so I 
think that this special handling won't work.

   (It looks that inet6_add_protocol() returns only 0 or -1)

int inet6_add_protocol(const struct inet6_protocol *prot, unsigned char 
protocol)
{
 return !cmpxchg((const struct inet6_protocol 
**)&inet6_protos[protocol],
 NULL, prot) ? 0 : -1;
}

   Thanks,



You're correct.  I've sent a patch to the dev list to fix it.  It's here:

https://mail.openvswitch.org/pipermail/ovs-dev/2019-January/355500.html

Nice catch!!

- Greg

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

Re: [ovs-discuss] About ovs_vport_init() error

2019-01-22 Thread Ken Ajiro


 On Mon, 21 Jan 2019 19:17:58 +,
 gvrose8...@gmail.com wrote
 in E-mail "Re: [ovs-discuss] About ovs_vport_init() error":

> >datapath/vport.c ovs_vport_init()
> >
> > err = ip6gre_init();
> > if (err && err != -EEXIST) {
> > goto err_ip6gre;   <==
> > } else {
> > if (err == -EEXIST) {
> > pr_warn("IPv6 GRE/ERSPAN Rx mode is not supported\n");
> > goto skip_ip6_tunnel_init;
> > }
> > }
> >
> >datapath/linux/compat/ip6_gre.c rpl_ip6gre_init():
> >
> > err = inet6_add_protocol(&ip6gre_protocol, IPPROTO_GRE);
> > if (err < 0) {
> > pr_info("%s: can't add protocol\n", __func__);   <==
> > unregister_pernet_device(&ip6gre_net_ops);
> > goto ip6_gre_loaded;
> > }
> >
> >I checked net/ipv6/protocol.c and understand that when 
> > inet6_add_protocol() failed it returns -1 (same to -EPERM) instead of 
> > -EEXIT.
> >
> >Is it needed checking if err is -EEXIT at ovs_vport_init() ?
> 
> That's -EEXIST.

  Sorry, I spelled it wrong.

> It looks to me like  you have the gre and ip6_gre kernel
> modules already loaded.  Try unloading those first.

  Thank you for your advise. I'll try it.

> Yes, special  handling is required in that case.

  However I think that inet6_add_protocol() never return -EEXIST so I think 
that this special handling won't work.
  (It looks that inet6_add_protocol() returns only 0 or -1)

int inet6_add_protocol(const struct inet6_protocol *prot, unsigned char 
protocol)
{
return !cmpxchg((const struct inet6_protocol **)&inet6_protos[protocol],
NULL, prot) ? 0 : -1;
}

  Thanks,

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

Re: [ovs-discuss] About ovs_vport_init() error

2019-01-21 Thread Gregory Rose




On 1/16/2019 11:10 PM, Ken Ajiro wrote:

   Hello,

   On my kernel 4.9.0 box, I could not insmod openvswitch.ko (OVS 2.10.1) by 
following error:

openvswitch: LISP tunneling driver
GRE over IPv4 demultiplexor driver
can't add protocol
Cannot take GRE protocol rx entry- The GRE/ERSPAN rx feature not supported
openvswitch: GRE over IPv4 tunneling driver
openvswitch: rpl_ip6gre_init: can't add protocol
openvswitch: GRE TX only over IPv6 tunneling driver
insmod: ERROR: could not insert module /tmp/openvswitch.ko: Operation not 
permitted

   I think that this error caused by following logic:

   datapath/vport.c ovs_vport_init()

err = ip6gre_init();
if (err && err != -EEXIST) {
goto err_ip6gre;   <==
} else {
if (err == -EEXIST) {
pr_warn("IPv6 GRE/ERSPAN Rx mode is not supported\n");
goto skip_ip6_tunnel_init;
}
}

   datapath/linux/compat/ip6_gre.c rpl_ip6gre_init():

err = inet6_add_protocol(&ip6gre_protocol, IPPROTO_GRE);
if (err < 0) {
pr_info("%s: can't add protocol\n", __func__);   <==
unregister_pernet_device(&ip6gre_net_ops);
goto ip6_gre_loaded;
}

   I checked net/ipv6/protocol.c and understand that when inet6_add_protocol() 
failed it returns -1 (same to -EPERM) instead of -EEXIT.

   Is it needed checking if err is -EEXIT at ovs_vport_init() ?


That's -EEXIST.

Yes, special  handling is required in that case.  It looks to me like 
you have the gre and ip6_gre kernel

modules already loaded.  Try unloading those first.

- Greg

   
   Thanks,




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

[ovs-discuss] About ovs_vport_init() error

2019-01-16 Thread Ken Ajiro



  Hello,

  On my kernel 4.9.0 box, I could not insmod openvswitch.ko (OVS 2.10.1) by 
following error:

openvswitch: LISP tunneling driver
GRE over IPv4 demultiplexor driver
can't add protocol
Cannot take GRE protocol rx entry- The GRE/ERSPAN rx feature not supported
openvswitch: GRE over IPv4 tunneling driver
openvswitch: rpl_ip6gre_init: can't add protocol
openvswitch: GRE TX only over IPv6 tunneling driver
insmod: ERROR: could not insert module /tmp/openvswitch.ko: Operation not 
permitted

  I think that this error caused by following logic:

  datapath/vport.c ovs_vport_init()

err = ip6gre_init();
if (err && err != -EEXIST) {
goto err_ip6gre;   <==
} else {
if (err == -EEXIST) {
pr_warn("IPv6 GRE/ERSPAN Rx mode is not supported\n");
goto skip_ip6_tunnel_init;
}
}

  datapath/linux/compat/ip6_gre.c rpl_ip6gre_init():

err = inet6_add_protocol(&ip6gre_protocol, IPPROTO_GRE);
if (err < 0) {
pr_info("%s: can't add protocol\n", __func__);   <==
unregister_pernet_device(&ip6gre_net_ops);
goto ip6_gre_loaded;
}

  I checked net/ipv6/protocol.c and understand that when inet6_add_protocol() 
failed it returns -1 (same to -EPERM) instead of -EEXIT.

  Is it needed checking if err is -EEXIT at ovs_vport_init() ?
  
  Thanks,

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

[ovs-discuss] About getting processing delay

2018-04-05 Thread MA Moyeen

Hi
I'm interested to measure the delays associated with flow table matching. how 
can I get time of entrance and exit of a packet in OVS? Given that packets are 
not control message so no packet in will occur to the Ryu Controller.
I'm using mininet, openflow 1.3, OVS and Ryu Controller.
Thanking you for your kind help in advance.

With Best Regards
M A MOYEEN
MCS student at Dalhousie University

Get Outlook for Android

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

Re: [ovs-discuss] About ovs2.8.1 & meter & iperf

2018-02-03 Thread Guoshuai Li


Hello,

ovs 2.8 only support meter in netdev bridge, "netlink" does not support.

there are currently some patches, you can follow：
https://mail.openvswitch.org/pipermail/ovs-dev/2018-January/343960.html


Thanks, Guoshuai.

Hi，
excuse me,when I used the ovs2.8.1 and implemented  “/ovs-ofctl -O 
OpenFlow13 add-meter s2 meter=1,kbps,band=type=drop,rate=1/” the 
CLI output “OFPMMFC_INVALID_METER”. If I typed "/ovs-vsctl set bridge 
s2 datapath_type=netdev/" before, it was succeed.

But if ovs was ”netdev“, the iperf test was failture.

/ryu-manager simple_switch_13.py/
/mn --topo linear,3 --mac --switch ovs,protocols=OpenFlow13 
--controller remote/



The result is as follows：
The server did not show the result.
So I really want to know "netdev" model and the meter has what kind of 
relationship？

What to do to use meter in ovs2.8.1 and test success？

I hope you can answer it.
Thank you very much!




___
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

[ovs-discuss] About ovs2.8.1 & meter & iperf

2018-02-02 Thread man

Hi，
excuse me,when I used the ovs2.8.1 and implemented  “ovs-ofctl -O OpenFlow13 
add-meter s2 meter=1,kbps,band=type=drop,rate=1” the CLI output 
“OFPMMFC_INVALID_METER”.  If I typed "ovs-vsctl set bridge s2 
datapath_type=netdev" before, it was succeed.  
But if ovs was ”netdev“, the iperf test was failture.


ryu-manager simple_switch_13.py
mn --topo linear,3 --mac --switch ovs,protocols=OpenFlow13 --controller remote




The result is as follows：
The server did not show the result.
So I really want to know "netdev" model and the meter has what kind of 
relationship？
What to do to use meter in ovs2.8.1 and test success？


I hope you can answer it.

Thank you very much!___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

[ovs-discuss] About libvirt use openvswitch question

2017-12-25 Thread wingo

Hello:
When I start libvirt vm with openvwitch as 
http://openvswitch.org/support/dist-docs-2.5/INSTALL.Libvirt.md.html


But When I destroy the VM, the ovs port has been not delete. see:


Bridge br_in
Port br-tap-in
Interface br-tap-in
Port "vnet22"
Interface "vnet22"
Port "vnet14"
Interface "vnet14"
Port "vnet12"
Interface "vnet12"___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Re: [ovs-discuss] About the 'clone' action

2017-10-25 Thread Ben Pfaff

On Wed, Oct 25, 2017 at 06:07:41PM +0800, Hui Xiang wrote:
> I think I am finally catching a bit with the concept of 'clone' action
> after reviewing below patches in order, so the for OVN case, the new
> 'clone' action aims to drop most of the OVS patch port, and after add new
> ct_clear action, some fixes, I assume it works with NAT, and I am using
> 2.8.1 for testing, please point out the patches if I am missing any. 

I think that should work fine.  There are a few bug fixes on branch-2.8
that are not in any v2.8.x release, but I don't think that they will
affect OVN.

> One other question is Can I set bridge-mapping:physnet1:br-int? In
> other words, the br-int has vm vif, has tunnel ports(the tunnel ports
> would point to another nic), and has the external nic as local gateway
> router port, is it feasible without configuring more extra flows.

I don't think OVN contemplates br-int being using as a bridge mapping.
My guess is that that would fail.
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Re: [ovs-discuss] About the 'clone' action

2017-10-25 Thread Hui Xiang

Thanks Ben for your info.

I think I am finally catching a bit with the concept of 'clone' action
after reviewing below patches in order, so the for OVN case, the new
'clone' action aims to drop most of the OVS patch port, and after add new
ct_clear action, some fixes, I assume it works with NAT, and I am using
2.8.1 for testing, please point out the patches if I am missing any. One
other question is Can I set bridge-mapping:physnet1:br-int? In other words,
the br-int has vm vif, has tunnel ports(the tunnel ports would point to
another nic), and has the external nic as local gateway router port, is it
feasible without configuring more extra flows.

[ovs-dev] [RFC PATCH] ofp-actions: Add clone action.
https://mail.openvswitch.org/pipermail/ovs-dev/2016-November/325542.html

ovn-controller: Drop most uses of OVS patch ports.
https://github.com/openvswitch/ovs/commit/f1a8bd06d58f2c5312622fbaeacbc6ce7576e347https://github.com/openvswitch/ovs/commit/f1a8bd06d58f2c5312622fbaeacbc6ce7576e347

[ovs-dev] [PATCH 2/3] dpif-netdev: Add clone action
https://mail.openvswitch.org/pipermail/ovs-dev/2017-January/327633.html

[ovs-dev] Issues with the use of the clone action for resubmission to the
pipeline
https://mail.openvswitch.org/pipermail/ovs-dev/2017-January/326981.html

[ovs-dev] ovn ping from VM to external gateway IP failed.
https://mail.openvswitch.org/pipermail/ovs-dev/2016-December/326936.html

[ovs-dev] [PATCH v2 0/4] Fix some "clone"-related issues
https://mail.openvswitch.org/pipermail/ovs-dev/2017-January/327251.html

[ovs-dev] [PATCH v2 3/4] New action "ct_clear".
https://mail.openvswitch.org/pipermail/ovs-dev/2017-January/327268.html

[ovs-dev] [PATCH v2 4/4] ovn-controller: Clear conntrack state inside clone
action.
https://mail.openvswitch.org/pipermail/ovs-dev/2017-January/327255.html

On Tue, Oct 24, 2017 at 12:21 AM, Ben Pfaff  wrote:

> On Mon, Oct 23, 2017 at 04:28:53PM +0800, Hui Xiang wrote:
> > I am trying to understand clone action deeply and checking the patch
> > related with 'clone'[1], where said "The clone action provides an action
> > envelope to enclose an action list." and "The clone action is very
> similar
> > with the OpenFlow clone action recently added", but sorry I am not able
> to
> > find any "clone" action definition in the OpenFlow spec[2], or any
> envelope
> > 's kind of phrases, it just referred some clone(copy) of piple, am I
> > looking in a wrong place?
>
> Open vSwitch has two kinds of actions.  First, there are OpenFlow
> actions, which include both standard actions and extension actions.
> "clone" is an OpenFlow extension action implemented by Open vSwitch.
> Second, there are datapath actions, which are an implementation detail
> of Open vSwitch.  Open vSwitch has a datapath action also called
> "clone", which does something similar to the OpenFlow extension "clone"
> action but at the datapath level.
>
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Re: [ovs-discuss] About the 'clone' action

2017-10-23 Thread Ben Pfaff

On Mon, Oct 23, 2017 at 04:28:53PM +0800, Hui Xiang wrote:
> I am trying to understand clone action deeply and checking the patch
> related with 'clone'[1], where said "The clone action provides an action
> envelope to enclose an action list." and "The clone action is very similar
> with the OpenFlow clone action recently added", but sorry I am not able to
> find any "clone" action definition in the OpenFlow spec[2], or any envelope
> 's kind of phrases, it just referred some clone(copy) of piple, am I
> looking in a wrong place?

Open vSwitch has two kinds of actions.  First, there are OpenFlow
actions, which include both standard actions and extension actions.
"clone" is an OpenFlow extension action implemented by Open vSwitch.
Second, there are datapath actions, which are an implementation detail
of Open vSwitch.  Open vSwitch has a datapath action also called
"clone", which does something similar to the OpenFlow extension "clone"
action but at the datapath level.
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

[ovs-discuss] About the 'clone' action

2017-10-23 Thread Hui Xiang

Hi folks,


I am trying to understand clone action deeply and checking the patch
related with 'clone'[1], where said "The clone action provides an action
envelope to enclose an action list." and "The clone action is very similar
with the OpenFlow clone action recently added", but sorry I am not able to
find any "clone" action definition in the OpenFlow spec[2], or any envelope
's kind of phrases, it just referred some clone(copy) of piple, am I
looking in a wrong place?

Thx much.

[1] https://mail.openvswitch.org/pipermail/ovs-dev/2017-January/327633.html
[2]
https://www.opennetworking.org/wp-content/uploads/2014/10/openflow-switch-v1.5.1.pdf
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Re: [ovs-discuss] About side effect of port mirroring

2017-10-04 Thread Ben Pfaff

On Wed, Oct 04, 2017 at 06:54:39PM +0900, Kurokawa Ryota wrote:
> Hi
> 
> I will use port mirroring.
> I learned how to use port mirroring by looking at the manual. 
> 
> I have one question.
> 
> 「As a side effect, port mirroring causes any packets received on output port 
> to be ignored.」
> 
> What does this mean?
> Does that mean that any packets received on output port will be dropped when 
> they arrive at the switch?

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

[ovs-discuss] About side effect of port mirroring

2017-10-04 Thread Kurokawa Ryota

Hi

I will use port mirroring.
I learned how to use port mirroring by looking at the manual. 

I have one question.

「As a side effect, port mirroring causes any packets received on output port to 
be ignored.」

What does this mean?
Does that mean that any packets received on output port will be dropped when 
they arrive at the switch?

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

Re: [ovs-discuss] About ovs-docker

2017-07-24 Thread Guru Shetty

It looks like you already figured it out.

On 19 July 2017 at 07:28, Zekeriya Akgül  wrote:

> Hi,
> I am student on Necmettin Erbakan Universty in Turkey.And working on
> communication between dpdk powered openvswitch and docker.And some issues
> occured about communication between docker and other hosts.
>
> I explained my problem in this post:
> https://superuser.com/questions/1231090/connected-with-open-
> v-switch-connection-issue-between-docker-container-and-othe
>
> Please response this post or response me by e-mail.
>
> Thank you!
> 
> Zekeriya AKGÜL
>
> ___
> 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

[ovs-discuss] About ovs-docker

2017-07-23 Thread Zekeriya Akgül

Hi,
I am student on Necmettin Erbakan Universty in Turkey.And working on
communication between dpdk powered openvswitch and docker.And some issues
occured about communication between docker and other hosts.

I explained my problem in this post:
https://superuser.com/questions/1231090/connected-with-open-
v-switch-connection-issue-between-docker-container-and-othe

Please response this post or response me by e-mail.

Thank you!

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

Re: [ovs-discuss] about L3 Route problem with two host

2017-07-16 Thread feihu929

I found the reason why the vm1 can not ping vm4.
It's may be I use vxlan to build the tun,  when replace geneve,  the vm1 can 
ping vm4

when use vxlan, run as below command in network1/2/3 host , 
[root@xxx ~]# ovs-vsctl set Open_vSwitch . external-ids:ovn-encap-type=vxlan 
the vm CAN NOT ping each other which not in the same logical switch and not in 
the same host node.

when use geneve, run as below command in network1/2/3 host , 
[root@xxx ~]# ovs-vsctl set Open_vSwitch . external-ids:ovn-encap-type=geneve
the vm CAN ping each other which not in the same logical switch and not in the 
same host node.

May be is a bug with vxlan?
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

[ovs-discuss] about L3 Route problem with two host

2017-07-14 Thread feihu929

I build a L3 Route Test with Three Host(network1/ovn-central, 
network2/ovn-host, network3/ovn-host), each ovn-host node run 2 vm and 
conntected by 2 logical switch, the two logical switch connected by 1 logical 
router, as below

 network1
  ---
  | ovn-central |
  ---
/ \
   /   \
  / \
 /   \
/ \
   /   \
  / \
  --- --- 
  |     | lswtich 1   |     |
  |  | vm1  |---|-|  | vm1  |---|
  |     | |   |     |
  | | |   | |
  | | |   | |
  | |-| |
  |   ovn-host  || lrouter 1 ||  ovn-host   |
  | |-| |
  | | |   | |
  | | |   | |
  |     | lswtich 2   |     |
  |  | vm1  |---|-|  | vm1  |---|
  |     | |     |
  | | | |
  --- ---
  network2   network3




When testing, I encount a problem as below.
1. the vm1 can ping vm2 which in the same logical switch not in the same host 
node.
2. the vm1 can ping vm3 which not in the same logical switch and in the same 
host node.
3. the vm1 CAN NOT ping vm4 which not in the same logical switch and not in the 
same host node.

the host (network1/2/3) is centos7 with openvswitch/ovn 2.6.1

the build command as below
---
# Create the first logical switch and its two ports.
ovn-nbctl ls-add sw0

ovn-nbctl lsp-add sw0 sw0-port1
ovn-nbctl lsp-set-addresses sw0-port1 "00:00:00:00:00:01 10.0.0.51"
ovn-nbctl lsp-set-port-security sw0-port1 "00:00:00:00:00:01 10.0.0.51"

ovn-nbctl lsp-add sw0 sw0-port2
ovn-nbctl lsp-set-addresses sw0-port2 "00:00:00:00:00:02 10.0.0.52"
ovn-nbctl lsp-set-port-security sw0-port2 "00:00:00:00:00:02 10.0.0.52"

# Create the second logical switch and its two ports.
ovn-nbctl ls-add sw1

ovn-nbctl lsp-add sw1 sw1-port1
ovn-nbctl lsp-set-addresses sw1-port1 "00:00:00:00:00:03 192.168.1.51"
ovn-nbctl lsp-set-port-security sw1-port1 "00:00:00:00:00:03 192.168.1.51"

ovn-nbctl lsp-add sw1 sw1-port2
ovn-nbctl lsp-set-addresses sw1-port2 "00:00:00:00:00:04 192.168.1.52"
ovn-nbctl lsp-set-port-security sw1-port2 "00:00:00:00:00:04 192.168.1.52"

# Create a logical router between sw0 and sw1.
ovn-nbctl create Logical_Router name=lr0

ovn-nbctl lrp-add lr0 lrp0 00:00:00:00:ff:01 10.0.0.1/24
ovn-nbctl lsp-add sw0 sw0-lrp0 \
-- set Logical_Switch_Port sw0-lrp0 type=router \
options:router-port=lrp0 addresses='"00:00:00:00:ff:01"'

ovn-nbctl lrp-add lr0 lrp1 00:00:00:00:ff:02 192.168.1.1/24
ovn-nbctl lsp-add sw1 sw1-lrp1 \
-- set Logical_Switch_Port sw1-lrp1 type=router \
options:router-port=lrp1 addresses='"00:00:00:00:ff:02"'


$ ovn-nbctl show
switch bf4ba6c6-91c5-4f56-9981-72643816f923 (sw1)
port sw1-lrp1
addresses: ["00:00:00:00:ff:02"]
port sw1-port2
addresses: ["00:00:00:00:00:04 192.168.1.52"]
port sw1-port1
addresses: ["00:00:00:00:00:03 192.168.1.51"]
switch 13b80127-4b36-46ea-816a-1ba4ffd6ac57 (sw0)
port sw0-port1
addresses: ["00:00:00:00:00:01 10.0.0.51"]
port sw0-lrp0
addresses: ["00:00:00:00:ff:01"]
port sw0-port2
addresses: ["00:00:00:00:00:02 10.0.0.52"]
router 68935017-967a-4c4a-9dad-5d325a9f203a (lr0)
port lrp0
mac: "00:00:00:00:ff:01"
networks: ["10.0.0.1/24"]
port lrp1
mac: "00:00:00:00:ff:02"
networks: ["192.168.1.1/24"]

# on network2 host
ip netns add vm1
ovs-vsctl add-port br-int vm1 -- set interface vm1 type=internal
ip link set vm1 netns vm1
ovs-vsctl set Interface vm1 external_ids:iface-id=sw0-port1
ip netns exec vm1 ip link set vm1 address 00:00:00:00:00:01
ip netns exec vm1 ip addr add 10.0.0.51/24 dev vm1
ip netns exec vm1 ip link set vm1 up
ip netns exec vm1 ip route add default via 10.0.0.1 dev vm1

ip netns add vm3
ovs-vsctl add-port br-int vm3 -- set interface vm3 type=internal
ip link set vm3 netns vm3
ovs-vsctl set Interface vm3 external_ids:iface-id=sw1-port1
ip netns exec vm3 ip link set vm3 address 00:00:00:00:00:03
ip netns exec vm3 ip addr add 192.168.1.51/24 dev vm3
ip netns exec vm3 ip link set vm3 up
ip netns exec vm3 ip route add default via 192.168.1.1 dev vm3


# on network3 host
ip netns add vm2
ovs-vsctl add-port br-int vm2 --

Re: [ovs-discuss] about

2017-04-19 Thread Justin Pettit


> On Apr 18, 2017, at 6:59 PM, qintao (F)  wrote:
> 
>  
>  
> Dear all ,
>  we create a bridge “br1” with the type of netdev .And the version of the 
> ovs is 2.5.0. Then we run the command “ovs-vsctl set int br1 lldp:enable=true 
> “ to make the interface br1 enable the function lldp.After that ,we delete 
> the bridge br1 ,we found the the process “ovs-vswitchd” has been lost.
> ”

Thanks for the report.  There are a couple of releases in the 2.5.x series 
since 2.5.0.  Are you able to reproduce the same issue with 2.5.2?

--Justin


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

[ovs-discuss] about

2017-04-18 Thread qintao (F)



Dear all ,

 we create a bridge "br1" with the type of netdev .And the version of the 
ovs is 2.5.0. Then we run the command "ovs-vsctl set int br1 lldp:enable=true " 
to make the interface br1 enable the function lldp.After that ,we delete the 
bridge br1 ,we found the the process "ovs-vswitchd" has been lost.
"

[cid:image001.png@01D2B8F3.98B68D70]
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Re: [ovs-discuss] About NSH support

2017-01-26 Thread Yang, Yi Y

https://github.com/yyang13/ovs_nsh_patches/tree/master/v2.6.1 has NSH patches 
for ovs 2.6.1, you can use it.

From: ovs-discuss-boun...@openvswitch.org 
[mailto:ovs-discuss-boun...@openvswitch.org] On Behalf Of sam su
Sent: Thursday, January 26, 2017 2:30 AM
To: ovs-discuss@openvswitch.org
Subject: [ovs-discuss] About NSH support

Hi,
I am going to try Openvswitch NSH function based on Ubuntu 16.04, how can I 
confirm the installed Openvswitch(2.6.1) support NSH? If NSH is not supported 
officially, is there any unofficial Openvswitch version support NSH?
Thanks,
Sam
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Re: [ovs-discuss] About NSH support

2017-01-25 Thread sam su

Hi Danny,

Nice, many thanks for you guys.

I don't really care about whether the OVS version is the latest or not,
since I just want to try NSH function, the OVS 2.6.1 should be good for me.
Anyway, I will try it first.

Thanks,
Sam



On Wed, Jan 25, 2017 at 5:30 PM, Zhou, Danny  wrote:

> OPNFV packages the forked OVS at https://github.com/yyang13/
> ovs_nsh_patches, but an
>
> old version.If you plan to use OVS 2.6.1, the forked OVS at above github
> has been upgraded
>
> to OVS 2.6.1, and it works with ODL and ONSO controller.
>
>
>
> Yi Yang in CC is the maintainer of that forked OVS repository and he is
> also working closely with
>
> other community folks on upstreaming NSH patch to OVS covering control
> plane, in-kernel data plane
>
> and DPDK_netdev data plane, but the eventually upstreamed code might be
> different from the one
>
> in this github repository.
>
>
>
> *From:* ovs-discuss-boun...@openvswitch.org [mailto:ovs-discuss-bounces@
> openvswitch.org] *On Behalf Of *sam su
> *Sent:* Thursday, January 26, 2017 8:42 AM
> *To:* Shu Shen 
> *Cc:* ovs-discuss@openvswitch.org
> *Subject:* Re: [ovs-discuss] About NSH support
>
>
>
> Hi Shu,
>
> Thank you so much for the info.
>
> I will take a look the docs first.
>
> Thanks,
>
> Sam
>
>
>
> On Wed, Jan 25, 2017 at 11:58 AM, Shu Shen  wrote:
>
> Hi Sam,
>
> OpenNFV maintains a version of OVS with NSH support, which is not
> supported by upstream OVS.
>
> Please refer to OpenNFV document:
>
> http://artifacts.opnfv.org/sfc/colorado/3.0/docs/
> scenarios_os-odl_l2-sfc-noha/index.html#specific-version-of-ovs
>
>
>
> /Shu
>
>
>
>
>
> On Wed, Jan 25, 2017 at 11:14 AM, sam su  wrote:
>
> Thank you, Ben.
>
> Let me explain a little bit why I'm going to try NSH based on Openvswitch.
> Because I saw a slides "SFC with NSH and OVS"( here is the link
> http://openvswitch.org/support/ovscon2015/16/1040-elzur.pdf ), it looks
> like the guy used openvswitch as a NSH classifier and a NSH forwarder
> already.
>
>
>
> Thanks,
>
> Sam
>
>
>
> On Wed, Jan 25, 2017 at 10:42 AM, Ben Pfaff  wrote:
>
> On Wed, Jan 25, 2017 at 10:29:42AM -0800, sam su wrote:
> > I am going to try Openvswitch NSH function based on Ubuntu 16.04, how
> can I
> > confirm the installed Openvswitch(2.6.1) support NSH? If NSH is not
> > supported officially, is there any unofficial Openvswitch version support
> > NSH?
>
> Open vSwitch does not support NSH.
>
> I don't know about unofficial versions.  Perhaps someone will speak up.
>
>
>
>
>
> ___
> 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

Re: [ovs-discuss] About NSH support

2017-01-25 Thread Zhou, Danny

OPNFV packages the forked OVS at https://github.com/yyang13/ovs_nsh_patches, 
but an
old version.If you plan to use OVS 2.6.1, the forked OVS at above github has 
been upgraded
to OVS 2.6.1, and it works with ODL and ONSO controller.

Yi Yang in CC is the maintainer of that forked OVS repository and he is also 
working closely with
other community folks on upstreaming NSH patch to OVS covering control plane, 
in-kernel data plane
and DPDK_netdev data plane, but the eventually upstreamed code might be 
different from the one
in this github repository.

From: ovs-discuss-boun...@openvswitch.org 
[mailto:ovs-discuss-boun...@openvswitch.org] On Behalf Of sam su
Sent: Thursday, January 26, 2017 8:42 AM
To: Shu Shen 
Cc: ovs-discuss@openvswitch.org
Subject: Re: [ovs-discuss] About NSH support

Hi Shu,
Thank you so much for the info.
I will take a look the docs first.
Thanks,
Sam

On Wed, Jan 25, 2017 at 11:58 AM, Shu Shen 
mailto:shu.s...@gmail.com>> wrote:
Hi Sam,

OpenNFV maintains a version of OVS with NSH support, which is not supported by 
upstream OVS.
Please refer to OpenNFV document:
http://artifacts.opnfv.org/sfc/colorado/3.0/docs/scenarios_os-odl_l2-sfc-noha/index.html#specific-version-of-ovs

/Shu

On Wed, Jan 25, 2017 at 11:14 AM, sam su 
mailto:ssu@gmail.com>> wrote:
Thank you, Ben.
Let me explain a little bit why I'm going to try NSH based on Openvswitch.
Because I saw a slides "SFC with NSH and OVS"( here is the link 
http://openvswitch.org/support/ovscon2015/16/1040-elzur.pdf ), it looks like 
the guy used openvswitch as a NSH classifier and a NSH forwarder already.

Thanks,
Sam

On Wed, Jan 25, 2017 at 10:42 AM, Ben Pfaff mailto:b...@ovn.org>> 
wrote:
On Wed, Jan 25, 2017 at 10:29:42AM -0800, sam su wrote:
> I am going to try Openvswitch NSH function based on Ubuntu 16.04, how can I
> confirm the installed Openvswitch(2.6.1) support NSH? If NSH is not
> supported officially, is there any unofficial Openvswitch version support
> NSH?

Open vSwitch does not support NSH.

I don't know about unofficial versions.  Perhaps someone will speak up.

___
discuss mailing list
disc...@openvswitch.org<mailto: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

Re: [ovs-discuss] About NSH support

2017-01-25 Thread sam su

Hi Shu,

Thank you so much for the info.
I will take a look the docs first.

Thanks,
Sam

On Wed, Jan 25, 2017 at 11:58 AM, Shu Shen  wrote:

> Hi Sam,
>
> OpenNFV maintains a version of OVS with NSH support, which is not
> supported by upstream OVS.
> Please refer to OpenNFV document:
> http://artifacts.opnfv.org/sfc/colorado/3.0/docs/
> scenarios_os-odl_l2-sfc-noha/index.html#specific-version-of-ovs
>
> /Shu
>
>
> On Wed, Jan 25, 2017 at 11:14 AM, sam su  wrote:
>
>> Thank you, Ben.
>>
>> Let me explain a little bit why I'm going to try NSH based on Openvswitch.
>> Because I saw a slides "SFC with NSH and OVS"( here is the link
>> http://openvswitch.org/support/ovscon2015/16/1040-elzur.pdf ), it looks
>> like the guy used openvswitch as a NSH classifier and a NSH forwarder
>> already.
>>
>> Thanks,
>> Sam
>>
>> On Wed, Jan 25, 2017 at 10:42 AM, Ben Pfaff  wrote:
>>
>>> On Wed, Jan 25, 2017 at 10:29:42AM -0800, sam su wrote:
>>> > I am going to try Openvswitch NSH function based on Ubuntu 16.04, how
>>> can I
>>> > confirm the installed Openvswitch(2.6.1) support NSH? If NSH is not
>>> > supported officially, is there any unofficial Openvswitch version
>>> support
>>> > NSH?
>>>
>>> Open vSwitch does not support NSH.
>>>
>>> I don't know about unofficial versions.  Perhaps someone will speak up.
>>>
>>
>>
>> ___
>> 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

Re: [ovs-discuss] About NSH support

2017-01-25 Thread Shu Shen

Hi Sam,

OpenNFV maintains a version of OVS with NSH support, which is not supported
by upstream OVS.
Please refer to OpenNFV document:
http://artifacts.opnfv.org/sfc/colorado/3.0/docs/scenarios_os-odl_l2-sfc-noha/index.html#specific-version-of-ovs

/Shu


On Wed, Jan 25, 2017 at 11:14 AM, sam su  wrote:

> Thank you, Ben.
>
> Let me explain a little bit why I'm going to try NSH based on Openvswitch.
> Because I saw a slides "SFC with NSH and OVS"( here is the link
> http://openvswitch.org/support/ovscon2015/16/1040-elzur.pdf ), it looks
> like the guy used openvswitch as a NSH classifier and a NSH forwarder
> already.
>
> Thanks,
> Sam
>
> On Wed, Jan 25, 2017 at 10:42 AM, Ben Pfaff  wrote:
>
>> On Wed, Jan 25, 2017 at 10:29:42AM -0800, sam su wrote:
>> > I am going to try Openvswitch NSH function based on Ubuntu 16.04, how
>> can I
>> > confirm the installed Openvswitch(2.6.1) support NSH? If NSH is not
>> > supported officially, is there any unofficial Openvswitch version
>> support
>> > NSH?
>>
>> Open vSwitch does not support NSH.
>>
>> I don't know about unofficial versions.  Perhaps someone will speak up.
>>
>
>
> ___
> 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

Re: [ovs-discuss] About NSH support

2017-01-25 Thread sam su

Thank you, Ben.

Let me explain a little bit why I'm going to try NSH based on Openvswitch.
Because I saw a slides "SFC with NSH and OVS"( here is the link
http://openvswitch.org/support/ovscon2015/16/1040-elzur.pdf ), it looks
like the guy used openvswitch as a NSH classifier and a NSH forwarder
already.

Thanks,
Sam

On Wed, Jan 25, 2017 at 10:42 AM, Ben Pfaff  wrote:

> On Wed, Jan 25, 2017 at 10:29:42AM -0800, sam su wrote:
> > I am going to try Openvswitch NSH function based on Ubuntu 16.04, how
> can I
> > confirm the installed Openvswitch(2.6.1) support NSH? If NSH is not
> > supported officially, is there any unofficial Openvswitch version support
> > NSH?
>
> Open vSwitch does not support NSH.
>
> I don't know about unofficial versions.  Perhaps someone will speak up.
>
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Re: [ovs-discuss] About NSH support

2017-01-25 Thread Ben Pfaff

On Wed, Jan 25, 2017 at 10:29:42AM -0800, sam su wrote:
> I am going to try Openvswitch NSH function based on Ubuntu 16.04, how can I
> confirm the installed Openvswitch(2.6.1) support NSH? If NSH is not
> supported officially, is there any unofficial Openvswitch version support
> NSH?

Open vSwitch does not support NSH.

I don't know about unofficial versions.  Perhaps someone will speak up.
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

[ovs-discuss] About NSH support

2017-01-25 Thread sam su

Hi,

I am going to try Openvswitch NSH function based on Ubuntu 16.04, how can I
confirm the installed Openvswitch(2.6.1) support NSH? If NSH is not
supported officially, is there any unofficial Openvswitch version support
NSH?

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

Re: [ovs-discuss] About controller rate limiting statistics

2016-12-05 Thread Ben Pfaff

I think you're right.  Can you provide a Signed-off-by, to indicate that
you agree to including the patch?  Please see CONTRIBUTING.rst for full
information.

Thanks,

Ben.

On Sat, Dec 03, 2016 at 11:46:35PM +, Ken Ajiro wrote:
> 
>   Hello,
> 
>   When I used controller packet-in rate limiting (controller_rate_limit in
>   controller table), I found that incorrect statistics was increased.
> 
>   I think that following fix is needed.
> 
>   Thanks,
> 
> -- 
> Ken Ajiro
> 
> 
> diff --git a/ofproto/connmgr.c b/ofproto/connmgr.c
> index 4b927d6..bfd1ff5 100644
> --- a/ofproto/connmgr.c
> +++ b/ofproto/connmgr.c
> @@ -539,7 +539,7 @@ connmgr_get_controller_info(struct connmgr *mgr, struct 
> shash *info)
> 
>  for (i = 0; i < N_SCHEDULERS; i++) {
>  if (ofconn->schedulers[i]) {
> -const char *name = i ? "miss" : "action";
> +const char *name = i == 0 ? "miss" : "action";
>  struct pinsched_stats stats;
> 
>  pinsched_get_stats(ofconn->schedulers[i], &stats);
> ___
> 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

[ovs-discuss] About controller rate limiting statistics

2016-12-03 Thread Ken Ajiro


  Hello,

  When I used controller packet-in rate limiting (controller_rate_limit in
  controller table), I found that incorrect statistics was increased.

  I think that following fix is needed.

  Thanks,

-- 
Ken Ajiro


diff --git a/ofproto/connmgr.c b/ofproto/connmgr.c
index 4b927d6..bfd1ff5 100644
--- a/ofproto/connmgr.c
+++ b/ofproto/connmgr.c
@@ -539,7 +539,7 @@ connmgr_get_controller_info(struct connmgr *mgr, struct 
shash *info)

 for (i = 0; i < N_SCHEDULERS; i++) {
 if (ofconn->schedulers[i]) {
-const char *name = i ? "miss" : "action";
+const char *name = i == 0 ? "miss" : "action";
 struct pinsched_stats stats;

 pinsched_get_stats(ofconn->schedulers[i], &stats);
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

42 matches

Mail list logo