= Сообщение: 2142 из 7440 ============================================= IPV6 = От : Nicholas Boel 1:154/10 16 Feb 16 16:47:39 Кому : Andrew Leary 16 Feb 16 16:47:39 Тема : Re: Bill not answering on IPv6 for several weeks now? FGHI : area://IPV6?msgid=1:154/10+56c3a7af На : area://IPV6?msgid=1:320/219@fidonet+56c2e792 = Кодировка сообщения определена как: UTF-8 ================================== Ответ: area://IPV6?msgid=1:229/452.1+6c4608b2 ============================================================================== Hello Andrew,
On 16 Feb 16 04:04, Andrew Leary wrote to Bill McGarrity:
AL> I've noticed that Comcast tends to change their IPv6 assignments AL> occasionally for no apparent reason. When I notice connects falling AL> back to IPv4, I have to log into my Linux box, use ifconfig to AL> determine the newly assigned IPv6 /64 prefix, adjust my "static" IPv6 AL> address accordingly, and update the AAAA record to re-enable full AL> inbound IPv6 connectivity. It wouldn't surprise me if this was done AL> by Comcast to discourage the use of server applications on their AL> residential service. However, it doesn't happen very often, so I can AL> live with it.
I suppose this would be a question for both you and Bill.. but, were you ever emailed by Comcast to specifically let you know that IPv6 support was in full swing?
I understand you have native IPv6, but they could very well still be in testing phases. My ISP (Time Warner Cable.. which, aren't they owned by Comcast now?) specifically told me that IPv6 was in development, would go up and down and change for many reasons, and they still don't fully support it until they actually send out the mass email stating so.
I'm pretty sure I have native IPv6 here, but it's unstable, or at the very least, nowhere near as stable as my he.net tunnel. So I'll stick with that for now.
