[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: "DNS-4to6 automatic mapping" - No more DNS-ALGs & 6then4 DNS queries



What box?  There is no box to enable v6 on OpenBSD.  The only place
in OpenBSD that does not have v6 enabled by default is in a few install
media kernels, which do not have space for v6.  The userland ftp utility,
used for retrieving images, fails most gracefully when given a hostname
that has both v4 and v6 addresses, it tries the v6, fails immediately,
and then uses the v4 address.

I guess you have not tried OpenBSD since you seem to think there are
options check boxes that enable/disable v6 entirely during the installation.
-- 
Todd Fries .. todd@fries.net

 _____________________________________________
|                                             \  1.636.410.0632 (voice)
| Free Daemon Consulting, LLC                 \  1.405.227.9094 (voice)
| http://FreeDaemonConsulting.com             \  1.866.792.3418 (FAX)
| "..in support of free software solutions."  \  1.700.227.9094 (IAXTEL)
|                                             \          250797 (FWD)
 \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
                                                 
              37E7 D3EB 74D0 8D66 A68D  B866 0326 204E 3F42 004A
                        http://todd.fries.net/pgp.txt

Penned by Iljitsch van Beijnum on 20071129 14:10.30, we have:
| On 29 nov 2007, at 13:19, Todd T. Fries wrote:
| 
| >The bottom line is that OpenBSD userland unconditionally enables IPv6
| >regardless if the kernel supports it or not.  If there is no v6  
| >default
| >route, v6 fails quickly and seamlessly back to v4 (telnet, ftp, ssh,  
| >etc)
| >and behaves sanely.
| 
| >I do not see why mandating different is productive for a future of v6
| >deployment.
| 
| I for one am glad that my OS of choice is smart enough to avoid this  
| unnecessary extra work. If your users don't mind this "you checked the  
| box during installation so now I'm going to waste time for each DNS  
| lookup even though a quick look at the routing table could avoid that"  
| approach, I agree that the IETF should probably not force you to do  
| things differently.