Cawifre

They washed each other, but the guy only paid attention to her chest because horny brain.

I've heard the notion that a backup you don't regularly restore is mostly just theater. If you need to feel comfortable that you can restore your backups, then do that. You will need another machine to use, and then just go through the motions.

As in a traincar with a staircase inside, or as in two stacked rail tracks in parellel along a subway route?

Please, could someone disect this frog for me?

I found a Wikipedia article that expands on motivations for the design: Titulus_(fortification)

The description in the wiki article and the orientation of the diagrams on page 63 of the Keeley document convince me that the ~~more common arrangement was to place the detatched screening wall segment on the exterior of the curtain with an~~ interior version sometimes used either instead of or in addition to the exterior screen.

Edit: I think I read the pg63 diagram orientations wrong, so I think my point is mostly that it can be either inside or outside, and that this whole PDF is really cool.

ip:port <-> ip:port

From any particular host (be it on the WAN or LAN) every TCP/UDP transmission is sent from some specific address-port pair destined for some other specific address-port pair. From the WAN (i.e. the Internet), every destination address must be in a public range, and we ran out of those a while ago, which is why NAT became a thing at all.

Your router is the only machine on your LAN that also has a WAN address, so every transmission destined for inside your LAN must be (from the perspective of the Internet) addressed to some port on your router. Port numbers under 1024 are special, but most of the 60-thousand other ports are without special meaning, and these unremarkable ports are the ones used to send outgoing transmissions even if the destination is some well-known, meaningful port like 80 (HTTP) or 22 (SSH). When the server responds (such as with an HTTP GET result) they send the response to the address-port pair that sent the originating request.

The magic ingredient in NAT is that your router remembers that it just proxied a request from some LAN station, and it holds in reserve whichever port it used to send that request (since it knows that any responses from the WAN will be aimed at that port of the router).

When your router receives a transmission from the WAN, it consults the records it has kept to decide which LAN station is supposed to received that transmission. Here we get to the concept of Port Forwarding, which just short circuits that NAT lookup and assigns some arbitrary port on the router as a persistant pathway to some specific LAN station.

In short, yes, only the destination port is required for your router to decide.

My favorite part is that the switch is still in the OFF position.

Just do the R => Julia conversion yourself with an AI assistant acting as a sounding board to explore ideas and experiment.

Generative AI is not even remotely close to trustworthy for a code converter, and under current limitations it seems that halucinations will be an intractible problem in any code manipulation that is being done without oversight by a skilled human that is able to understand the implications of the generated code.

This would make a fantastic profile picture!

Testerererer