/tech/ - Technology

>>31764
>4mb ai slop image
>ai slop paragraph to bypass minimum length
>literally no content in the OP
why do mods allow this garbage. I always report and the always dismiss my reports

>it's not DNS
>it's not DNS
<it's DNS

mOTHERFUCK

>>31765
dont like it dont respond, no ones forcing you to discuss networking

What is some useful stuff to learn in terms of networking?

>>32588
Nftables
iproute
vyos
protocols
Staring at wireshark

>>32588

# Basic Terms
Software Defined Networking
IDS/IPS (Intrusion Prevention System)
IPv6 & implementation
Placing IPv4 Addresses inside of IPv6 addresses for simplicity
NAT (Network Address Translation)
SLA (Service Level Agreement): Maintain certain levels of uptime for your activist house.
Encrypted DNS Implementations
The domain .local or .internal

# Federal Power
- The knowledge that HTTPS is not resistant to Quantum Computers and that the NSA can save obscure amounts of data in Tape Storage for save now, decrypt later attacks.
- Americans can seize Domain Names with martial law and war time power acts. This means Crimethinc, the Anarchist Library, & Leftypol will lose control of their domain names within the next decade following a US vs China war regarding Tiawan, China in 2035.
- Custom root certificate authorities and DNS Providers: So your activist house CA and Domain Names can't be hijacked by a domain seizure.
- Upstream Internet Connection: (where your protest camp network joins the wider internet for 14 hours, before getting shut down).

i have a site2site wireguard vpn that lets push backups from my homelab to another rack in my grandparent's basement

had the idea for a IPv6 only network that receives an IP block via SLAAC and doesn't even have a router, just switches, firewalls, and WAPs, is this possible?

Had another idea for a network topology. The network is partitioned into two parts, a dirty part and a clean part.

At the center is a DIY data dyode. It connects a server fitted with a RAID array and large GPU to the dirty network. It hosts a UDP file server which receives signed chunks which can be manually resent by chunk (it deletes incorrectly signed chunks), a set of VDI servers for terminals, and a Local LLM, at the minimum.

This server is connected directly via a switch and ethernet to a number of terminals, likely Banana Pis. Example terminals could include a multimedia system (a nice tv and controller is all you really need), or a workstation for writing, and programming (a nice keyboard and vertical monitor is all you need). We're currently pre-streaming here, so this setup makes some sense.

The dirty network is more or less standard. The user uses the dirty network to download files and upload them to the server.

>>32856
>It hosts a UDP file server which receives signed chunks which can be manually resent by chunk (it deletes incorrectly signed chunks)
I've written the server, but not yet tested it. I'm also not sure how large to set the buffer size, just seems like it should be related to the MTU. The entire program would fit on four screens, and the most complex part, which is not very complex, on two (pic rel).

The server basically just receives a datagram which has a UUID (16 bytes), start (8 bytes), length (8 bytes), and a payload. It writes the payload out to the start position in a file with the UUID as the name.

It also maintains an interval tree of missing intervals of the file as a csv. It initializes to an interval from zero to the file length and then on every write to the file subtracts the interval from the tree, and then it writes the whole thing to disk.

It's only realistic to run this program if you're in the LAN, or tunneling in. And also it expects you to be running IPSec for the authentication and encryption, probably with a static SA (whatever that is) and ESN so that you don't have to do key negotiation.