On Thu, 29 Nov 2001, Mark A. Tagliaferro wrote: > I have the following system where I'm using Suse 7.1 on the servers: > > 172.22.2.0/24 172.22.3.0/24 172.22.4.0/24 > Clients Clients Clients > Internet Win95 Win95 Win95 > | | | | > +----------+ +----------+ +----------+ +----------+ > | Srv1 | | Srv2 | | Srv3 | | srv4 | > +----------+ +----------+ +----------+ +----------+ > | | | | > +---------------+---------------+---------------+ > backbone network 172.22.1.0/24 > > On srv1 I have masquerading, NAT, firewall etc running and it's working well. > >From the other servers I have access to the internet. The problem comes is on > the client side. Even though they are connecting (via samba) to the linux > servers they are not getting internet access. They manage to ping the nic on > the server but nothing on the backbone and obviously nothing on the net. > > The servers are abviously not routing the packets. Can this be simply solved > by fixing the route.conf or do i need to set up masquerading on all the > servers? Should I also be doing something to the samba config file? Nothing to do with samba. Try: echo 1 > /proc/sys/net/ipv4/ip_forward That will tell your servers (Svr[234]) that they can "route". If that works then read the suse docs on how to make the change stick worse case, add it to rc.local Yours Tony. /* * "The significant problems we face cannot be solved at the * same level of thinking we were at when we created them." * --Albert Einstein */ - : send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
