Routing question!! (Solved)

[Mark A. Tagliaferro]

Just for the record this was the solution that worked!

Thanks to all
Mark
> 
> > 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?
> > Thanks
> > Mark
> >
> > __________________________________________________
> > Do You Yahoo!?
> > Everything you'll ever need on one web page from News and Sport to Email
> and Music Charts
> > http://uk.my.yahoo.com
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-admin" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> >
> Hi
> 
> well first of all as others noticed you have to enable ip_forwarding (echo
> 1 > /proc/sys/net/ipv4/ip_forward)
> 
> then you will have to either run some routing protocol in the backbone to
> "theach" each srv/router about the routes of networks behind other srv or
> you will have to add static routes to each router to the other subnets
> behind the other svrs
> 
> example , on srv1 you need to do:
> 
> route add -net 172.22.2.0 netmask 255.255.255.0 gw <ip-srv2> (you havent
> wrote the ip address of each srv server on the backbone network so you
> will have to replace srv2 with the ip address of srv2 on 172.22.1.0), this
> means that you tell srv1 that to reach 172.22.2.0 he need to send the
> packets to <ip-srv2>
> route add -net 172.22.3.0 netmask 255.255.255.0 gw <ip-srv3> (for the next
> network)
> route add -net 172.22.4.0 netmask 255.255.255.0 gw <ip-srv4> (for the
> last)
> 
> this should get internet connection working for the subnets behind srv
> 
> 
> then you will have to add similar routes to tech each srv about subnets
> behind other srv if you want to be able to reach eachother
> 
> example on srv2:
> route add -net 172.22.3.0 netmask 255.255.255.0 gw <ip-srv3>
> route add -net 172.22.4.0 netmask 255.255.255.0 gw <ip-srv4>
> this should make 172.22.2.0 be able to reach 172.22.3.0 and 172.22.4.0
> 
> you need to repeat this on srv3 and srv4 (of course changing the subnets)
> 
> .... you get the ideea right ? :)
> 
> PS: in your case i would prefer some routing protocol
> 
> ----------------------------
> Mihai RUSU
> "... and what if this is as good as it gets ?"
>  

________________________________________________________________
Nokia 5510 looks weird sounds great. 
Go to http://uk.promotions.yahoo.com/nokia/ discover and win it! 
The competition ends 16 th of December 2001.