June 2006 - ipv6calc - lists.deepspace6.net

eui64_to_privacy broken for big-endian architectures
by Niko Tyni 10 Jul '06

10 Jul '06

Hi Peter and other ipv6calc list members, it looks like the ipv6calc RFC3041 (privacy extensions) code is broken on big-endian systems. The Debian automatic build daemon logs indicate that the test '--eui64_to_privacy' is failing on these architectures: s390 mips sparc hppa m68k It's working on these: arm alpha powerpc mipsel ia64 amd64 i386 AFAIK, this looks like a list of big-endian vs. little-endian systems. In particular, mipsel is just the same as mips but little-endian. The result on the failed ones is: Test './ipv6calc --eui64_to_privacy 0123:4567:89ab:cdef 0123456789abcdef' for '4662:bdea:8654:776d 486072ff7074945e' Result '96de:eee5:308c:8ea7 df277f120cf06be3' doesn't match! The full build logs can be found at http://buildd.debian.org/build.php?arch=&pkg=ipv6calc I haven't investigated this much yet. I can get my hands on a sparc machine probably tomorrow, so I'm well positioned to test this. I'll get back to this when I have a patch. The problem has been there at least since 0.45, so it's not a new regression. It just wasn't noticed earlier. I'm CCing 375855-forwarded(a)bugs.debian.org - please keep the CC when responding so the information in the Debian bug database stays up to date. Cheers, -- Niko Tyni ntyni(a)iki.fi

2 9

New version 0.60.0 released
by Peter Bieringer 25 Jun '06

25 Jun '06

Hi, I've released version 0.60.0 now. Available at: ftp://ftp.bieringer.de/pub/linux/IPv6/ipv6calc/ (and via CVS - note that DS6 currently contains only older versions). See here for the full change log: http://cvs.deepspace6.net/view/ipv6calc/ChangeLog Major changes: - support of IP2Location databases (currently only for IPv4, the API still miss IPv6 support). If a new API is available, I will include it Can be enabled by compile time ./configure --enable-ip2location or rpm --with ip2location - new base85 implementation by Niko Tyni - Machine readable output of ipv6calc is now capable of proper printout of (more than one) embedded IPv4 addresses (ipv6calcweb.cgi is adjusted, also) For packet managers, please push new release to repositories. Peter -- Dr. Peter Bieringer http://www.bieringer.de/pb/ GPG/PGP Key 0x958F422D mailto:pb@bieringer.de Deep Space 6 Co-Founder and Core Member http://www.deepspace6.net/

1 0

Test
by Peter Bieringer 23 Jun '06

23 Jun '06

Sorry, only a test. Peter -- Dr. Peter Bieringer http://www.bieringer.de/pb/ GPG/PGP Key 0x958F422D mailto:pb@bieringer.de Deep Space 6 Co-Founder and Core Member http://www.deepspace6.net/

1 0

ipv6calc version 0.60.0beta1 available
by Peter Bieringer 22 Jun '06

22 Jun '06

Hi, after some rapid development a new version is on the way to be released. See here for the full change log: http://cvs.deepspace6.net/view/ipv6calc/ChangeLog Please test heavily. I plan to release final version in one or two weeks or so. Miror feature requests are still accepted. Major changes in user/machine interface - Machine readable output is now capable of proper printout of (more than one) embedded IPv4 addresses (ipv6calcweb.cgi is adjusted, also) Example: $ ./ipv6calc/ipv6calc -p databases/IP2Location/IPV6-COUNTRY.BIN -m -i 2001:0000:0102:0304:0000:1234:0506:0708 IPV6=2001:0000:0102:0304:0000:1234:0506:0708 TYPE=unicast,global-unicast,productive,teredo IPV4_SOURCE[250.249.248.247]=TEREDO-SERVER IPV4[250.249.248.247]=250.249.248.247 IPV4_REGISTRY[250.249.248.247]=IANA IPV4_SOURCE[1.2.3.4]=TEREDO-CLIENT IPV4[1.2.3.4]=1.2.3.4 IPV4_REGISTRY[1.2.3.4]=IANA TEREDO_PORT_CLIENT=60875 IPV6_REGISTRY=IANA IPV6CALC_NAME=ipv6calc IPV6CALC_VERSION=0.60.0beta1 IPV6CALC_COPYRIGHT="(P) & (C) 2001-2006 by Peter Bieringer <pb (at) bieringer.de>" IPV6CALC_OUTPUT_VERSION=2 <- introduced as "API" version to ipv6webcalc.cgi Major feature extensions: - IP2Location support (for IPv4) Can be enabled by compile time ./configure --enable-ip2location or rpm --with ip2location If enabled, but no database is given, support will be silently skipped Peter -- Dr. Peter Bieringer http://www.bieringer.de/pb/ GPG/PGP Key 0x958F422D mailto:pb@bieringer.de Deep Space 6 Co-Founder and Core Member http://www.deepspace6.net/

1 1

Re: [ipv6calc] Re: ipv6calc: new base85 implementation
by Peter Bieringer 12 Jun '06

12 Jun '06

Niko Tyni schrieb: > On Mon, Jun 12, 2006 at 10:16:39AM +0200, Peter Bieringer wrote: > >>> It looks good to me, FWIW. The only thing missing I can see is documenting >>> the "-p" ip2location option in lib/ipv6calchelp.c >> Thanks, implemented in local source. > > Oops, almost forgot: there's a small problem with hyphens in the ipv6logconv > manpage. Patch attached. Thank you, applied to CVS. Regards, Peter -- Dr. Peter Bieringer http://www.bieringer.de/pb/ GPG/PGP Key 0x958F422D mailto:pb@bieringer.de Deep Space 6 Co-Founder and Core Member http://www.deepspace6.net/

1 0

Re: ipv6calc: new base85 implementation
by Peter Bieringer 11 Jun '06

11 Jun '06

Niko Tyni schrieb: > On Wed, Jun 07, 2006 at 03:47:54PM +0200, Peter Bieringer wrote: > >> BTW: switch in Makefile.in currently doesn't work for ipv6calc binary >> itself, I have troubles to inherit the information from main Makefile to >> ipv6calc/Makefile (perhaps one can lead me to proper implementation). > > I'm not an autoconf guru, but I think an AC_ARG_ENABLE macro is the > cleanest solution. A quick patch based on that is at > > http://www.helsinki.fi/~ntyni/ipv6calc/ip2location.patch > > It seems to work for me. I have no idea how specific to GNU make the > 'ifeq' and the ':=' (needed for recursive expansion) constructs are, > though. I thought already about the same, thank you very much for your patch! BTW: I've fixed some build options bugs also, now it should be working fine. spec file for RPM was also updated to understand "--with ip2location" Here is a example about the output: $ ./ipv6calc/ipv6calc -p databases/IP2Location/C-IP2Location-1.1.0/data/IP-COUNTRY-SAMPLE.BIN -q -m -i 66.1.2.3 IPV4=66.1.2.3 IPV4_REGISTRY=ARIN IP2LOCATION_COUNTRY_SHORT=US IP2LOCATION_COUNTRY_LONG=UNITED STATES IP2LOCATION_REGION=This parameter is unavailable for selected data file. Please upgrade the data file. IP2LOCATION_CITY=This parameter is unavailable for selected data file. Please upgrade the data file. IP2LOCATION_ISP=This parameter is unavailable for selected data file. Please upgrade the data file. IP2LOCATION_LATITUDE=0.000000 IP2LOCATION_LONGITUDE=0.000000 IP2LOCATION_DOMAIN=This parameter is unavailable for selected data file. Please upgrade the data file. IP2LOCATION_ZIPCODE=This parameter is unavailable for selected data file. Please upgrade the data file. IPV6CALC_NAME=ipv6calc IPV6CALC_VERSION=0.52cvs IPV6CALC_COPYRIGHT="(P) & (C) 2001-2006 by Peter Bieringer <pb (at) bieringer.de>" So now it's on IP2Location side to provide an update for the C-API supporting IPv6. Peter -- Dr. Peter Bieringer http://www.bieringer.de/pb/ GPG/PGP Key 0x958F422D mailto:pb@bieringer.de Deep Space 6 Co-Founder and Core Member http://www.deepspace6.net/

2 1

Re: ipv6calc: new base85 implementation
by Peter Bieringer 07 Jun '06

07 Jun '06

Hi Niko, Niko Tyni schrieb: > On Wed, Jun 07, 2006 at 08:35:26AM +0200, Peter Bieringer wrote: > >> Changes / replacement committed to CVS. Please give a try. > > Splendid :) > > The current CVS code doesn't compile, though. It looks like it's missing > the "IP2Location.h" header file. Fixed in CVS by extending the Makefile(.in) to make IP2Location support optionally. Also committed IP2Location C-API 1.1.0 to CVS. BTW: switch in Makefile.in currently doesn't work for ipv6calc binary itself, I have troubles to inherit the information from main Makefile to ipv6calc/Makefile (perhaps one can lead me to proper implementation). >> BTW: what do you mean with "past md5/OpenSSL change"? Did I miss something? > > Sorry for being unclear. I just meant that since ipv6calc is nowadays > using a builtin md5 implementation, That's right. > the OpenSSL linking exception in > LICENSE isn't needed anymore. And I suppose that technically you need > an exception statement from all the copyright holders of the GPL code > included, but that's kind of nitpicking of course. > > In any case, the parenthesized statement in > > 2. I allow to link OpenSSL library used by SSLeay license > (md5 hash function is used from this libary) > > isn't true anymore, as far as I understand. Removed, thank you for clarification. Regards, Peter -- Dr. Peter Bieringer http://www.bieringer.de/pb/ GPG/PGP Key 0x958F422D mailto:pb@bieringer.de Deep Space 6 Co-Founder and Core Member http://www.deepspace6.net/ OpenBC http://www.openbc.com/hp/Peter_Bieringer/ Personal invitation to OpenBC http://www.openbc.com/go/invita/3889

1 0

IP2Location support added to ipv6calc
by Peter Bieringer 07 Jun '06

07 Jun '06

Hi, in March I've implemented IP2Location support to ipv6calc. See here for more information: http://www.ip2location.com In March 2006, the support of IPv6 was still missing in C API. Unfortunately, last status I get some days ago has't changed, they are out of manpower and missing demand to implement it soon. Anyway, I committed the changes now to CVS, for IPv4, IP2Location support is already working. Here the changelog since the last release (0.51): 20060607/PB lib/librfc1924.c - replace conversion code with clean reimplementation created by Niko Tyni because of unknown license issue of the old piece of code update databases 20060317/PB databases/ipv6-assignment/create-registry-list.pl databases/ipv4-assignment/create-registry-list.pl databases/ipv6-assignment/dbipv6addr_assignment.h databases/ipv4-assignment/dbipv4addr_assignment.h lib/libipv6addr.h lib/libipv4addr.h - store also prefix length in lookup table update databases 20060316/PB lib/libipv4addr.c - fix wrong use of () in ipv4addr_setword 20060306/PB Makefile.in ipv6calc/Makefile.in ipv6calc/ipv6calc.c ipv6calc/showinfo.c - add support for IP2Location lib/ipv6calcoptions.h - add new option: -p <path to IP2Location database> 20060213/PB ipv6calc/Makefile.in - replace "make" by "${MAKE}" (forgotten in 20051119) Please try it. Peter -- Dr. Peter Bieringer http://www.bieringer.de/pb/ GPG/PGP Key 0x958F422D mailto:pb@bieringer.de Deep Space 6 Co-Founder and Core Member http://www.deepspace6.net/

1 0

Re: ipv6calc: new base85 implementation
by Peter Bieringer 07 Jun '06

07 Jun '06

Hi Niko, Niko Tyni schrieb: > Hello Dr. Bieringer, > > my name is Niko Tyni, and I'm planning to take over the maintenance of > the Debian ipv6calc package, as Masamichi Goudge unfortunately doesn't > have the time for that anymore. > > First, I'd like to thank you for the nice tool you have created. It > has been quite helpful to me in my work as a network engineer and > I appreciate the amount of work you have put into it. > > While looking through the code, I noticed that while the licenses and the > copyrights of the various pieces of code that come from other sources are > excellently documented in general, there seems to be no information on > the license of the RFC 1924 (base85 conversion) code in lib/librfc1924.c. This is indeed right, I didn't find any information. > I'm aware that the RFC is mostly an April 1st joke, and the code that > lib/librfc1924.c is based on, samplecode/rfc1924-encode.c, is probably > part of the joke. Still, I think it would make things cleaner if it was > known without doubt that also this part of the code is free software. For sure, also the old code was't be good enough to check with splint. > To that end, I have rewritten the base85 implementation so that there is > nothing left of the original code from rfc1924-encode.c. This new code is > naturally under the GNU General Public License (version 2, as all ipv6calc > code.) Moreover, it is clearer (at least IMO :), 40 % shorter and about > 400 times faster on my 32-bit hardware than the current implementation. Thank you very much! > You can find my implementation and the test code I used for the > measurements at > > http://www.helsinki.fi/~ntyni/ipv6calc/ > > Please consider replacing the current RFC 1924 implementation with this > in a future release of ipv6calc. > > (If you do this, please also consider removing the file > samplecode/rfc1924-encode.c from the ipv6calc distribution, as it > is in principle unknown whether anyone is allowed distribute it even > unmodified. Also, it would be good to update the LICENSE file to reflect > both this and possibly the past md5/OpenSSL change.) Changes / replacement committed to CVS. Please give a try. BTW: what do you mean with "past md5/OpenSSL change"? Did I miss something? Peter -- Dr. Peter Bieringer http://www.bieringer.de/pb/ GPG/PGP Key 0x958F422D mailto:pb@bieringer.de Deep Space 6 Co-Founder and Core Member http://www.deepspace6.net/

1 0