AL>BM> It's fixed.... For some reason Comcast changed my IP and I had to AL>BM> update my AL>BM> AAAA.
AL> I've noticed that Comcast tends to change their IPv6 assignments AL> occasionally AL> for no apparent reason. When I notice connects falling back to IPv4, I AL> have AL> to log into my Linux box, use ifconfig to determine the newly assigned AL> IPv6 AL> /64 prefix, adjust my "static" IPv6 address accordingly, and update the AL> AAAA AL> record to re-enable full inbound IPv6 connectivity. It wouldn't surprise AL> me AL> if this was done by Comcast to discourage the use of server applications AL> on AL> their residential service. However, it doesn't happen very often, so I AL> can AL> live with it.
I don't pretend to know how things work where you are, but I have a static address, which I pay extra for, and it cannot be changed. On the other hand, and as you probably know, a dynamic address may be changed at any time.
Many of my colleagues and friends tried to convince me that what I have isn't worth it, but to me it is, and after all, it is my money. (-:
Regards,
Roger
--- DB 3.99 + Windows 10 * Origin: NCS BBS (1:3828/7)
