I know some folks who deployed during OEF/OIF and used these types of systems. Many a night raids were conducted simply by watching where attackers originated from.
Respectfully, you are incorrect. Switches, in the technical sense and accepted terminology, refers to Layer 2 processing. Routing is Layer 3. And so on. MLS is just a combined product offering multiple Layers of processing.
I think this argument can never be won. "Layer 3 switch" is common terminology. But "switching" strictly speaking is a Layer 2 action. But sometimes we say that a switch is "switching packets at Layer 3" when it is doing a hardware action in response to IP layer information. We could go back and forth all day. So let's all be reasonable if possible.
I believe “L3 switch” and routers(L3-L7) are distinguished by architecture; L2 and L3 switches employ non-programmable “packet switching fabric” ASIC with CPU acting as a control system, while routers are generally a general purpose computer optionally with non-Turing-complete ASICs for faster packet processing.
Expectations of a “switch” is therefore that it’s not a dual core PowerPC box with 24-96 GbE ports on PCIe, running outdated Linux Kernel, and that it can’t do what such a bare metal box could do.
I'm not sure what is non-programmable about the packet switching fabric. It can be programmed to switch packets, which is what we want the device to do. It can also be programmed to route packets, which is done at the same rate as switching them (usually line rate). So we can call this "layer 3 switching" because it is the same process as the L2 switching but it is happening at L3. That's what a L3 switch is and does.
It can't do the same as a box with general purpose CPU, but it can do the thing you bought it for (routing) at line rate (hence the comparison to switching).
My Brocade FCX 648S-HPOE arrived from eBay yesterday.
See I have a homelab setup I'm cobbling together and a mission to train a door to recognize and block my neighbor's cat from entry. Her name is Aria and she pisses everywhere then eats the cat food. I have 3 cats that require free use of the cat door, and if its closed they piss everywhere.
I've been scheming about how to do this for quite some time. The basic idea would be to install a magnetic lock on the cat door, and actuate it over an MTQQ triggered relay. But how to trigger it? My cats refuse to wear collars and their microchips weren't readable within usable proximity. Enter https://frigate.video/ this summer. Its a self-hosted NVR that can be trained to recognize arbitrary objects and fire off events when objects are detected, including to MQTT. It looked like a viable project, and I've been trying to get some camera system anyways for minding the front door while I work from a distant basement- but I haven't been willing to join the Ring panopticon just yet.
Over the past few months I've been acquiring the required hardware from eBay. I overpaid for a Google Coral USB TPU, and got a steal on a pair of their recommended cameras, Loryta IPC-T5442TM-AS-LED unused from a commercial install job. Unfortunately they are POE only, or a propriety 12VDC. I know I was going to need POE eventually anyhow, and while my Mikrotik RB4011iGS+5HacQ2HnD has a single POE port I would need more - and I wasn't able to get even that port working for one reason or another. So I found a Brocade FCX 648S-HPOE for $50. Overkill? Most definitely. I thought there would be no harm, and it would give me an opportunity to work with serious gear and improve my networking acumen. It is as loud as a laundry machine I swear.
Unfortunately its so serious that I need to go find an RS-232 cable to enable web management - until then it drops all links. So I still haven't been able even fire up the cameras. If my foraging through the cable bins again proves fruitless, then I'm going to their drive around town or find one online and wait until the next weekend...
So that Best Buy home equipment sounds kinda nice right now.
The Brocade FCX 648S-HPOE has is a stackable switch with forty four 10/100/1000 Mbps ports plus four Combo ports, which include four 10/100/1000 Mbps RJ45 ports and four 100/1000 Mbps SFP ports. The switch has two management interfaces, a DB9 serial port (Console) on the front panel and an RJ45 port (Out-of-band Management Interface) on the rear panel
A layer 3 switch does not just “glean” information from the packet , it can switch packets and rewrite IP header data at wire speed to place packets on different networks completely bypassing a router.
I don’t know of any better term for it than a “layer 3 switch”.
> Yep, not a monopoly, just a market bully applying mafia-like extortionary tactics.
Yeah that's totally it. It couldn't be that people like to have a phone that gets security updates for more than 2 years. Or having an AppStore that is policed in any meaningful way that keeps blatant spam and data-slurping apps out. Or any other numerous things that the Android ecosystem is totally fucked up on.
I love Apple haters- They rarely ever make sense and just come off as bitter.
> I love Apple haters- They rarely ever make sense and just come off as bitter.
Whether I hate or love Apple as a company doesn't (inversely) weigh in on my opinion on Google - same sh*t different mafia :)
To be fair, I "love" (some) Apple products and software, though they tend to be older incarnations. (But that's true for almost anything - newer versions become too "loud" for me.) Conversely, I "hate" some business practices (and tech choices).
But I'm not a fanboy of either, I just occasionally come across their products.
And I agree on the comment on the Android ecosystem. Which goes some way to say that a totalitarian mafia is better than a laissez-faire mafia.
I wonder whether this also means that cathedrals are better than bazaars?
That's completely unrelated though? Of course people do like to have a phone that gets security updates for more than 2 years. Apple makes a phone which gets security updates for more than 2 years, and also is applying mafia-like extortionary tactics.
> (Sorry to ramble, I'm doing what I started sarcastically referring to as my "executive time" during the Trump administration -- if the signal is sometimes useful you can't complain it's also sometimes weird as hell.)
"Executive time", a/k/a fuck off time, is perhaps one of the few great things Trump gave us. I'm legitimately not kidding. More people need to engage in fuck off time on a regular basis. It is refreshing for the mind.
That line from Fight Club really needs a whole lotta asterisks and qualifications. There are plenty of forced-recall scenarios where the manufacturer would prefer to use the ABC<=X approach but are not allowed or simply over-ruled by government. Safety of life being the primary over-riding concern, for good reason.
I'm pretty surprised this issue has gotten as long in the tooth time wise as it has. I remember seeing a story about this ticking-timebomb power connector like 1.5 months ago and then heard nothing. I'm guessing there is scurrying behind the scenes between then and now, but you never know.
I'm pretty certain that safety of life is not the primary over-riding concern (also for good reason) - modern vehicles can be made much safer by requiring advanced safety features (see: https://www.consumerreports.org/car-safety/cars-with-advance...) - but these aren't mandatory because there is a cost associated with each life saved, and, at some point, we as a society don't value human life as much as $$$ - so that's the line we draw.
Safety of life is not a boundless good. All of the good things around us come at some risk to life. Of course, the government's liability to overvalue safety (or to be more neutral, to inconsistently determine the value of safety) in a particular proceeding (be it before a court in a lawsuit or before a regulatory agency that might order a recall), is just another part of the calculation.
Ok, and? Aside from the pure theory banter, I expect the government to come down hard on a manufacturer when they knowingly ship a device with a sustained heat/power issue resulting in fires.
The fight club reference is to internal information and decision making processes, it doesn’t imply that the company is the only thing that can decide to do a recall.
> Imagine if the situation was flipped, and your CEO went "sales reps need to understand engineering complexity, so from now on they will each have to fix 10 bugs a month."
Picking up the telephone and debugging areas of expertise YOU created or are already responsible for is much easier than making a sales guy into a pseudo-engineer.
Also, paradoxically, some of the best product features I've come across literally started as a ghetto-coded-idea by a Technical Account Manager (sales engineer). Said features were later formalized and picked up officially by engineering, but the nexus of the product feature started with a non-dev.
Sorry for the ramble/rant. My point is this: Don't get so married to job titles. It can be limiting in my humble opinion.
I know some folks who deployed during OEF/OIF and used these types of systems. Many a night raids were conducted simply by watching where attackers originated from.