Embed this notice7666 (7666@comp.lain.la)'s status on Thursday, 07-Sep-2023 09:57:41 JST
7666I'll be doing network maintenance on September 10th to swap out the core router for a shiny new one with (hopefully) less problems. I am NOT be replacing the virtualized pfsense just yet - that's phase 2. I just want the core swapped because it's getting flaky, then I'll get around to that later.
Goes without saying but uncached services will not be available during the swap (this means pleroma). When it happens, you'll know. Gonna take probably 45 minutes. (It'd be twice that without Jade around - thank god for her)
@bot@7666 a router is the thing that your devices connect to on your home's local network, and then its job is to connect to the rest of the internet. though that might be the job of a modem that you plug the router into, to connect to coax or fiber or dsl internet
@bot@7666 you make a request, the router sends it to the website and back to you. I believe it's achieved through NAT through routers and networking are the most frustrating thing I've dealt with for some reason, it's not that they're hard I've just been exceptionally unlucky
as for another machine directly contacting yours (initiating the connection), this can either be done through port forwarding (router maps a specific local device port 6969 to public IP port 6969), not possible to have multiple devices serve the same port from one IP
@bot@olmitch@meso NAT is the magic behind why you can have a ton of devices on a single public IP address leased from your ISP. It keeps track of the connections your devices make so that when the reply comes back, it knows which device to send it to. This is all on the IP layer and has nothing to do with MAC addresses, which just help the switching part of your router find the device on the LAN. Switching and routing are two entirely different things, for the record.
@bot@olmitch@meso Your device has to talk to your router first before it can talk to the outside world, hence the term "default gateway". When you make a request for a website from a device, It knows this device, from a specific IP and port, asked for a specific IP and port outside the network (remember, DNS is not a factor here in routing).
Your router may either preserve the device's source port or rewrite it altogether and use its own in place (It doesn't matter, because that website is seeing the router, on your public IP, make the request). Either way, it knows, and because it knows, it can get the traffic to the correct spot.