Applicable to only those of the US (who choose to comply), which would mean giving non-US an advantage, which is a distinct no-no. They tried to restrict Fable to only-US, but that backfired since the world isn't at all clean cut, resulting in full unavailability of the model
Without international treaty and regulation restricting frontier capabilities globally, any attempt to outlaw open source models will only be as effective as King Canute ordering the tide to turn. Unless the USA fancies bombing those who refuse.
It cannot. The only available law is an export control law. A restriction on an open model would be strongly unconstitutional due to a freedom of speech guarantee in the Constitution.
With Wi-Fi 8 we will finally get steerable friendly roaming like cellular radio is doing for almost 40 years now.
This "here's a neighbor table, disassoc and fuck you&good luck"-method we must use right now is just super painful. It's super complicated to build reliable networks that way.
All ham radio repeater groups here dropped Meshtastic as it was super unreliable. And they know how to build proper antennas and filters.
Meshcore is 100% free. The last issue was the closed sorce Android/iPhone client - but there are FOSS Flutter based-Opensource clients available (https://github.com/zjs81/meshcore-open)
With GNSS+PPS and a hardware timer latch you can easily sync internal microcontroller timers to 2 to 3-digits nanoseconds against the global standard with a tightly controlled loop. But cannot get better than the PPS signal itself (roughly 30-100nS).
Everything below needs that a huge amount of engineering. CERN&friends developed the "White Rabbit" (https://ohwr.org/projects/white-rabbit/) system for this. This allows sub-Nanoseconds syncing of netwoked devices.
Yes. I'm aware. Perhaps I'm more stupid about this topic than normal, but it looks to me like the NICs I have do (NIC names have been changed for clarity, but all other output is untouched):
$ ethtool -T intel-nic
Time stamping parameters for intel-nic:
Capabilities:
hardware-transmit
software-transmit
hardware-receive
software-receive
software-system-clock
hardware-raw-clock
Hardware timestamp provider index: 0
Hardware timestamp provider qualifier: Precise (IEEE 1588 quality)
Hardware timestamp source: MAC
Hardware Transmit Timestamp Modes:
off
on
Hardware Receive Filter Modes:
none
all
$ ethtool -T brcm-nic
Time stamping parameters for brcm-nic:
Capabilities:
hardware-transmit
software-transmit
hardware-receive
software-receive
software-system-clock
hardware-raw-clock
Hardware timestamp provider index: 0
Hardware timestamp provider qualifier: Precise (IEEE 1588 quality)
Hardware timestamp source: MAC
Hardware Transmit Timestamp Modes:
off
on
Hardware Receive Filter Modes:
none
ptpv1-l4-event
ptpv2-l4-event
ptpv2-l2-event
Intel's drivers are notoriously annoying as the parent of the parent comment suggests. It seems to be a mix of hardware bugs and a driver that doesn't properly account for them. I know many who've moved to ASIX, Mellanox, and other chipsets just because they don't get weird behaviors or two edges per pulse without hacking the driver.
> It seems to be a mix of hardware bugs and a driver that doesn't properly account for them.
~~yaaaaay~~
Also, who the heck knows if my switches are behaving correctly? I may be dealing with a system with multiple failing components.
I'd never considered Mellanox hardware... I'd always thought of them as "super expensive datacenter hardware", but non-Infiniband cards I can see on Newegg aren't entirely-unreasonably priced. (TBD if I can find a PCI-E 2.0 1x card, though). I'd not heard of ASIX, and they have a card that would fit in my slot, but -sadly- no in-tree driver. It looks like the only in-tree driver is for a 100mbit card... the AX88796C.
Anyway, thanks for the advice/info and the mention of more-reliable manufacturers.
They are following closely and the best offer 80-90% of the performance and come with a very small fraction of the costs.
reply