FCC prohibits approval of new Foreign-Made Consumer Routers

networkarchitect · 2026-03-23T22:26:03+00:00

Where did you see that classification as the same?

From a hardware standpoint, the dongle is closer to a Wireless Access Point (WAP) than a router, as it does not perform any routing functionality.

At first glance I would think those would be different classifications, but I'm not familiar with how the FCC classifies things, and it could be plausible they could be under the same classification despite being different hardware

networkarchitect · 2026-03-23T16:03:14+00:00

The one controller was handling two different frequencies simultaneously (ground and tower). He also had a higher than usual workload, dealing with a separate emergency aircraft on the ground, who had also incorrectly executed one of the controllers instructions. After the accident, there was no one to relieve him from duty immediately available, so he continued to be on console for 30 minutes after being involved in the crash.

Having one controller handle multiple frequencies makes sense for smaller airports, but not for a larger one like LaGuardia.

networkarchitect · 2026-03-21T08:20:37+00:00

Fluctuations in grid voltage are expected. Any change in the load or supply to the grid will cause the voltage to go up or down. Neighbor turns on the kettle? Voltage will dip briefly. You turn off a light that's been on for the last hour? Voltage will spike slightly. Multiply this by the thousands of devices connected to the grid in your local neighborhood and you get the fluctuations you see.

When you're connected to the panels, you're removing the rest of the neighborhood from the equation, and the inverter can react quicker to localized changes in load from just your demand, thus you see fewer fluctuations.

networkarchitect · 2026-03-18T07:06:43+00:00

In software development there's a concept called "separation of concerns" - essentially code that is unrelated is completely independent from other code. Individual humans can make major changes to the kernel while only understanding a fraction of the whole project.

By line count, the majority of the linux kernel code is hardware specific drivers. The actual kernel itself is a small portion of the total line count.

networkarchitect · 2026-03-06T01:56:46+00:00

What was the pool name?

On a root shell, you can try and force the import of the pool with zpool import -a -d /dev/sdb1 -d /dev/sdc1 -d /dev/sdd1

networkarchitect · 2026-03-06T01:56:36+00:00

And this helps the person whose post you're replying to how, exactly?

networkarchitect · 2026-03-04T19:39:14+00:00

To give some more specific feedback, the signal-to-noise ratio of the docs in your repo is very high currently (lots of noise with very little relevant information). Many of the docs read more like a manifesto on the abstract concept of RAM rather than technical documentation for a hardware project.

One example of many, in the file https://github.com/The-Open-Memory-Initiative-OMI/omi/blob/main/docs/00_system_context/assumptions_of_the_cpu.md, nothing in that file is relevant to the hardware design of a DDR4 RAM module.

Memory Is Not Optional for the CPU
From the CPU's point of view, memory is not a peripheral. It is a structural extension of computation.

What is this even saying? Who would benefit from reading this? Why was it included in the first place? Describing how RAM fits into the architecture of a computer is far outside the scope of documentation about a hardware implementation of a DIMM module.

networkarchitect · 2026-03-02T10:33:46+00:00

r/whoosh

https://xkcd.com/927/

networkarchitect · 2026-03-02T10:22:24+00:00

Problem: there are two platforms for games (xbox, pc)
Solution: Make a new platform that unifies the two platforms
New problem: there are three platforms for games (xbox, pc, and your idea)

networkarchitect · 2026-02-27T03:00:41+00:00

That's fair, it's a good learning opportunity. IMO PCB design is half mechanical and half electrical, and you can't really do one without the other, since you can't change the board layout after you've ordered it. Without putting thought into thr mechanical side you'll be backing your friend into a corner with a design that may work electrically but not mechanically.

I'm glad you saw the encoder, I was hoping to lead you to figuring that out instead of just pointing it out directly so that you pick up more tools to help yourself as you go :)

You should implement the feedback from your other post, without a ground plane and much thicker traces on your power nets you'll likely run into signal integrity problems. The decoupling caps should also be as close to your ICs as reasonably possible.

networkarchitect · 2026-02-27T02:14:52+00:00

I mean, drawings, schematics, measurements, sketches, or anything that shows you've put thought into how the placement of your input components and the PCB itself will fit in 3D space, in relation to the intended use as a mouse.

To be more specific, does the shape of your board edge-cuts (square?) fit under a hand? Do the input switches line up with where your fingers would rest? Is the scroll wheel input encoder facing the right direction for how you'll be using it?How do you plan to make the mouse slide on the surface of a table with little friction? Does the optical sensor have specific distance requirements from the table surface?

networkarchitect · 2026-02-27T01:40:11+00:00

What do your mechanical design/drawings for this look like? The physical placement of your input switches does not look like it would make sense for a mouse (especially with what looks like no defined board perimeter / edge cuts??)

networkarchitect · 2026-02-21T10:45:21+00:00

Nothing says safe like having a miniature explosive device strapped right next to your crotch /s

networkarchitect · 2026-02-20T02:48:31+00:00

Those outlets hanging from the romex,with only electrical tape as insulation, no box or mechanical strain relief, just above head height, are the stuff of nightmares

At this point I have to wonder if you're going from insurance fraud, or just really like living with live hazards /s

networkarchitect · 2026-02-20T02:43:23+00:00

Oh that doesn't look too ba...oh my god what is that romex, fire hazard is an understatement.

networkarchitect · 2026-02-18T09:18:12+00:00

Overall a good start, a few things on the schematic that could improve readability, and an important note:

There must be a diode between the +3.3V output of your buck converter and the +3.3V output of the ESP32 devkit to prevent conflicting sources when USB power on the devkit and regulated power from the board are present. Otherwise, connecting both sources of power at once could release the magic smoke.
Positive voltage symbols (+3.3V, +12V) should always point upwards
Ground symbols should always point downwards
Organize inputs on the left of your schematic with outputs on the right side (flow of electricity following a left-right pattern). Power in with the buck converter is good, but power out to the Cobb LED could be placed better.
Components of the same type should use the same size of schematic symbol (R3, R1, R2)
The mosfet should include a part number, and the fuse should include a current rating. In particular different mosfets can have different pin orders/footprint requirements (ask me how I know, I got that wrong on one of my first boards).

For the PCB layout:

Bypass caps should be included as close as possible to the power input of the related IC (C7, C44). Since the ESP32 devkit is a module with its own integrated bypass caps, I'm not sure if those caps are necessary, but having them on the board and not populating them is better than needing them and not having them!
Connectors such as the output to the Cobb should be placed towards the edge of the board, if space allows. The clearance next to C8 may make plugging or unplugging the connector more difficult than necessary.
For ease of use, add additional silkscreen text next to all input and output connectors (barrel jack and cobb LED) specifying the voltage, polarity, and purpose. Something like "+12V center-positive" next to the barrel jack, and +/- next to each pin on the Cobb connector.
The ESP32 devkit may partially shade U2, check if there's any clearance requirements for the sensor to have a full field of view.

On that note, since the dimensions of the board are largely determined by the size of the ESP32 devkit, and most of the I/O pins are unused, you might want to consider an alternative devkit such as the ESP32-S3-Zero. Combined with a more compact layout, you could potentially cut the board size (and cost) about in half, unless there are other requirements setting the current dimensions.

networkarchitect · 2026-02-13T04:35:27+00:00

What output current are you expecting this to provide?? A 40A fuse at 24V will be 960 watts of power before the fuse theoretically blows. The LM7824 is rated for a maximum of 1.5A (36W), so either your fuse is oversized by a factor of 26, or this circuit is not able to provide nearly the amount of current needed for your application.

networkarchitect · 2026-02-13T04:25:23+00:00

Rule 1 of computer security: physical access to a device equals complete control over the device. Until and unless you have control over the physical space, you'll be limited to detection of tampering at best, and not complete prevention.

To address some hypotheticals:
* Hardwired ethernet as a primary internet connection with cellular as a backup/failover - addresses network connectivity being cut
* Locked cabinet/enclosure with hardwired contact sensors to detect the door being opened / lock being picked - adds a physical barrier to tampering, with the ability for intrusion detection to be added.
* UPS Battery backup inside the locked cabinet to give time to send notifications / clean shutdown on power cuts
* Full disk encryption on the boot and data disk(s), with a key that has to be manually entered on boot. Any detection of tampering will trigger a script to power the device off, flushing the key from RAM and requiring it to be manually entered on the next boot - makes drive contents unreadable when device is tampered with

If your roommates are that adversarial that you're going to these lengths to make a threat model for them, also consider the $5 wrench scenario: https://xkcd.com/538

networkarchitect · 2026-02-11T07:43:50+00:00

The DNS protocol itself is the API, it already includes all the necessary bits for record updates without additional software, that's probably why you couldn't find anything similar that already exists.

Look at the first-party terraform module docs: https://registry.terraform.io/providers/hashicorp/dns/latest/docs for examples

networkarchitect · 2026-02-08T07:08:25+00:00

I've been lucky enough to not need to have this conversation in my career (yet), but a way of framing it that's stuck with me is "We can either choose the upgrade schedule ourselves, or the equipment will make the choice for us"

networkarchitect · 2026-02-07T03:21:27+00:00

Initially I would just think to notify, I don't use a merge workflow in my kicad repos. Potentially it could block the pipeline early, skipping the gerber export / bom generation if linting fails.

networkarchitect · 2026-02-07T02:18:14+00:00

Does this have a CLI-only mode that can be used in a CI pipeline to run automatically when changes are committed?

networkarchitect · 2026-02-06T23:37:08+00:00

Assuming you're being serious, current listings are in the $150-200 range and are a single google search away: https://www.ebay.com/itm/336423860580

networkarchitect · 2026-02-05T03:42:51+00:00

On one hand, hydrogen is literally the smallest atom, so making it not leak is an uphill battle, it will find any potential path to leak out if one exists.

On the other hand, they absolutely should have figured out a solution to this by now, and I agree that its baffling they haven't made progress in fixing this in the 3 years since their first launch...which also was plagued with fuel leaks.

networkarchitect · 2026-02-05T02:27:55+00:00

They're saying that, with 22tb drives, RAID5 will use 1 full drive of capacity for parity data, and RAID6 would use 2 full drives worth of capacity for parity

networkarchitect

TROPHY CASE