that makes sense. thanks Ben!
___
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss
Hi
if I have a rule, nw_src=192.168.0.0/16 and a specific rule,
nw_src=192.168.0.1/32 and a packet comes from 192.168.0.1, which rule will it
match? the /16 or /32? I want to match the 192.168.0.1 packet even if I have
both rules
_
Hi
is there a way to tag a packet in OVS? (I don't mean VLANs). by a tag, it could
be a boolean value or something that can help separate two packets coming from
the same src and dst with same MAC.
___
discuss ma
Thanks Ben. while I don't need it yet but would be good to know - is there a
way to profile flows in OVS (other than the obvious way of just running and
testing)?
>> is it better to specify nw_src in addition to nw_dst? My question can
>> also be worded as that for better performance for lots of
Hi..
is it better to specify nw_src in addition to nw_dst? My question can also be
worded as that for better performance for lots of flows, which is better:
specifying explicit flow rules or wildcarded ones?
nw_src: X, nw_dst: Y
- vs -
nw_dst: Y
Hi Ben
thanks for the tip.
> ovs-ofctl add-flow br0
> 'ip,nw_src=0.128.0.0/0.128.0.0,actions=load:0->NXM_OF_IP_SRC[23]'
> ovs-ofctl add-flow br0
> 'ip,nw_src=0.0.0.0/0.128.0.0,actions=load:1->NXM_OF_IP_SRC[23]'
Is it possible to wildcard this? This is what I did:
sudo ovs-ofctl add-flow br0 'ip
Hi Justin
Thanks for replying
> mailto:jasonthor...@outlook.com>> wrote:
> is it possible to modify specific bits of an IP address when setting
> flow rules for a switch? (using add-flow and
> actions=mod_nw_{src,dst} ).
>
> That won't work, since that action is expecting a specific IP addre
hi
is it possible to modify specific bits of an IP address when setting flow rules
for a switch? (using add-flow and actions=mod_nw_{src,dst} ).
basically, I am looking for setting actions on the IP address to change some
source/destination. like modifying all IPs from 192.168.0.* to 192.168.1.*
