anderstrier

4 ms·

1.
by anderstrier 5y ago
> In other words: The current IPv6 specifications don't allow public IPv6 addresses to send packets to public IPv4 addresses. They also don't allow public IPv4 addresses to send packets to public IPv6 addresses. Public IPv6 add
2.
by anderstrier 6y ago
Thanks! I guess I should keep blogging then :)
3.
by anderstrier 6y ago
I remember being able to overwhelm my first "home router" with the "Browse for servers" tab in Counter Strike 1.6! It would fetch a list of all servers from Steam, and then connect to them individually, eventually killin
4.
by anderstrier 6y ago
Consider sending Aussie Broadband a link to my blog post. It should be a simple fix for them to raise the timeout, which should fix the problem for all their customers.
5.
by anderstrier 6y ago
They will increase their "TCP established connection idle-timeout" from 1 hour to 2 hours and 4 minutes as I requested. This shouldn't make much difference for them. Most connections are closed within a few seconds anyways. L
6.
by anderstrier 6y ago
Please read the post. My ISP already confirmed the problem, and told me that they expect to roll out a fix this week. I live in Denmark, and here it is fairly common that ISPs do Carrier-grade NAT.
7.
by anderstrier 6y ago
I describe those workarounds in my post as well. But that only solves the problem for me. Making my ISP fix the underlying issue - that their TCP connection idle-timeout is too short - will make sure all their customers won't have to e
8.
My ISP Is Killing My Idle SSH Sessions(anderstrier.dk)
403 points by anderstrier 6y ago|240 comments
9.
Using an iPod with a damaged hard drive(anderstrier.dk)
2 points by anderstrier 6y ago|0 comments
10.
by anderstrier 10y ago
Symptoms: apt-get update hangs, and the appstreamcli process is using 100% CPU. Fix described here: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/157...
11.
Ubuntu LTS updating failing all over the world(bugs.launchpad.net)
30 points by anderstrier 10y ago|25 comments