Sounds interesting. I always wanted to use a Raspberry PI as router (to have one as backup in case the OpenWRT Linksys goes down), but couldn't wrap my head around properly how to overcome the single network port (I think the usual recommendation is to use an extra USB network card/adapter). Can you elaborate more about this VLAN stuff (you would put your modem, your router, and all your machines on the switch... and in the switch you tell the router connection to double use the connection for WAN and LAN separated via VLANs? And put the modem into the "WAN VLAN" too?)
Ideally the PI also should to what the extra DSL Modem does… but I guess that's where the dram must stop. :D
When you setup your single ethernet port (let's call it eth0) as a VLAN trunk port, you'll get the ability to configure multiple virtual interfaces off of it. How many virtual interfaces you get depends on how many VLANs you want to tag traffic for. For example, if you have 2 VLANS with ids 100 and 200 (100 being your public Internet-facing traffic, and 200 being your LAN traffic), you would then have interfaces eth0.100 and eth0.200 to work with that you can then use in your firewall scripts as if they were two separate, physical interfaces.
This of course means you need a VLAN-aware switch that this single ethernet port can plug into, configured as a VLAN trunk (in Cisco terms) port. You would then want to configure one of the other switch ports as a VLAN access port assigned to VLAN 100 (untagged). This is the port you would plug your cable modem into. Then (in the simplest example) you could assign all the rest of the switch ports to VLAN 200 (untagged), and you would plug all your LAN devices into them.
The TL;DR is to have two vlans on the cable from your switch (called a "trunk"), "lan" and "wan", carrying the respective LAN and WAN networks. Then, on the Pi, create two vlans on the underlying Ethernet interface. Then those two VLAN interfaces can be configured just like the LAN and WAN interfaces of the router. On the switch, you’d dedicate one port to the WAN by adding it to the WAN VLAN without tagging, and the other interfaces do the LAN VLAN, also untagged.
I... Don't think it does that? It shouldn't, anyway. How long has that been a thing? They've been hit pretty hard by the slop crew lately but I couldn't imagine it being so bad they require an up to date UA
It's going on since quite a while. Want to update some GNU software, or look up something? I have to switch the user agent to "curl" to be able to visit the sites.
It is weird to think, computers are almost completely devoid of whirring nowadays. Other than the fan, and fans have gotten quite quiet. Floppies, CDs, hard drives. Tapes even (although I’m not that old).
It’s just kind of funny, I guess, the upcoming generation will never have the surprising “wow, my computer is silent” moment. I guess that was a one-time thing.
I tried to describe to my kid the sound of a 5.25" floppy disc the other day. MMWA MWA mmmmmm MWAMWA mmmmmmm.
He has seen 3.5" discs, but never the large floppies. His mind almost exploded when I talked about games needing 7 or 8 discs and hitting certain points where the game would pause while you put a new disc in.
I remember when the hard drive on my PowerMac 7200/90 started to fail (I was told that some of the ball bearings the platter rotated on were broken [0]). When the drive detected a 'wobble' on the platter, the entire computer would just power down with no warning at all - it was like the sound of a vacuum cleaner powering off. Silence and a blank screen that looked like a power cut, followed by that "oh sh!t" moment.
I love that Amiga emulators (FS/E/Win)UAE have an option to emulate the floppy drive sound. Very nostalgic, but also useful as an indication that something's happening!
But most SPAMs are HTML, so you'll have a good default last-stage in-client filtering in place in case some SPAM actually makes it through the other setup on the server (greylisting, DNS based filtering lists, policy-based filtering, etc.) :)
Very much so. While a lot of mail clients block images, they can be used to track you. Hell a lot of HTML can be used to track you if you're smart about it
I run a setup like that on my (outdated) Yosemite machine to provide multiple private TLDs for local deployment/development needs.
I set that up in like 2014? Even back then it was known already that the quick /etc/resolver way was the deprecated way to do things. So I guess they finally killed that feature off?
The proper (more awkward) way is to use scutil directly (which then stores the settings in some binary plist somewhere, I assume).
Maybe try this and see if it still works afterwards?
scutil is only half the story, because some macOS lookups still go through mDNSResponder in ways that ignore or override that config, which leaves you debugging random misses and binary plist junk. At this point, unbound or dnsmasq is simpler.
It would be less hypocritical if that critique of the situation wasn't posted on a website that itself loads unnecessary 3rd party resources (e.g. cloudflare insights).
Luckily I use a proper content blocker (uBlock Origin in hard mode).
I can't select text. A huge accessibility issue. A site like that is disqualified by default. The whole content is in a thin stripe in the middle, left and right huge areas unused. Resizing the browser window causes weird effects.
If that's a case study how to not do things: Congrats! Job well done!
The squash and stretch effect is certainly not to my taste but it's a personal site, where people should feel they can try things out. I do think the effect should be disabled when users have "reduce motion" enabled.
Pretty much any Mac bought in the past 5 years can fulfil the requirements, which doesn't feel terribly unreasonable, and I bet the Intel case would be straightforward to cover too, and now you're catering for every Mac bought in the past 6 years.
Apple are dicks about making it easy to test on older macOS revisions, but I'm sure that'd actually be easier than you'd expect too. (I have a FOSS project that has macOS as a supported target. It targets OS X Mavericks, released in 2013. I don't have any easy way of testing anything older than macOS Ventura, released in 2022, and to be honest I don't really care to figure out how to do any better, but, last time somebody complained about OS X Mavericks incompatibility, and I fixed the problem, which was actually very easy to do: it did apparently work.) Put in a modicum of effort and I'm sure you can make this thing work for every Mac sold since like 2015, and there'd be a non-zero chance it'd work for some older ones too.
Thinking back to when BBSs were a thing, since that'd be on topic: perhaps Americans got a lucky break with the Apple II, in production from 1977-1993 (says Wikipedia) and seemingly a viable commercial platform for a measurable fraction of the period? For me, growing up in the UK in the late 20th century, the whole computer ecosystem seemed to get pretty much completely refreshed about every 10 years at the very most. Buy a BBC Micro in 1983: platform dead by 1990. Buy a ZX Spectrum in 1983: platform dead by 1991. Buy an Atari ST in 1985: platform dead by 1992. Buy an Amiga in 1986: platform dead by 1994. The PC was a bit of an exception, as the OS remained the same (for good or for ill...) for longer, but the onward march of hardware progress meant that you'd need new hardware every few years if you wanted to actually run recent software.
Anyway, my basic thinking is that if in March 2026 you are releasing some software that requires you to have a computer manufactured at some point in the 2020s, then this is hardly without historical precedent. It might even simply be the natural order of things.
Me? I set the displays to go to sleep after N minutes.
Ideally the PI also should to what the extra DSL Modem does… but I guess that's where the dram must stop. :D
reply