[pox-dev] how to specify wildcards in ofp_match.from_packet()?

[William Emmanuel Yu]

Nice touch. Adding both flow rules in one go. Thanks.

On Mon, 2012-09-24 at 05:41 -0700, Murphy McCauley wrote:
> Check l2_pairs in the betta branch for a rough example, BTW.
> 
> -- Murphy 
> 
> On Sep 24, 2012 5:39 AM, "William Emmanuel S. Yu" <wyu at ateneo.edu>
> wrote:
>         Its a bummer but it will have to do. Thanks.
>         ------Original Message------
>         From: Murphy McCauley
>         To: aaa-William Yu
>         Cc: pox-dev at lists.noxrepo.org
>         Subject: Re: [pox-dev] how to specify wildcards in
>         ofp_match.from_packet()?
>         Sent: Sep 24, 2012 8:29 PM
>         
>         On Sep 24, 2012, at 5:13 AM, William Emmanuel S. Yu wrote:
>         
>         > Oh my. Definitely a great point I missed out.  So does this
>         mean there is no solution that allow us to a good
>         destination-only flow rule at L2? So source awareness is
>         mandatory to ensure "learning".
>         
>         I wouldn't bet my house on it, but I think that is true if you
>         are working within the OpenFlow 1.0 specification.
>         (Note that this also means you have on the order of
>         hosts-squared rules if you're doing learning in 1.0.)
>         
>         -- Murphy
>         
>         "Sent on the move."

-- 
-------------------------------------------------------
William Emmanuel S. Yu, Ph.D. (杨怀义)
Department of Information Systems and Computer Science
Ateneo de Manila University
email  :  wyu at ateneo dot edu
blog   :  http://hip2b2.yutivo.org/
web    :  http://CNG.ateneo.edu/cng/wyu/
phone  :  +63(2)4266001 loc. 4186
GPG    :  http://CNG.ateneo.net/cng/wyu/wyy.pgp

Confidentiality Issue:  This message is intended only for the use of the
addressee and may contain information that is privileged and
confidential. If you are not the intended recipient, you are hereby
notified that any use or dissemination of this communication is strictly
prohibited.  If you have received this communication in error, please
notify us immediately by reply and delete this message from your system.