On Thursday, June 22, 2017 at 2:44:08 AM UTC+2, Carlos E.R. wrote:   
   > On 2017-06-21 21:33, andrew.williams@t-online.de wrote:   
   > > On Wednesday, June 21, 2017 at 8:38:33 AM UTC+2, Christian Schweingruber   
   wrote:   
   > >> Hi   
   > >>   
   > >> Am 20.06.2017 um 20:00 schrieb andrew.williams@t-online.de:   
   > >> ...   
   > >>> Does anyone else use IP Forwarding under 42.2?   
   > >> sure, every day, without any problem.   
   > >>   
   > >> Questions/Hints:   
   > >> - firewall?   
   > >> - cat echo /proc/sys/net/ipv4/ip_forward   
   > >> - routing   
   > >> - nat?   
   > >>   
   > >> greetings chrigu   
   > >>>   
   > >    
   > >    
   > > Firewall?  The Internal network is configured as just that.  Masquerading   
   was originally on but I have tried it both ways today.   
   > >    
   > > cat /proc/sys/net/ipv4/ip_forward ("echo"?) showed up as zero.  I turned   
   IPV4 and IPV6 forwarding off and on again (Yast Network Settings) and it was   
   then set to 1.  This could be a bug or it could be a symptom.   
   > >    
   > > Routing?  As I said originally, fixed IPV4 Addresses on that network and I   
   have the routing on the clients to go through that address.  It works on the   
   Suse 11.x machine which is on the same internal network.   
   > >    
   > > nat?  I have never configured this.   
   > >    
   > > I'm obviously doing something wrong but no idea what.  Thanks.   
   >    
   > You are giving too little information for us to make guesses...   
   >    
   > --    
   > Cheers, Carlos.   
      
      
   ok, I'll try a bit of verbosity.  All these settings are for the server which   
   is supposed to pass things through, the clients are perfectly happy with the   
   old system.   
      
   The old (working) gateway system runs SuSE 11.2 which is the last level which   
   ran on that particular hardware.   
   I had this running under Leap 42.1 without any difficulties, it has not worked   
   under 42.2 since the Upgrade.  The settings are identical between the two   
   machines unless specifically mentioned, they are untouched from 42.1 apart   
   from "test" changes.   
      
   The gateway servers also offer NFS and Samba to their clients, the clients   
   could and can talk both to the 11.2 and the 42.x machines.   
      
   Network settings:   
   - IPV6 is enabled   
   - "Change Default Route via DHCP"   
   - "Change Hostname via DHCP"   
   - Routing: No gateways defined   
   - Enable IP Forwarding is set (11.2), Enable IPv4 Forwarding and Enable IPv6   
   forwarding are set for 42.2.   
   - Network Setup Method is "Wicked Service", I'm pretty certain 42.1 also used   
   Wicked but 11.2 did not.   
   - The External interface uses DHCP   
   - The Internal interface has 192.168.x.y where x is the same for clients and   
   servers and y varies.  I set the appropriate value for y on the clients   
   depending on which one I want to use as a gateway.  Yes, dynamic would be   
   better but I only need to    
   change the value if something breaks.   
   - I rely on radvd to handle IPV6 routing, it worked for 42.1 and I'm pretty   
   certain it is working for 11.2 (I tested it back then).  I can see that it is   
   running on the 42.2 machine.   
      
   Firewall:   
   - The External interface blocks everything, the Internal interface permits   
   everything.   
   - "Masquerade Networks" is set, no additional qualifications.   
      
   The gateway systems also act as caching DNS servers (I run Bind) and the   
   clients are set up to try both IP addresses.  Name resolution via the 42.2   
   gateway is definitely working.   
      
   If I try "cat  /proc/sys/net/ipv4/ip_forward"   
   - the 11.2 machine returns a 1   
   - the 42.2 machine returns zero.   
   - as I wrote earlier: if I turn IPv4 forwarding off and on again, the 42.2   
   machine also returns a 1 but it still does not work.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)