Thanks Asadullah,
I did try to add dl_type=0x0800 before, unfortunately, it did not help.
On Wed, Nov 20, 2013 at 8:53 PM, Asadullah Hussain wrote:
> Just a suggestion, Try "dl_type=0x0800" (ethernet packets) in the rule
> too. This may help in rule matching too.
>
>
> On 21 November 2013 05:23
Just a suggestion, Try "dl_type=0x0800" (ethernet packets) in the rule too.
This may help in rule matching too.
On 21 November 2013 05:23, terryxing wrote:
> Hi Ben,
>
>
> I have three VMs, I want like this, VM1 ping VM2, duplicate the packets to
> VM3
>
> root@node-35:~# ovs-ofctl add-flow br-
Hi Ben,
I have three VMs, I want like this, VM1 ping VM2, duplicate the packets to
VM3
root@node-35:~# ovs-ofctl add-flow br-int
"dl_src=VM1,priority=100,actions=NORMAL,mod_dl_dst=vm3_mac_address,NORMAL"
I can use the above command to make the packet first output to normal, and
then modify the
I tried the add-flow command before, and it is just there when I use
dump-flows to see the flow table. I am just wondering that if it will just
staying there if I keep the OVS running.
BTW, the port mirroring works, Thank your so much.
On Tue, Nov 12, 2013 at 10:30 AM, Ben Pfaff wrote:
> When
When you try it, what do you see?
On Tue, Nov 12, 2013 at 09:56:27AM -0800, terryxing wrote:
> it is okay for the short-lived controller exit, but will the rule last in
> OVS If I just keep it running ?
>
>
> On Tue, Nov 12, 2013 at 8:00 AM, Ben Pfaff wrote:
>
> > On Mon, Nov 11, 2013 at 11:23
Thanks Ben,
it is okay for the short-lived controller exit, but will the rule last in
OVS If I just keep it running ?
On Tue, Nov 12, 2013 at 8:00 AM, Ben Pfaff wrote:
> On Mon, Nov 11, 2013 at 11:23:36PM -0800, terryxing wrote:
> > What do you mean by short-lived ? How long it can last and ca
On Mon, Nov 11, 2013 at 11:23:36PM -0800, terryxing wrote:
> What do you mean by short-lived ? How long it can last and can I save the
> flowtable ?
Most controllers run until you stop them. ovs-ofctl connects and
executes the command you give it, then exits.
_
Thanks Ben,
I actually thought about using the NORMAL as the output action in OVS CLI
but It seems like the syntax is not correct. About the last part of you
answer, I can set the action as NORMAL, mod_nw_dst, NORMAL, thus, the last
NORMAL means the OVS will behave like a L2/L3 normal switch to
On Mon, Nov 11, 2013 at 09:14:54PM -0800, terryxing wrote:
> 1. I am wondering that what the OVS is running like without connection any
> controller ? Because I thought it is just a layer 2 switch.
Yes, that's right.
> but when I run a openflow controller talking to it.(I tried pox and
> flood
Hi Ben,
Thanks for your reply. I will try the command you mentioned tomorrow. I
have another two question to bother you.
1. I am wondering that what the OVS is running like without connection any
controller ? Because I thought it is just a layer 2 switch. but when I run
a openflow controller
On Mon, Nov 11, 2013 at 04:50:37PM -0800, terryxing wrote:
> I tried the command line below by change the set into add you mentioned but
> it did not work,
>
> I tried the below one, it did not work, it said add command requires at
> least 4 arguments.
>
> ovs-vsctl -- add Bridge br-int mirrors=@
Thanks Ben,
I tried the command line below by change the set into add you mentioned but
it did not work,
I tried the below one, it did not work, it said add command requires at
least 4 arguments.
ovs-vsctl -- add Bridge br-int mirrors=@m -- --id=@vm4 get port
tapa0a5bd27-98 -- --id=@vm3 get port
On Mon, Nov 11, 2013 at 02:31:13PM -0800, terryxing wrote:
> I have a question about the port mirror.
>
> I use the command line as below: I just want to implement the port mirror
> algorithm like this, on the same bridge, mirror ovs port 1 traffic to ovs
> port 10, and mirror ovs port 2 traffic t
Hi Ben
Thanks very much for your kind reply.
I have a question about the port mirror.
I use the command line as below: I just want to implement the port mirror
algorithm like this, on the same bridge, mirror ovs port 1 traffic to ovs
port 10, and mirror ovs port 2 traffic to ovs port 11 and
On Mon, Nov 11, 2013 at 01:18:38PM -0800, terryxing wrote:
> Port mirroring is a good way and I did that. But, I can not create multiple
> port mirroring on a single bridge. For example, H1 packet will be
> duplicated to H4 port, and H3 packet will be duplicated to H5 port. Based
> on my underst
Hi Ben
Thanks for your quick and kind reply.
Port mirroring is a good way and I did that. But, I can not create multiple
port mirroring on a single bridge. For example, H1 packet will be
duplicated to H4 port, and H3 packet will be duplicated to H5 port. Based
on my understanding, port mirrori
On Mon, Nov 11, 2013 at 10:45:53AM -0800, terryxing wrote:
> I have a question about the ovs-ofctl command line to add flow.
>
> What I want is that, assume that I have 4 vms (H1, H2, H3 and H4)
> connecting to the same bridge. when H1 send a packet for H2, I want it also
> forwards to H4.
You
Hi Dear All,
I have a question about the ovs-ofctl command line to add flow.
What I want is that, assume that I have 4 vms (H1, H2, H3 and H4)
connecting to the same bridge. when H1 send a packet for H2, I want it also
forwards to H4. I can append the H4 output port to the actions output ports
b
18 matches
Mail list logo
