<div dir="ltr">On Wed, Aug 27, 2008 at 9:50 PM, Robert Moskowitz <span dir="ltr"><<a href="mailto:rgm@htt-consult.com">rgm@htt-consult.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
<br>
Rob Townley wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Wed, Aug 27, 2008 at 8:24 AM, Robert Moskowitz <<a href="mailto:rgm@htt-consult.com" target="_blank">rgm@htt-consult.com</a> <mailto:<a href="mailto:rgm@htt-consult.com" target="_blank">rgm@htt-consult.com</a>>> wrote:<br>
<br>
Um, as the original poster, I WANT IPv6. Not make IPv4 lookups<br>
faster by ignoring AAAA records.<br>
<br>
Further testing has IPv6 working just fine. Thing is when I<br>
enable the HIP API intercepts, FIrefox does not work. Like they<br>
are doing something 'non-standard' with the regualr TCP socket API<br>
so that HIP can't slide in there. I tried disabling a number of<br>
options, thinking it might be some security setting, but if it is,<br>
I have not found it.<br>
<br>
<br>
Yep, i fully understood you wanted IPv6. i just thought you might want to verify what settings you have for Firefox -- making sure Firefox has turned on IPv6 dns.<br>
</blockquote>
Default was on. <br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Just curious, what is the motivation for the HIP api stuff, it is not there by default is it? <br>
</blockquote>
read the RFCs on HIP: 4423 and 5201-5206.<br>
<br>
4423 provides the justification of HIP and its architecture. I created HIP almost 10 years ago, shortly after (as IPsec co-chair) got the IPsec RFCs out. HIP is much more than an alternative keying protocol for ESP (compared to IKE). It directly addresses secure mobility. HIP **IS** an important change to the TCP/IP architecture; this has been part of its slow advancement. As such it has its own 'native' API: <a href="http://www.ietf.org/internet-drafts/draft-ietf-hip-native-api-05.txt" target="_blank">http://www.ietf.org/internet-drafts/draft-ietf-hip-native-api-05.txt</a>.<br>
<br>
I can go into more about HIP if you wish.<br>
<br>
<br>
_______________________________________________<br>
CentOS mailing list<br>
<a href="mailto:CentOS@centos.org" target="_blank">CentOS@centos.org</a><br>
<a href="http://lists.centos.org/mailman/listinfo/centos" target="_blank">http://lists.centos.org/mailman/listinfo/centos</a><br>
</blockquote></div><br><br>So HIP isn't in any distribution by default or is it? How does one know? Would it make sense to include HIP in a Wireless Access Point firmware or a RADIUS type machine? Looks interesting, will have to keep it in mind for wlan sec.<br>
</div>