I’ve been losing my mind for almost 4 hours, and I feel like an idiot.
-
I’ve been losing my mind for almost 4 hours, and I feel like an idiot.
At first I couldn't understand why the TLS handshake was always taking more than 300 milliseconds. I thought it was a local or server-side issue. Only after about an hour did I test google.com and saw the exact same behavior.
That's when I realized that with my other WAN connection, the timing drops significantly.
So I started going crazy over my MikroTik configuration, convinced it had to be something related to multi-WAN. I even briefly asked an AI (I know, I know...), which said the problem was probably my neighbor, who had eaten too much pizza.
At that point, I kept spiraling.
Then it hit me that the Vodafone Station has its built-in Wi-Fi disabled, since I manage the network behind it. I could enable it and bypass the MikroTik. I enabled it and ran a direct test.
Bingo. Same problem.
So the issue is upstream. I suspect it’s "Vodafone Rete Sicura", some awful thing I never wanted and that probably does some kind of traffic inspection.
I really can't wait for FTTH to arrive so I can finally get rid of this stuff.
-
I’ve been losing my mind for almost 4 hours, and I feel like an idiot.
At first I couldn't understand why the TLS handshake was always taking more than 300 milliseconds. I thought it was a local or server-side issue. Only after about an hour did I test google.com and saw the exact same behavior.
That's when I realized that with my other WAN connection, the timing drops significantly.
So I started going crazy over my MikroTik configuration, convinced it had to be something related to multi-WAN. I even briefly asked an AI (I know, I know...), which said the problem was probably my neighbor, who had eaten too much pizza.
At that point, I kept spiraling.
Then it hit me that the Vodafone Station has its built-in Wi-Fi disabled, since I manage the network behind it. I could enable it and bypass the MikroTik. I enabled it and ran a direct test.
Bingo. Same problem.
So the issue is upstream. I suspect it’s "Vodafone Rete Sicura", some awful thing I never wanted and that probably does some kind of traffic inspection.
I really can't wait for FTTH to arrive so I can finally get rid of this stuff.
@stefano Disgusting! Today it's a luxury to have a real and untempered internet connection. About 16 years ago I saw Vodafone compressing my images which I uploaded to an FTP server. It's just stupid...
-
@stefano Disgusting! Today it's a luxury to have a real and untempered internet connection. About 16 years ago I saw Vodafone compressing my images which I uploaded to an FTP server. It's just stupid...
@finn I agree. I don't need Vodafone to sniff my traffic and decide if it's "secure" or not. Years ago that service wasn't Active by default. Then something changed and I started to see, from time to time, those "this site isn't secure" pages. I asked to disable it and they did it. But I remember that I read somewhere they're reenabling it and now it cannot be disabled as "it's for our security".
All I ask is that they stop messing with my traffic.
-
undefined stefano@mastodon.bsd.cafe shared this topic
-
@finn I agree. I don't need Vodafone to sniff my traffic and decide if it's "secure" or not. Years ago that service wasn't Active by default. Then something changed and I started to see, from time to time, those "this site isn't secure" pages. I asked to disable it and they did it. But I remember that I read somewhere they're reenabling it and now it cannot be disabled as "it's for our security".
All I ask is that they stop messing with my traffic.
@stefano Amen brother! Just give us pure unfiltered internet. If someone wants any "security extras" they can opt-in for that.
-
I’ve been losing my mind for almost 4 hours, and I feel like an idiot.
At first I couldn't understand why the TLS handshake was always taking more than 300 milliseconds. I thought it was a local or server-side issue. Only after about an hour did I test google.com and saw the exact same behavior.
That's when I realized that with my other WAN connection, the timing drops significantly.
So I started going crazy over my MikroTik configuration, convinced it had to be something related to multi-WAN. I even briefly asked an AI (I know, I know...), which said the problem was probably my neighbor, who had eaten too much pizza.
At that point, I kept spiraling.
Then it hit me that the Vodafone Station has its built-in Wi-Fi disabled, since I manage the network behind it. I could enable it and bypass the MikroTik. I enabled it and ran a direct test.
Bingo. Same problem.
So the issue is upstream. I suspect it’s "Vodafone Rete Sicura", some awful thing I never wanted and that probably does some kind of traffic inspection.
I really can't wait for FTTH to arrive so I can finally get rid of this stuff.
> I even briefly asked an AI (I know, I know...)
LLMs being used as a search engine "on steroids" is actually a good use case, IMHO.
You don't have to blindly trust the output, but instead have something to keep searching for an answer.
-
I’ve been losing my mind for almost 4 hours, and I feel like an idiot.
At first I couldn't understand why the TLS handshake was always taking more than 300 milliseconds. I thought it was a local or server-side issue. Only after about an hour did I test google.com and saw the exact same behavior.
That's when I realized that with my other WAN connection, the timing drops significantly.
So I started going crazy over my MikroTik configuration, convinced it had to be something related to multi-WAN. I even briefly asked an AI (I know, I know...), which said the problem was probably my neighbor, who had eaten too much pizza.
At that point, I kept spiraling.
Then it hit me that the Vodafone Station has its built-in Wi-Fi disabled, since I manage the network behind it. I could enable it and bypass the MikroTik. I enabled it and ran a direct test.
Bingo. Same problem.
So the issue is upstream. I suspect it’s "Vodafone Rete Sicura", some awful thing I never wanted and that probably does some kind of traffic inspection.
I really can't wait for FTTH to arrive so I can finally get rid of this stuff.
@stefano residential line ?
Here in Belgium they filter out the ports 80/443 by default: "security measure".
> I even briefly asked an AI (I know, I know...),
to realize that it doesn't help. :)