Anyway, this year we even omitted that tree, so I didn’t have to bother with that.
Specifically today? It’s 2AM, not much went on, just doing my things, thankfully nothing related to Christmas.
I sent my cash too late so I ran out of Mullvad time. I paid for a week of IVPN and the setup didn’t fair too well.
“Bypass VPN for local networks” in their app on Android doesn’t work, so I lost ability to use KDE Connect for now.
On laptop I just used plain WG with NetworkManager on Plasma. It seems to not accept anything but 0.0.0.0/0 in AllowedIPs which is something I’ve been screwing around with for a while until I found someone else from a year ago with the same issue. I even tried 0.0.0.0/1, 128.0.0.0/1 rather than the larger calculated list, bug to no avail. It just doesn’t work.
I guess I’ll just use OpenVPN on Android. The second doesn’t seem to matter much.
I am also trying to figure out whether what I’ve found is infinite unthrottled (almost) free mobile data glitch with T-Mobile, or some kind of sorcery I missed in their documentation.
Sort of, but in a bad way.
Anyway, this year we even omitted that tree, so I didn’t have to bother with that.
Specifically today? It’s 2AM, not much went on, just doing my things, thankfully nothing related to Christmas.
I sent my cash too late so I ran out of Mullvad time. I paid for a week of IVPN and the setup didn’t fair too well.
“Bypass VPN for local networks” in their app on Android doesn’t work, so I lost ability to use KDE Connect for now.
On laptop I just used plain WG with NetworkManager on Plasma. It seems to not accept anything but
0.0.0.0/0in AllowedIPs which is something I’ve been screwing around with for a while until I found someone else from a year ago with the same issue. I even tried0.0.0.0/1, 128.0.0.0/1rather than the larger calculated list, bug to no avail. It just doesn’t work.I guess I’ll just use OpenVPN on Android. The second doesn’t seem to matter much.
I am also trying to figure out whether what I’ve found is infinite unthrottled (almost) free mobile data glitch with T-Mobile, or some kind of sorcery I missed in their documentation.
Someone hit the spiked eggnog a bit too hard.