5 ms·
1) When was the last time you fixed networking issues by turning on IPv6? 2) When was the last time you fixed networking issues by turning off IPv6? For me, t
by nikanj 4y ago
1) When was the last time you fixed networking issues by turning on IPv6?
2) When was the last time you fixed networking issues by turning off IPv6?
For me, the answer to 1) remains "never", the answer to 2) is currently "Late winter"
- patrakov 4y ago> 1) When was the last time you fixed networking issues by turning on IPv6? In 2017. The problem was that file copying via scp was very slow between the servers (one in Germany, one in China). I set up a he.net tunnel in China, got an IPv6 address, and it went much faster via IPv6.
- eqvinox 4y ago3) When was the last time you fixed networking issues by turning on IPv4? About a year ago, when I noticed wikipedia still doesn't have IPv6 reachable DNS resolvers. 4) When was the last time you fixed networking issues by turning off IPv4? A few weeks ago, IPv4 was just slow for some reason I couldn't quite determine.
- icedchai 4y agoI've been running IPv6 since roughly 2007, starting with SiXXS tunnels, then HE.net tunnels, then moving to native. In that time, all problems "due to IPv6" were fixable. Turning off IPv6 was never the actual answer.
- magicalhippo 4y agoOf course. But it's quick and almost always works.
- jeroenhd 4y ago1. Yesterday, actually! 2. Never, because altering my network in a way that I'm no longer able to reach my own servers isn't really a "solution".
- toast0 4y ago> 1) When was the last time you fixed networking issues by turning on IPv6? I've used IPv6 to help users behind CGNAT; enabling IPv6 for client -> server often means those clients no longer go through carrier stateful firewalls and their sometimes tragically low idle timeouts (I've seen timeouts as low as 10 seconds). I've also used IPv6 to help in a proxy config when I couldn't get the upstream servers configured for more listening ports; it's super easy to get extra v6 source addresses for the proxy servers and harder to get v4 addresses. With high volumes and low session times, you run into port reuse issues at around 10k-20k sessions per {source ip, dest ip, dest port} tuple; theoretically you can get to 64k, but TIME_WAIT takes time to clear and you don't want to be too aggressive. Probably less going forward, but v6 and v4 often have different routed paths, and sometimes you want to get off of one path and onto another. If you're using a tunneled v6 connection, you almost certainly have a different path for most destinations. > 2) When was the last time you fixed networking issues by turning off IPv6? My previous DSL modem would crash when receiving fragmented IPv6 packets. My current one doesn't crash, but adds a lot of internal latency. Temporarily fixed by disabling IPv6; permanently fixed by using the modem in bridge mode and doing PPPoE on my own personal equipment (at great cost to my own sanity, PPPoE is gross, and I built a multi-node redundancy setup, so PPPoE sessions can be transferred between my redundant routers, bleh)
- lolc 4y agoI frequently "turn on" IPv6 by disconnecting from my company VPN. Some things work better that way.
- doodlesdev 4y ago1) Last week 2) Never
- icehawk 4y ago1) About 12 hours ago, because T-Moble's CGNAT is broken 2) 20 years ago? Late 00's
- justsomehnguy 4y ago1. Multiple times. Idiots love to do meaningless things, so they disable IPv6 without understanding the consequences. I turn it back on and things start to work again.