>
> After your very helpful reply, I think my question summarizes to: the
> neoMatch struct does have a wildcarded Vlan, but shouldn't it be
> changed to 22 (in my previous test) by the
> "setDataLayerVirtualLan(22)" before the compare? Are you saying that
> "setDataLayerVirtualLan()" won't change
Hello Ali,
Thanks again for the usual fast reply.
After your very helpful reply, I think my question summarizes to: the
neoMatch struct does have a wildcarded Vlan, but shouldn't it be
changed to 22 (in my previous test) by the
"setDataLayerVirtualLan(22)" before the compare? Are you saying that
Hi Victor,
I believe there is a case which isn't caught by my code. If a flowmod wildcards
the vlan field, the neoMatch struct will also wildcard the vlan field and there
this will be ignored in the matching process and therefore result in the
behaviour you see.
What you want to express is th
Hello Ali,
I'm sorry for not supporting my statement before. I've prepared some
logs of what I did, which I hope will help you to understand better:
1) This is the FlowSpace: http://pastebin.com/FMNzVNaF
It contains only one rule, and its match is only dl_vlan = 1.
2) This is the POX code I'm u
I just reproduced this on a 1.2 FlowVisor and the flowmod is disallowed as
expected.
Could you send me you flowspace and perhaps a packet capture of whats going on?
Cheers.
--
Ali
On Sep 12, 2013, at 11:09 AM, Victor Torres wrote:
> Hello Ali,
>
> According to fvctl:
>
> FlowVisor version
Hello Ali,
According to fvctl:
FlowVisor version : flowvisor-1.2.0
FlowVisor DB version : 2
The bug in the previous version was about this
"setDataLayerVirtualLan()"? Because this behaviour seems to repeat for
nw_src, nw_dst, dl_src, dl_dst, tp_src and tp_dst, and they all seem
to use a similar
Hmm this sounds like a bug that we had in a previous version of FV. Could you
tell me what version you are running?
Cheers.
--
Ali
On Sep 12, 2013, at 4:30 AM, Victor Torres wrote:
> Hello Ali,
>
> I can't really thank you enough! I do have a situation I would like
> some help with.
>
> Giv
Hello Ali,
I can't really thank you enough! I do have a situation I would like
some help with.
Given the previous example situation, the fact is that I've tried it
in a "real" (mininet) setup and the FLOW_MOD from Alice do arrive at
the switch performing the action (SetVlanID(22)) even though its
> Thank you again and I'm sorry for bothering so much. After all this
> time theres one thing that I couldn't really figure out:
No worries, it's really not a problem.
>
> Suppose I have only one FlowSpace rule giving WRITE permissions to
> ALICE, and the match of this FlowSpace rule is dl_vlan=
Hello Ali,
Thank you again and I'm sorry for bothering so much. After all this
time theres one thing that I couldn't really figure out:
Suppose I have only one FlowSpace rule giving WRITE permissions to
ALICE, and the match of this FlowSpace rule is dl_vlan=1. ALICE then
tries a FLOW_MOD (with an
>
> 1) When I send a FLOW_MOD with an Action to change de DL_VLAN, we talk
> about SwitchFlowMap, which seems to come from the FlowSpaceUtil. Does
> this mean that this SwitchFlowMap and the FlowEntries it talks about
> are from the configured FlowSpace rules?
>
Yes those are the ones.
> 2) I
Hello Ali,
Thanks again for the quick and so helpful support.
I've been looking at the code for quite some time now, and some things
seem specially tricky for me to understand:
1) When I send a FLOW_MOD with an Action to change de DL_VLAN, we talk
about SwitchFlowMap, which seems to come from t
Hi Victor,
So what you are saying is correct. When a FlowMod arrives from a controller we
know which slice/controller it's from. Therefore, the flowmod's match struct is
matched against the flowspace of that slice. Then, for every flowspace rules
matching the flowmod's match the original flowmo
Hello again Ali,
Thank you for all you support so far. I think theres no way for me but
to go into FlowVisor's code. So, at first, I have a question and
appreciate any direction on how to go on with this:
At first, I'm really interested in how FLOW_MOD messages are handled.
According to the FV Wi
> 1) So FV does update its FlowTable Cache from OF Messages going Switch <->
> Controller. But when you say "at most every 30s, means that if it doesn't get
> any update it asks the switch for its FlowTable? The FlowMod thing means that
> the FlowVisor asks periodically for the switch for modifi
Hi Ali,
Thanks again for your quick reply, its been a huge help! Just to see if I'm
getting things right:
1) So FV does update its FlowTable Cache from OF Messages going Switch <->
Controller. But when you say "at most every 30s, means that if it doesn't
get any update it asks the switch for its
Hi Victor,
> 1) Does FlowVisor updates its FlowDB as OF Messages pass through it? Or does
> it asks directly the switches for their Flow Tables? Reading the source code
> I'm inclined to think of the first option.
You are mostly right. Flowvisor stores a cache of the flowtable which it
refresh
Helllo Ali,
Thanks for your message!
If I may, I would like to ask two more questions:
1) Does FlowVisor updates its FlowDB as OF Messages pass through it? Or
does it asks directly the switches for their Flow Tables? Reading the
source code I'm inclined to think of the first option.
2) I would
Hi Victor,
Currently, you cannot specify which openflow actions are allowed on a per
flowspace basis. This is clearly a desirable feature but unfortunately we have
not addressed it yet. We would welcome any pull requests/contributions in this
direction.
Cheers.
--
Ali
On Aug 30, 2013, at 11:
Hello,
Does anybody know if it is possible to define allowed/denied actions for
slices in FlowVisor?
Best regards,
Victor T.
___
openflow-discuss mailing list
openflow-discuss@lists.stanford.edu
https://mailman.stanford.edu/mailman/listinfo/openflow-d
20 matches
Mail list logo
