<html><head><style type="text/css">body,p,td,div,span{font-size:13px; font-family:Arial, Helvetica, sans-serif;};body{border: 0; margin: 0; padding: {0}px; height: {1}px; cursor: text}body p{margin:0px;}</style></head><body>I would agree that we need some sort of IPv6 functionality. IPv6 is coming whether we like it or not, so it would be a good idea to have the BlueOnyx system capable of supporting IPv6. (Which it can already, I see that, but I don't want to see the functionality completely removed.) While I know it will take time to work the IPv6 config into the GUI, I'd like to see it there one day. I will make life easier on those who don't fully grasp IPv6, or the manual configuration of it via command line.<br><br><div id="EmailSignature">------------------------------<br>
Don Teague<br>
www.donteague.com</div><br><br><br>At Monday, 2012-09-24 on 22:34 Chris Gebhardt - VIRTBIZ Internet wrote:<br><blockquote style="border:0;border-left: 2px solid #22437f; padding:0px; margin:0px; padding-left:5px; margin-left: 5px; ">Michael Stauber wrote:<br>
> Hi all,<br>
> <br>
> Ok, this is indeed something funny and needs to be looked at.<br>
> <br>
> I tried to make sense about the suggestions as to what needs fixed where<br>
> to disable IPv6 entirely.<br>
<br>
If it may please the court, may I submit we have IPv6 disabled by <br>
default, but not completely removed... just in case we might like to <br>
make some manual entries so that we could use IPv6 if desired?<br>
<br>
We're actually doing this "on purpose" on a couple of boxes, and I have <br>
another couple of customers who are also experimenting.<br>
<br>
> Can someone please summarize this again for me in one message? Thanks!<br>
<br>
Sure thing. One of my hosting boxes "magically" grabbed an IPv6 address <br>
using auto discover. Sendmail attached to the IPv6 IP. Our nameservers <br>
are all IPv6-enabled. This hosting box happened to look up the <br>
mailserver for comcast.net:<br>
<br>
mx1.comcast.net. 300 IN A 68.87.26.147<br>
mx1.comcast.net. 48 IN AAAA 2001:558:fe14:70::22<br>
mx2.comcast.net. 300 IN A 76.96.40.147<br>
mx2.comcast.net. 7200 IN AAAA 2001:558:fe2d:70::22<br>
dns101.comcast.net. 292 IN A 68.87.29.164<br>
dns101.comcast.net. 292 IN AAAA 2001:558:1002:a:68:87:29:164<br>
dns102.comcast.net. 3560 IN A 68.87.85.132<br>
dns102.comcast.net. 3560 IN AAAA 2001:558:1004:7:68:87:85:132<br>
dns103.comcast.net. 3560 IN A 68.87.76.228<br>
dns103.comcast.net. 3560 IN AAAA 2001:558:1014:c:68:87:76:228<br>
dns104.comcast.net. 3560 IN A 68.87.68.244<br>
dns104.comcast.net. 3560 IN AAAA 2001:558:100a:5:68:87:68:244<br>
dns105.comcast.net. 3560 IN A 68.87.72.244<br>
dns105.comcast.net. 3560 IN AAAA 2001:558:100e:5:68:87:72:244<br>
<br>
<br>
The box used one of the IPv6 records to connect to comcast.net. The <br>
only problem here was that we did not have a proper PTR on the IPv6 <br>
address. We rectified that in all of about 2 minutes after noticing the <br>
issue, and mail went through just fine.<br>
<br>
So I suppose the issue is that for most production cases, it would be <br>
best to have IPv6 disabled.<br>
<br>
We happen to be making an aggressive IPv6 push, so I'm not going to be <br>
one of the folks who says just eliminate all IPv6. But I do agree that <br>
in most cases it would be best if left disabled by default.<br>
<br>
This should be as simple as adding this to ifcfg-eth0:<br>
IPV6_AUTOCONF=no<br>
<br>
-- <br>
Chris Gebhardt<br>
VIRTBIZ Internet Services<br>
Access, Web Hosting, Colocation, Dedicated<br>
www.virtbiz.com | toll-free (866) 4 VIRTBIZ<br>
_______________________________________________<br>
Blueonyx mailing list<br>
<a class="normal-link" href="mailto:Blueonyx@mail.blueonyx.it">Blueonyx@mail.blueonyx.it</a><br>
<a href="http://mail.blueonyx.it/mailman/listinfo/blueonyx" target="_blank" class="normal-link">http://mail.blueonyx.it/mailman/listinfo/blueonyx</a></blockquote></body></html>