Yea, but the current approach is not working though.....
File
"/home/tester/.pyenv/versions/2.7.5/lib/python2.7/site-packages/ryu/lib/ofctl_v1_3.py",
line 368, in to_match_ipv6
ip = netaddr.IPNetwork(value)
File
"/home/tester/.pyenv/versions/2.7.5/lib/python2.7/site-packages/netaddr/ip/__init__.py",
line 917, in __init__
raise AddrFormatError('invalid IPNetwork %s' % addr)
AddrFormatError: invalid IPNetwork 1334420292643450700532337556609564672
-----Original Message-----
From: FUJITA Tomonori [mailto:[email protected]]
Sent: Wednesday, February 19, 2014 3:18 AM
To: Morgan Yang
Cc: [email protected]
Subject: Re: [Ryu-devel] to_match_ip() vs to_match_ipv6 in /ryu/lib/ofct_v1_3.py
On Wed, 19 Feb 2014 03:09:52 +0000
Morgan Yang <[email protected]> wrote:
> Is there a reason why the "to_match_ip" uses the socket library and
> the "to_match_ipv6" uses the netaddr library? That's ok but the
I guess that we did not use netaddr long ago (so socket is used) but at some
point, we started to use netaddr everywhere.
------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk
_______________________________________________
Ryu-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ryu-devel
