On Tuesday, August 1, 2017 at 12:04:12 PM UTC+2, Carlos E.R. wrote:   
   > On 2017-07-31 08:14, andrew.williams@t-online.de wrote:   
   > > On Tuesday, June 20, 2017 at 8:00:59 PM UTC+2, andrew....@t-online.de   
   wrote:   
   > >> I have a Windows (and Linux 13.2) machine which I use once or twice a   
   month, it connects to the world via my "main machine" and IP Forwarding.  The   
   IPV4 Addresses are fixed on that internal network, IPV6 forwarding via radvd.   
   > >> The IPV4 part of this has worked since 15-20 years on one Suse / Opensuse   
   version after another, the IPV6 part for around a year now.   
   > >>   
   > >> It has not worked since I upgraded from Leap 42.1 to 42.2.   
   > >> I have a spare 32-bit machine using Suse 11.1 and am currently having to   
   use that instead.   
   > >> NFS and Samba work perfectly well between the various hosts, but that is   
   all.  There is always a chance that I have screwed up a setting or two but it   
   certainly does not look like it.   
   > >>   
   > >> Does anyone else use IP Forwarding under 42.2?   
   > >   
   > >   
   > > I installed 42.3 a week ago and got around to testing this today.   
   > > It works again.  With the inherited network config from 42.2 and 42.1.   
   >   
   > Wonderful! :-)   
   >   
   > Sorry I could not see what was wrong previously.   
   >   
   > --   
   > Cheers, Carlos.   
      
   If it was not for CS saying it worked for him, I'd be assuming it was a   
   fundamental defect in 42.2.  As it is, I'm assuming it was a defect which only   
   applied under certain circumstances.  Should I hold you responsible for that?   
   -)   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)