[Discussion] IPv4 mapped addresses not working properly

[Richard Carlson <rcarlson@xxxxxxxxxxxxx>]

Matt, John, & John;

Drat!  I've been working with the folks from SLAC to get a NDT server 
installed and I finally tracked a down the problem.  They used the new v1.6 
userland library and for some reason I don't understand IPv4 mapped 
addresses are not being handled properly buy the 
web100_connection_find_v6() routine.  I know this is the routine I sent you 
a patch for last month, and that appears to work for real IPv6 addresses, 
but - to my surprise - IPv4 mapped addresses are still failing.

The NDT uses some address routines Jeff Boote wrote to support both IPv4 
and IPv6 networks.  For reasons best know to someone else, these routines 
generate IPv4 mapped addresses if both v4 & v6 networks are supported.  If 
you disable the IPv6 option, then real IPv4 addresses are created.

So by default the NDT will support both IPv4 & IPv6 addresses so I get 
mapped IPv4 addresses.  For reasons I can't explain, these mapped addresses 
are not being handled properly by the find_v6() routine, I think that real 
IPv6 addresses are, but I haven't tested that myself.   In any case I 
applied the mapped IPv4 patch I sent you last month and that forces the 
mapped addresses to be handled by the find_v4() routine.  That make the NDT 
server process work again.

I can send you the patch again, or someone can help me debug this more to 
find out what is going on.

Regards;
Rich


------------------------------------



Richard A. Carlson                              e-mail: RCarlson@xxxxxxxxxxxxx
Network Engineer                                phone:  (734) 352-7043
Internet2                                       fax:    (734) 913-4255
1000 Oakbrook Dr; Suite 300
Ann Arbor,  MI  48104 


_______________________________________________
Discussion mailing list
Discussion@xxxxxxxxxx
http://internal.web100.org/mailman/listinfo/discussion