Is this purely AI generated world better or worse than what we had 5 years ago?
------------------------------------------
https://growmane.blogspot.com/2023/09/acquaintances-seem-to-have-much-shorter.html
2 years after the last great Comca$t battle, seemingly to the day, the
connection was disabled at 2am one monday night & the lion kingdom was
back in walled garden mode.
What previously worked: the outage map, waiting a while, restarting the
gateway, restarting the router, deleting dhcp cache, no longer worked.
It seems the worry free plan of a lifetime had just 2 years in it.
Despite the overwhelming incompetance in the organization, they might
carefully audit all the accounts. There were hopes the plan would last
until retirement. Then lions would be excused from dealing with Comca$t
for the rest of their natural lives.
Phone tethering as a backup didn't go so well anymore. Either the 5G
network or 2.4Ghz might be saturated during the day. Phone to phone
tethering was solid but Linux failed constantly. After a certain time
limit, linux could no longer ping the phone & the connection stalled.
The 1st problem was Boost joining the club of requiring a fee to use
tethering. They don't sniff the TTL but route through a separately paid
rmnet device.
Ping outside the phone & masquerading from linux didn't work anymore.
They might be using TTL to disable masquerading. Pinging anywhere from
the phone worked. Drop kicking wifi on Linux seemed to get it to go a
while longer. Uninstalling & reinstalling the kernal modules got it to
go.
Suspect writing a packet mangling program to bypass tethering would not
be trivial but might be essential. Wifi for user programs has always
been throttled, but it might also be the reason tethering is so bad in
Linux. All the linux boxes have crummy wifi drivers, with really shit
power management. All the USB dongles are 2.4Ghz only. They might be
running into power management bugs. Pinging the phone might keep it
alive longer, but nowhere near what it was.
It's been hard to find motivation to work on tethering since the
commutes ended. That was the mane thing keeping lions current on it.
Lions used the hell out of it, back in the day, but wifi on mac was a
lot better too.
A new wrinkle is the need to bridge wifi & lan for containers. The lan
device more likely has to be taken off the bridge when using tethering,
since its only purpose is the internet.
If only lions were back in their dorm with just the lone $25 D-link &
university T1. It had problems, but those days were just a lot more
productive & simpler. Every battle was a forward move instead of a
sideways move.
Finally checking on the account page revealed nothing useful. Trying to
change plans led to the dreaded "Xfinity service is included at your
address" meaning there was no way to change anything without sending out
a truck. The next idea was trying Comca$t public wifi. It was a real hail mary, since lions didn't think their plan had it.
Accessing that from linux requires
iwconfig wlan0 essid "xfinitywifi"
dhclient -v wlan0
Then you have to load any page in a browser & sign in on the login.
wpa_supplicant & drivers with broken wireless extensions don't work.
The only drivers with wireless extensions are the raspberry pi's.
Despite the gateway being stuck in walled garden mode, the public wifi
worked. So the piano became the new router. The raspberry pi's are on
5Gghz.
The latency is longer on wifi. It seems a lot of programs use IPv6 &
that is now broken. Gootube downloader doesn't work over xfinitywifi.
Shocking how much doesn't work, since most animals only use wifi.
It seems the MTUs have to be reduced for VPNs to work. The symptom is
ICMP working but https not.
Container configs need
lxc.network.0.mtu = 1420
Helas, this changes the bridge on the host.
Openconnect needs --mtu=1420 --base-mtu=1420 to shrink it to at least
1350. The required values for openconnect vary by installation.
Actually managed to get yt-dlp to work with the bridge MTU 1420 & enp6s0
MTU 1500.
Comments
Post a Comment