I plugged into ethernet (as wifi w/captive portal does not work for me). I think clearnet worked but I have no interest in that. Egress Tor traffic was blocked and so was VPN. I’m not interested in editing all my scripts and configs to use clearnet, so the library’s internet is useless to me (unless I bother to try a tor bridge).
I was packing my laptop and a librarian spotted me unplugging my ethernet cable and approached me with big wide open eyes and pannicked angry voice (as if to be addressing a child that did something naughty), and said “you can’t do that!”
I have a lot of reasons for favoring ethernet, like not carrying a mobile phone that can facilitate the SMS verify that the library’s captive portal imposes, not to mention I’m not eager to share my mobile number willy nilly. The reason I actually gave her was that that I run a free software based system and the wifi drivers or firmware are proprietary so my wifi card doesn’t work¹. She was also worried that I was stealing an ethernet cable and I had to explain that I carry an ethernet cable with me, which she struggled to believe for a moment. When I said it didn’t work, she was like “good, I’m not surprised”, or something like that.
¹ In reality, I have whatever proprietary garbage my wifi NIC needs, but have a principled objection to a service financed by public money forcing people to install and execute proprietary non-free software on their own hardware. But there’s little hope for getting through to a librarian in the situation at hand, whereby I might as well have been caught disassembling their PCs.
Even ignoring that, if internet via a wired ethernet connection isn’t an option they provide for whatever reason… their network infrastructure shouldn’t allow the connection anyway. It should be blocked as an unknown device on the network end, regardless if someone plugs into the network.
Yeah, having services blocked on Wi-Fi and not ethernet just tells me that their IT staff didn’t properly configure the network in public areas properly. That ethernet port should have been disabled, physically locked, or properly configured to use the public network like the Wi-Fi does.
Exactly, and let’s give them the benefit of the doubt since we don’t know. The librarian or assistant helping OP probably just doesn’t know much about the IT stuff other than how to help people get on the wifi. And it is entirely possible that they’re NEVER seen anyone even try the port before, that’s not common at all. Actually managing the IT infrastructure at that level is almost surely NOT part of their job.
WiFi has been included in essentially everything for over a decade. I mean even ignoring laptops having Wifi way before mobile devices, even going back to the origin of smartphones for the masses, the original iPhone had Wifi back in 2007, that’s 17 years ago.
Oh I’ve got nothing against how the librarians handled it. I’m more concerned that their IT staff failed to properly shield the library from liabilities like OP.