Hello everyone, any news about support ovs for group table feature?

Mainly fast failover, in ovs-ofctl.

It would be a show ....

Alextian


2014-02-04 <[email protected]>:

> Send discuss mailing list submissions to
>         [email protected]
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         http://openvswitch.org/mailman/listinfo/discuss
> or, via email, send a message with subject or body 'help' to
>         [email protected]
>
> You can reach the person managing the list at
>         [email protected]
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of discuss digest..."
>
>
> Today's Topics:
>
>    1. Re: dec_ttl action doesn't work and sorry for     multiple posts.
>       (Justin Pettit)
>    2. flow removal messages from ovs (Pradeep Kiruvale)
>    3. Problem install OVS on a XEN System (G?nther J. Niederwimmer)
>    4. Re: flow removal messages from ovs (Ben Pfaff)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 3 Feb 2014 20:52:12 -0800
> From: Justin Pettit <[email protected]>
> Subject: Re: [ovs-discuss] dec_ttl action doesn't work and sorry for
>         multiple posts.
> To: Allan Jie <[email protected]>
> Cc: "[email protected]" <[email protected]>
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset="us-ascii"
>
> Does it properly decrement the TTL if you don't modify the TOS?  Does it
> behave as you'd expect with OVS 2.0 (the latest release)?
>
> --Justin
>
>
> > On Feb 3, 2014, at 7:00 PM, Allan Jie <[email protected]> wrote:
> >
> > I want to clarify the problem. And I don't why I cannot post that
> correctly.
> >
> > Now here is the thing.
> > I start a network like 4 host and 1 switches.
> > h1,h2 and s1.
> >
> > I know the dec_ttl action is for ipv4 packet and openflow 1.1+.
> >
> > So I have finished this command.
> > ovs-vsctl set bridge s1 protocols=OpenFlow10,OpenFlow12,OpenFlow13
> > And also use -O OpenFlow13 in ovs-ofctl.
> > Like the following line:
> > ovs-ofctl -O OpenFlow13 add-flow s1
> table=0,priority=65535,ip,in_port=1,vlan_tci=0x0000,dl_src=9e:60:7c:45:f2:b8,dl_dst=32:a2:19:d3:56:4f,nw_src=10.0.0.1,nw_dst=10.0.0.2,nw_proto=0,nw_tos=0,actions=output:2,dec_ttl
> >
> > Then in h1, I use the command
> > h1 sendip -d dsf -p ipv4 -is 10.0.0.1 -id 10.0.0.2 10.0.0.2
> > which will send an "ip packet" from h1 to h2.
> >
> > And then in h2, I use this command to listen the port.
> > tcpdump ip host 10.0.0.1 -v
> >
> > But the result is I cannot see any changes of the ttl in the received
> packet. The ttl value is still 64.
> >
> >
> > I have done that according to Justin information. But I still cannot get
> it work. I change the ovs-ofctl like this as you said. (position of dec_ttl
> and output)
> > ovs-ofctl -O OpenFlow13 add-flow s1
> table=0,priority=65535,ip,in_port=1,dl_src=3e:a4:62:46:92:28,dl_dst=86:9e:4b:4c:54:53,nw_src=10.0.0.1,nw_dst=10.0.0.2,nw_proto=0,nw_tos=0,actions=dec_ttl,output:2
> >
> > However, when I also use another actions, it seems that it doesn't work
> too. Like I use this following actions
> > actions=del_ttl,mod_nw_tos:0x08,output:2
> > But I use tcpdump ip host 10.0.0.1 -v
> > I cannot see any change of the "tos" value of the packet. Here comes the
> result of tcpdump
> > ------------------------------------
> > 10.0.0.1 > 10.0.0.2:  ip 3
> > 17:57:42.921902 IP (tos 0xc0, ttl 64, id 56235, offset 0, flags [none],
> proto ICMP (1), length 51)
> > --------------------------------
> > My environment is mininet 2.1 and openvswitch 1.10.
> >
> > Maybe I will try to clarify my problem again.
> > My setup is very simple. Using Mininet to configure this network.
> > h1 (h1-eth0)----(s1-eth1)s1(s1-eth2)---(h1-eth0)h2.
> >
> > I start the network using this command.
> > sudo mn --switch ovsk --mac --custom ~/mininet/custom/LinkCustom.py
> --topo mytopo
> > BTW, I try to use the following command to modify something.
> > sudo ovs-ofctl -O OpenFlow13 add-flow s1
> table=0,priority=65535,ip,in_port=1,dl_src=fe:81:d2:69:f6:74,dl_dst=de:dc:30:cd:6f:66,nw_src=10.0.0.1,nw_dst=10.0.0.2,nw_proto=0,nw_tos=0,actions=dec_ttl,mod_nw_dst:10.0.0.3,mod_dl_dst:00:00:00:00:00:11,output:2
> >
> > And it did change the dst ip and dst mac. (I also use tcpdump command to
> monitor on the h2 side)
> > However, dec_ttl still doesn't work. Can anybody help me out?
> >
> >
> > --
> > Research student, final-year undergraduate
> > Extreme Scale Network Computing and service laboratory(
> http://www.cloud-uestc.cn/cloud-uestc-EN/index.html),
> > School of Computer Science & Engineering,
> > University of Electronic Science and Technology of China(
> http://www.oice.uestc.edu.cn/en/).
> > Website: http://www.allanjie.ml/
> > _______________________________________________
> > discuss mailing list
> > [email protected]
> > http://openvswitch.org/mailman/listinfo/discuss
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://openvswitch.org/pipermail/discuss/attachments/20140203/fc1cb151/attachment-0001.htm
> >
>
> ------------------------------
>
> Message: 2
> Date: Tue, 4 Feb 2014 15:00:19 +0100
> From: Pradeep Kiruvale <[email protected]>
> Subject: [ovs-discuss] flow removal messages from ovs
> To: [email protected]
> Message-ID:
>         <CAJ2SuL=8ZR1j8BFPZgPM9buHnkfpd0DhzT38u=
> [email protected]>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi All,
>
> Myself Pradeep,new to ovs.I am doing a project where in I am using
> floodlight open flow controller with ovs.I have subscribed  for flow
> removal messages from the switch.I am supposed to receive only one message
> per removal of flow,but I am receiving two message per flow removal.please
> let me know what is the reason.
>
> Thanks,
> Pradeep
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://openvswitch.org/pipermail/discuss/attachments/20140204/af5e5ebb/attachment-0001.htm
> >
>
> ------------------------------
>
> Message: 3
> Date: Tue, 04 Feb 2014 16:21:46 +0100
> From: G?nther J. Niederwimmer <[email protected]>
> Subject: [ovs-discuss] Problem install OVS on a XEN System
> To: [email protected]
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset="utf-8"
>
> Hello,
>
> "openvswitch 2.0.0"
>
> I have installed and running OVS on a opensuse KVM System this is working
> excellent ;)
>
> now i like to do this also on a SLES 11 XEN System but ...
>
> I have the question can any tell me a link with a Help Page for this
> problem?
>
> I mean files are missing (vif-openvswitch and ?)
>
> The SLES have the kernel 3.0.101 and xen-4.2.3
>
> without a config openvswith is starting and running fine ;)
>
> but with a config I have no network an whole System :(.
>
> --
> mit freundlichen Gr??en / best Regards,
>
>   G?nther J. Niederwimmer
>
>
> ------------------------------
>
> Message: 4
> Date: Tue, 4 Feb 2014 07:55:57 -0800
> From: Ben Pfaff <[email protected]>
> Subject: Re: [ovs-discuss] flow removal messages from ovs
> To: Pradeep Kiruvale <[email protected]>
> Cc: [email protected]
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset=us-ascii
>
> On Tue, Feb 04, 2014 at 03:00:19PM +0100, Pradeep Kiruvale wrote:
> > Myself Pradeep,new to ovs.I am doing a project where in I am using
> > floodlight open flow controller with ovs.I have subscribed  for flow
> > removal messages from the switch.I am supposed to receive only one
> message
> > per removal of flow,but I am receiving two message per flow
> removal.please
> > let me know what is the reason.
>
> This bug was fixed some time ago.  I guess you're using an older
> version.
>
>
> ------------------------------
>
> _______________________________________________
> discuss mailing list
> [email protected]
> http://openvswitch.org/mailman/listinfo/discuss
>
>
> End of discuss Digest, Vol 56, Issue 12
> ***************************************
>



-- 
Alextian Bartholomeu Liberato, M.Sc
(27) 9510-9125
_______________________________________________
discuss mailing list
[email protected]
http://openvswitch.org/mailman/listinfo/discuss

Reply via email to