pfSense would be a better choice than OpenWrt
I heard pfSense had a hard time with wireless radios, and that’s where OpenWrt shines comparably. Is that not true?
pfSense would be a better choice than OpenWrt
I heard pfSense had a hard time with wireless radios, and that’s where OpenWrt shines comparably. Is that not true?
Packet loss occurs when a router has to drop some packets because the buffer to store them is running out because the link where they are supposed to go is overloaded.
Bufferbloat is the issue where you make your queues too deep, i.e. you allocate too much RAM to buffering, while the cause of the buffering still exists, so the deeper queue just fills up anyway, so you haven’t improved anything, and have induced extra latency on the packets that do make it trough.
Deep buffers can help in situations where you have a step down in link speed, but only bursty and not sustained overloading of the slower output link.
The big bottleneck in router hardware is more about TCAM or HBM memory used to store the FIB of the global routing table. Since the table has grown so much the devices with less high speed memory can’t hold the table anymore, and if they start swapping the FIB to normal memory your routing performance goes to shit.
So not all of your concerns seem to apply to this class of device, but of course you’re right, The Register should have mentioned the RAM.
what can I do on the LAN when the internet gateway is down
Access your NAS from your workstation or your media PC.
Can confirm. I’ve seen this on multiple boards. I think this was Asus nomenclature.
Depends on which instance you use for your client, I would say. For me only discuss.tchncs.de gets to see my IP address, and Milan Ihl, our admin, as well as his Lemmy server, are in Germany.
This means two things:
But I’ve probably doxxed myself with personal stories. Pretty sure a dedicated person could find my employer, the team I’m in, and my age.
More importantly, they can’t adapt Windows to their (rather unusual) needs.
Damn that’s a spectre that I hadn’t even thought of yet.
I’m guessing here, but the only thing that makes sense in context is Fixed Wireless Access, FWA.
Maybe some error with the initialism snuck in because Shimitar is from Italy. I could see myself doing something similar, since in German we read W as “vee”.
Well, maybe now with a republican FCC
lol, no
All these shady things started happening after he left.
Not really, they have a history of this kind of thing. They just calmed down a little between roughly 2005 and 2015.
The big antitrust case when they killed Netscape was in 1998. Bill Gate’s deposition from that case is kind of interesting to watch as a historical document. It’s on youtube here: https://www.youtube.com/playlist?list=PL90W55zhFBOuZuhgxBsjpgDy0o3ll1PSz
In that lawsuit their “Embrace Extend Extinguish” strategy in which they tried to smother open standards became public too.
They tried with Java and their J++ language too, but failed luckily. And lost a lawsuit against Sun on the way.
There is this overview showing the options: https://openwrt.org/docs/guide-user/network/wifi/wifiextenders/overview
I have only used the WDS mode once and none of the others, so my experience isn’t enough to make a recommendation.
I’ll just quote the OpenWRT Wiki here, because I think half the comments here confuse mesh and roaming:
Are you sure you want a mesh?
If you are looking for a solution to enable your user devices to seamlessly roam from one access point to another in your home, you need 802.11r (roaming), not 802.11s.
It is unfortunate that some manufacturers have used the word “Mesh” for marketing purposes to describe their non-standard, closed source, proprietary “roaming” functionality and this causes great confusion to many people when they enter the world of international standards and open source firmware for their network infrastructure.
- The accepted standard for mesh networks is ieee802.11s.
- The accepted standard for fast roaming of user devices is ieee802.11r.
These are two completely unrelated standards.
Source: https://openwrt.org/docs/guide-user/network/wifi/mesh/802-11s#are_you_sure_you_want_a_mesh
Wow they really went into their stupid useless plan in the most ham-fisted way
On a general note I would say for the individual consumer it doesn’t matter so much if they keep releasing yearly, we just don’t have to buy yearly.
It’s kind of a waste of resources for the manufacturers supporting more models than necessary. If that leads to shorter support schedules that’s when it impacts us. But as you observed they seem to be lengthening at the moment.
I’m currently on a Pixel 6 from 2021, that I bought used from someone who was chasing the latest and greatest. I have no reason for changing yet. After October 2026 when support ends I’ll see if I have to migrate to Graphene OS or something. If no secure path forward exists I may have to get newer hardware then.
From what I can tell, the only OEM that does this currently might be Fairphone.
Does what? I don’t see anything in the sentences before that “this” could refer to.
I wouldn’t say it’s in trouble. It’s about to be retired by ICANN. But there isn’t any trouble, just standard policy processes.
That makes sense. He’s old enough and close enough thematically to have seen a few of these tech hype cycles.
You’d think the secret service were better at opsec than random soldiers getting their helicopters blown up.
The direction of your change doesn’t matter, the GPL license under which the program was already given out is not revocable.
If all copyright holders agree you can grant a different license in addition to the first one, or you can stop offering one license and start offering another one, all the new changes that were never offered under the first one will then only be publicly available under the new license.
But anyone who received the code at a specific time with a GPL license can keep it, modify it, distribute it onwards with the same license and so on, no matter what new terms the copyright holders begin to offer to other people later.