>> 	I believe u_int32_t is much more correct here.  there's no particular
>> 	relationship between in_addr_t and IPv6 address.
>> 	please backout the change.
>the problem is that u_int32_t isn't portable (i.e, not every platform
>has it), and it's only used in one place in the code (in one section of
>your ipv6 mods). is there a more portable method of what you were
>trying to do?

	hmm, in that case, I can think of two ways:
	- if u_int32_t is not available, use configure.in to #define u_int32_t
	  into 32bit unsigned integer type.
	- don't try to pack 4 bytes together.  do it in per-byte manner.
	the latter one looks much easier, and much more safe.

itojun