Exec summary: I have no clue what is going on here.
The java code generated by yangtools looks correct. However it accepts input which should definitely fail (as in the openflow example).
The regexps are correct. If I cut-n-paste them into the following perl snippet they work:
#!/usr/bin/perl
@z = ("^((:|[0-9a-fA-F]
{0,4})
([0-9a-fA-F]{0,4}
((([0-9a-fA-F]
{0,4}?(:|[0-9a-fA-F]{0,4}
))|(((25[0-5]|2[0-4][0-9]|[01]?[0-9]?[0-9])
.)
(25[0-5]|2[0-4][0-9]|[01]?[0-9]?[0-9])))(/(([0-9])|([0-9]
{2})|(1[0-1][0-9])|(12[0-8])))\$", "^(([^:]+
(([^:]:[^:])|(.
..)))|((([^:][^:])?:
([^:][^:])?)(/.+)\$");
while ($a = <STDIN>) {
chomp($a);
foreach $regexp (@z) {
if ($a =~ /$regexp/)
else
{ print "NOK for $regexp\n"; } }
}
Unless there is something in the yang generated code which I have missed, this looks like a bug in the underlying regexp library.
Awaiting down stream projects to update their code.
To remain open until new IPv6Builder() is used.
Projects Still failing:
Openflow
OVSDB
GBP
Hi Carol,
What exactly are the changes that down stream project need to do?
Thanks
Anil
Anil, you need to replace any instantiation of IpvXPrefix (mostly found in Matchers) which is being done without a netmask with a correct argument - with netmask.
The easiest way is utility class with multiple createPrefix() methods:
Ipv6Prefix createPrefix(string);
Ipv6Prefix createPrefix(string, integer);
Ipv6Prefix createPrefix(Ipv6Address);
Ipv6Prefix createPrefix(Ipv6Address, integer);
Ipv4Prefix createPrefix(string);
Ipv4Prefix createPrefix(string, integer);
Ipv4Prefix createPrefix(Ipv4Address);
Ipv4Prefix createPrefix(Ipv4Address, integer);
You just drop that in instead of the direct new IpvXPrefix() instantiation across the board. It will take whatever argument you are feeding it and consume it.
I ended up adding temprorarily (string, string) for openflowplugin, but IMHO that is temporary, the mask has no need of being a string in a network application. Ever.
The easiest way to get that done would have been to override the yangtools generation if we had that facility. As we do not have it, you have to do it manually.