From: tnp@invalid.invalid   
      
   On 01/01/2026 12:26, Richard Kettlewell wrote:   
   > The internal network destination address_is_  in its routing table.   
      
   But not its port. And not in its NAT table,   
      
   The essence of NAT is that the originating port cannot be accessed directly.   
      
   And that *everything* gets translated, There is no concept of 'allowing   
   some shit through even though it's not in my NAT tables' beyond   
   theoretical.   
      
   Whether  that is a feature of NAT or a firewall, is semantics, but *in   
   practice* it is not a security risk.   
      
   If the police want to examine my server, they simply knock on the door   
   with a warrant. No matter what protocol is on the interface   
      
      
      
   --   
   All political activity makes complete sense once the proposition that   
   all government is basically a self-legalising protection racket, is   
   fully understood.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)