BM> It's fixed.... For some reason Comcast changed my IP and I had to BM> update my BM> AAAA.
I've noticed that Comcast tends to change their IPv6 assignments occasionally for no apparent reason. When I notice connects falling back to IPv4, I have to log into my Linux box, use ifconfig to determine the newly assigned IPv6 /64 prefix, adjust my "static" IPv6 address accordingly, and update the AAAA record to re-enable full inbound IPv6 connectivity. It wouldn't surprise me if this was done by Comcast to discourage the use of server applications on their residential service. However, it doesn't happen very often, so I can live with it.
