[ovs-dev] Is this your personal account?

2016-06-04 Thread albert raj
Hello, 
 
Just wanted to know where I should send you the profits you'll be making?
 
My team is all setup and ready to welcome you on board,
so that we can start you on one of the most amazing pesos making journeys 
you'll ever take.
 
>>
CLICK HERE TO START YOUR JOURNEY 
Let's not waste another minute, click the link below and your first commissions 
will be coming in as early as in the next 30 minutes.
 
>>
CLICK HERE TO START EXPEDITION 
To your success, Russell Duran
___
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev


[ovs-dev] Delivery reports about your e-mail

2016-06-04 Thread Mail Administrator
Dear user of openvswitch.org,

Your e-mail account was used to send a huge amount of spam messages during this 
week.
Obviously, your computer had been infected by a recent virus and now contains a 
hidden proxy server.

Please follow the instructions in order to keep your computer safe.

Have a nice day,
The openvswitch.org support team.

___
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev


[ovs-dev] [PATCH] vtep: add per-tunnel tunnel key support in vtep-ctl and ovs-vtep. related to commit c2cd1902

2016-06-04 Thread Itamar Ofek

___
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev


[ovs-dev] Respond for immediate verification

2016-06-04 Thread CINDY LIU
Hello,

This is to inform you that an ATM Card has been accredited in your favor. The 
ATM Card Value is US$830,000.00.
You are to send :  Your Name, Address,Phone and Occupation for verification.

Cindy Liu
___
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev


[ovs-dev] [PATCH] VxLAN-gpe implementation

2016-06-04 Thread Yi Yang
Current Linux kernel git tree has included VxLAN-gpe implementation

author  Jiri Benc 
committer   David S. Miller 
commit  e1e5314de08ba6003b358125eafc9ad9e75a950c (patch)
tree1e18cdabf1c9d9ef17e26c6480e629465447f77f /drivers/net/vxlan.c
parent  a6d5bbf34efa8330af7b0b1dba0f38148516ed97 (diff)
vxlan: implement GPE

This patch is to port it to ovs in order that people also can use VxLAN-gpe
even if they don't replace their kernels with latest Linux kernel.

Signed-off-by: Johnson Li 
Signed-off-by: Yi Yang 
---
 datapath/linux/compat/include/linux/if_link.h |   2 +
 datapath/linux/compat/include/linux/openvswitch.h |   1 +
 datapath/linux/compat/include/net/vxlan.h |  72 ++
 datapath/linux/compat/vxlan.c | 160 +++---
 datapath/vport-netdev.c   |   3 +-
 datapath/vport-vxlan.c|  17 ++-
 lib/netdev-vport.c|   4 +-
 7 files changed, 236 insertions(+), 23 deletions(-)

diff --git a/datapath/linux/compat/include/linux/if_link.h 
b/datapath/linux/compat/include/linux/if_link.h
index 6209dcb..4fe5add 100644
--- a/datapath/linux/compat/include/linux/if_link.h
+++ b/datapath/linux/compat/include/linux/if_link.h
@@ -100,6 +100,8 @@ enum {
IFLA_VXLAN_REMCSUM_NOPARTIAL,
 #define IFLA_VXLAN_COLLECT_METADATA rpl_IFLA_VXLAN_COLLECT_METADATA
IFLA_VXLAN_COLLECT_METADATA,
+#define IFLA_VXLAN_GPE rpl_IFLA_VXLAN_GPE
+IFLA_VXLAN_GPE,
 #define __IFLA_VXLAN_MAX rpl___IFLA_VXLAN_MAX
__IFLA_VXLAN_MAX
 };
diff --git a/datapath/linux/compat/include/linux/openvswitch.h 
b/datapath/linux/compat/include/linux/openvswitch.h
index 3b39ebb..bd37594 100644
--- a/datapath/linux/compat/include/linux/openvswitch.h
+++ b/datapath/linux/compat/include/linux/openvswitch.h
@@ -287,6 +287,7 @@ enum ovs_vport_attr {
 enum {
OVS_VXLAN_EXT_UNSPEC,
OVS_VXLAN_EXT_GBP,  /* Flag or __u32 */
+   OVS_VXLAN_EXT_GPE,  /* Flag, Generic Protocol Extension */
__OVS_VXLAN_EXT_MAX,
 };
 
diff --git a/datapath/linux/compat/include/net/vxlan.h 
b/datapath/linux/compat/include/net/vxlan.h
index 75a5a7a..25b3e24 100644
--- a/datapath/linux/compat/include/net/vxlan.h
+++ b/datapath/linux/compat/include/net/vxlan.h
@@ -84,6 +84,66 @@ struct vxlanhdr_gbp {
 #define VXLAN_GBP_POLICY_APPLIED   (BIT(3) << 16)
 #define VXLAN_GBP_ID_MASK  (0x)
 
+/*
+ * VXLAN Generic Protocol Extension (VXLAN_F_GPE):
+ * +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+ * |R|R|Ver|I|P|R|O|   Reserved|Next Protocol  |
+ * +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+ * |VXLAN Network Identifier (VNI) |   Reserved|
+ * +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+ *
+ * Ver = Version. Indicates VXLAN GPE protocol version.
+ *
+ * P = Next Protocol Bit. The P bit is set to indicate that the
+ * Next Protocol field is present.
+ *
+ * O = OAM Flag Bit. The O bit is set to indicate that the packet
+ * is an OAM packet.
+ *
+ * Next Protocol = This 8 bit field indicates the protocol header
+ * immediately following the VXLAN GPE header.
+ *
+ * https://tools.ietf.org/html/draft-ietf-nvo3-vxlan-gpe-01
+ */
+
+struct vxlanhdr_gpe {
+#if defined(__LITTLE_ENDIAN_BITFIELD)
+   u8  oam_flag:1,
+   reserved_flags1:1,
+   np_applied:1,
+   instance_applied:1,
+   version:2,
+reserved_flags2:2;
+#elif defined(__BIG_ENDIAN_BITFIELD)
+   u8  reserved_flags2:2,
+   version:2,
+   instance_applied:1,
+   np_applied:1,
+   reserved_flags1:1,
+   oam_flag:1;
+#endif
+   u8  reserved_flags3;
+   u8  reserved_flags4;
+   u8  next_protocol;
+   __be32  vx_vni;
+};
+
+/* VXLAN-GPE header flags. */
+#define VXLAN_HF_VER   (BIT(29) | BIT(28))
+#define VXLAN_HF_NP(BIT(26))
+#define VXLAN_HF_OAM   (BIT(24))
+#define VXLAN_HF_GPE   (BIT(26))
+
+#define VXLAN_GPE_USED_BITS (VXLAN_HF_VER | VXLAN_HF_NP | VXLAN_HF_OAM | \
+(0xFF))
+
+/* VXLAN-GPE header Next Protocol. */
+#define VXLAN_GPE_NP_IPV4  0x01
+#define VXLAN_GPE_NP_IPV6  0x02
+#define VXLAN_GPE_NP_ETHERNET  0x03
+#define VXLAN_GPE_NP_NSH   0x04
+#define ETH_P_NSH  0x894f
+
 /* VXLAN protocol header:
  * +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  * |G|R|R|R|I|R|R|C|   Reserved|
@@ -120,6 +180,7 @@ struct vxlanhdr {
 struct vxlan_metadata {
__be32  vni;
u32 gbp;
+u32 gpe;
 };
 
 #define VNI_HASH_BITS  10
@@ -205,15 +266,26 @@ struct vxlan_dev {
 #define VXLAN_F_GBP0x800
 #define VXLAN_F_REMCSUM_NOPARTIAL  0x1000
 #define VXLAN_F_COLLECT_METADATA   0x2000
+#define VXLAN_F_GPE   

Re: [ovs-dev] finally it has been released and it’s free

2016-06-04 Thread wilfrid payman
Hello, 
 
Just wanted to know where I should send you the profits you'll be making?
 
My team is all setup and ready to welcome you on board,
so that we can start you on one of the most amazing pesos making journeys 
you'll ever take.
 
>>
CLICK HERE TO START YOUR JOURNEY 
Let's not waste another minute, click the link below and your first commissions 
will be coming in as early as in the next 30 minutes.
 
>>
CLICK HERE TO START EXPEDITION 
To your success, Abdul Justice
___
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev


Re: [ovs-dev] [PATCH v4] Add configurable OpenFlow port name.

2016-06-04 Thread Xiao Liang
Thanks for your review!

On Sat, Jun 4, 2016 at 1:15 AM, Ben Pfaff  wrote:
> On Tue, May 24, 2016 at 03:07:23PM +0800, Xiao Liang wrote:
>> Add new column "ofname" in Interface table to configure port name reported
>> to controllers with OpenFlow protocol, thus decouple OpenFlow port name from
>> device name.
>>
>> For example:
>> # ovs-vsctl set Interface eth0 ofname=wan
>> # ovs-vsctl set Interface eth1 ofname=lan0
>> then controllers can recognize ports by their names.
>>
>> Signed-off-by: Xiao Liang 
>> ---
>> v2: Added test for ofname
>> Increased db schema version
>> Updated NEWS
>> v3: Rebase
>> v4: Rebase
>> Move prototypes in ofproto/ofproto.h to correct section
>
> Thanks for the patch!  I think that this is a reasonable approach.
>
> I'd like ovs-ofctl to report an error if a user attempts to refer to a
> port by name but there is more than one port with the name.  That could
> be in a separate patch.

And what do you think of also adding an option (say, "--all") to
select all ports with the name?

>
> The logic in ofproto_port_set_ofpname() does not make sense to me in the
> third case here:
>
> if (!devname ||
> (ofp_name && !strncmp(ofp_name, ofport->pp.name, name_size - 1)) ||
> (!ofp_name && !strncmp(devname, ofport->pp.name, name_size - 1))) {
> /* No need to change port name. */
> return;
> }
>
> I believe that in the
> (!ofp_name && !strncmp(devname, ofport->pp.name, name_size - 1))) {
> case, we should remove any current ofp_name and change the name of the
> OpenFlow port back to the device name, but instead the code appears to
> do nothing.

In this case, the OpenFlow port name is already the same as devname
(strncmp). I think it's not necessary to remove the smap entry here
because it would be overwritten if changed later.

>
> It is too bad that the ofp_names smap exists at all.  It seems that it
> should be possible to simply represent the ofp_name inside the ofport,
> without the need for a separate map.

I don't like the smap, too. But didn't find a good way to get rid of
it. In update_port, ofproto_port and ofputil_phy_port are filled with
information from dpif. There seems no way to pass ofp_name here except
embedding it in dpif. So I followed the way of ofp_requests, putting
it into a map. Do you have any suggestions? And please correct me if
I'm wrong.

>
> It would be a good idea to mention the possibility of duplicate names in
> the documentation in vswitch.xml.
>

Yes, I will add this in next version.

Thanks,
Xiao
___
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev


[ovs-dev] Delivery reports about your e-mail

2016-06-04 Thread Automatic Email Delivery Software
ó÷‘ÇRE'Цƒ±¬Rý“vϒ‡ŠÌ;ÎdL¸2 ƒ2ž]Ë&“BVjñçådK"š‡‚Î8þ®âÙ
[út>[çÇ·©D¤`~—xÚÒï!ÒßX&"Nƒç϶2YnÍs™1IªKäÄv{TKmPâÖsɗlËN*{>ïëcܙè|kݺۗâg
.ڊÎ^qè¦Ê«ÅøÄj 
¦žÐné.´-¡é¶Ãðn¡à¯¾òe;/F,‘kFϪmAzëiÃæN²†*Fº’zá0¿pŸÉÃN»òÍNp¬_¼í‰˜¬à¿Z³‹Æ!
iצ©­«±/°;üÜ3½røÆ,ã
ЎÄ4‚iùzÌ[¬x}þõì¦ö~(‘Ëe 
š§8SאC¾DU¿zÜàt0öõ\ٔÂdÉí[Ç5Šk÷;-¹«ï~¿y‡šF»ðÒ^:%JÚæ“b°7š<øv&1âOIá2,`r£Ü&¡|‡B¨ÈQýDhƒOҖb‘gàJZ˜«¡D¨äOƒË„âá\÷y*oRÁ£íJÙò‘‘â.xÕxPÏÆ%è0íFÊRa×üà¹~eí´ITYÂ:
°Ê‰jSúF-s½]¥‰Rì‘á
¥Ö˜EÎçà$§Í–3Ë69
ú?zYµÌ[ǨËrª3ÔI¶¾wd-šÞxKþ#Õq<-…–Ÿcà&K?Ÿ|#¯í¹e޾­³ízÆùñ‘díh¬ª÷آܓ‰
cbæ•2YõHJfL6Cåk/øV[µùÅ2¾ ¤ÎdÂSSð~B¡³ÀÜõ…
ò¦À|ÁÕÞ|H:A‘w­˜>5O²ÛßÚ¼|¹iúPð>É$Ïè¨Æ¦_ò9ZÂì‰Ä®"˜Àåb§®Í>ßôïÌyxêÜ,»4å{­—
óÕÌ$±!l»PGè
¶æ†Ù½¡ÌYnŠ¢¿ë4:uÝ5ÅÏZ–,.‘L½ýªæ.¸x×F³bù~ŠÏ¡“žˆÀ˜»bo7¤„Gº}G8ƙ5ÐöBÛøËJ
ïٗ5æº?{tR¶”9
û杴ÄSÄãÓeˆ ³žý
Î9Êïù
`2Å$Øõ•)BÆ­µµl9ø¿²u´
¸#5jÑß±l£ìPÝLMLVmÔVk<Ó¸‹[ËC»ëâGᥳët5ß%ÂqlzV~cäròFw丵õ¹
íú ¦„ayµ9AB†Gñ<2h캱`-–¡¼”¬ÅJc]d¸w¬…
¤Œ®I&P9ÞJ$¨wå«"{Œ*'kËAFž–W¹÷ô‡6ü|~n0†‡pëtÏ´tTù÷4|ìÊ°&ȸà4Þ½,Fh°3Yíòñ֙AˆWÜÀ,VhÍì‰kùä&Ҍ¤(lÒÛÍmá£G'W{YáÑâfÔ9J
 ÂÜïœ?aÐ\…¦Z1ô̑ÈÎx܄.äýbÀ¯¯†1¿è ñÙ
Âýå2¼¥¼’¬Cûµ÷6Ú:R>Óô¶—CÆ!’‹?hŠËÕ
ÞS枟kiâ—
ä¬ÖU“7¥ªO?}Œ‘i³Ø‡þÞ³G-bŽXP]gs¹TwPþJû/›D‹¸µÞÅ`°w´®gÜî«ß×(QÈ¡¸28èÓ4ú´®ýݒñ_§BUâÙ¿»÷ºUÒÜxÏ×xûÊí
ɇ®ÐŽ 1.¿Ü`òúÎÑoé[·[SZˆc¤qÃ!#2un×
É9ñÝ-­‘E0ŠËf8x5œ¡¿ìò̼1µ|PëùX`$
nSˆ!«—é~dšjW˜Çø‹Aʦ†tëvö}èn~™pb0šªs•þ'¢ŸàeÙ¦ZÈáUÙÜà¦1qmR*h¿Û²…
ΧuÚ7H£Û6p#æM–p>MÑ¢/HÑðnÑ}²Ÿà$ÐÑÙò6x߃*¾ø¥ê·¡¼5³Ëæï½în4Z«ääSŒËø}]j¹µºÇ¾˜4­^÷TøM'÷H\Úà
 ×WLÌ¥½•£–Ï“¸ä”mïKD75¤KßИ«4rê<£c±Ü¾Ã§mtÕ𝄌^(Pô'CÜXØý
‡ àÖ°çÂùXLØâµð¢øOÓyŒDŠì)×>Ç¿åa»yŠfÄLÀd±—ÙLú~‡7fù-§z‰ø·Œ‹¸ŒÚ¨òyu˜§ê^ÇÃF—b…p dæ
*ˆI›æ±½ÐØ£bBc(E®$
6Ü08ŽÀx9ѶR

___
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev