From: lew.pitcher@digitalfreehold.ca   
      
   Hi, Henrik   
      
      
   On Thu, 02 May 2024 05:15:19 +0000, Henrik Carlqvist wrote:   
      
   > On Wed, 01 May 2024 17:12:52 +0000, Lew Pitcher wrote:   
   >> I should mention that, in this configuration, I /have not/ implemented   
   >> any firewall rules. I want to get basic routing working before I start   
   >> complicating the data flow with a firewall.   
   >   
   > Maybe those firewall rules are exactly what you need. My guess is that   
   > you are lacking NAT (IP masqueradning). When sending ping or any other   
   > packet out from sysdev2 to internet those packages come from your private   
   > IP address 192.168.55.2 but only the sysdev1 machine knows how to reach   
   > back to that IP address. Your machine wordsworth with IP address   
   > 192.168.99.3 does not have a route back to 192.168.55.2.   
      
   And, with that simple statement, you have solved my problem.   
   /Of course/, wordsworth needs a route back to sysdev2. And, in the   
   environment I'm trying to model, that route would be supplied by   
   a NAT rule on sysdev1.   
      
   > Either you will   
   > need to implement NAT on sysdev1 or add a route on wordsworth (and   
   > probably also implement a more cumbersome NAT in your real internet   
   > facing router).   
      
      
      
   Thanks, Henrik. You've hit the nail on the head.   
   And now, I'm off to make some firewall rules.   
      
   --   
   Lew Pitcher   
   "In Skills We Trust"   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)