two network cards for ltsp server

[Gavin McCullagh]

Hi,

On Fri, 29 Jun 2007, Uwe Geercken wrote:

> card that is used for internet access has 192.168.0.1 / 255.255.255.0.

> internal lan traffic has 192.168.1.1 / 255.255.255.0.
 
> now the traffic from the server internally and to the internet works. also the
> traffic from a client with 192.168.1.2, hooked up to the switch works. I can
> also ping the server and the 192.168.0.1 interface, but I can not get internet
> access on the client.

So, the client can ping both interfaces on the server.  Presumably it
cannot ping the isdn router?  This might just need forwarding switched on,
see below.

> btw: i am not booting the clients to the ltsp server. the client is a fat client
> for the moment, but I want to be able to have it work also in this scenario.

If I understand correctly you have

	-------      ----------      ----------
	| net | <--> | Server | <--> | Client |
	-------      ----------      ----------

and you need the client to get to the net with the server routing the
traffic for you.  The client is obviously not an LTSP thin client but a
standalone computer of some sort.

For linux server to route traffic, you need to turn on ip forwarding with:

	echo 1 > /proc/sys/net/ipv4/ip_forward

> the routing is set up as follows:
> 
> route add - net 192.168.0.0 netmask 255.255.255.0 gw 192.168.0.1
> route add - net 192.168.1.0 netmask 255.255.255.0 gw 192.168.1.1

This looks right for the server (apart from the space in "- net"), but you
shouldn't need these commands as linux will create routes to the networks
you're directly on.  The above would be wrong for the client.  You should
just set the default route to be out its one interface as 192.168.0.1 is
not directly visible from the thin client.

> so now my question would be, what is wrong in this setup. respectively what I
> have to do on the client side, to be able to access the internet.

The ip_forward is important.  If that doesn't work, you might reply with
the output of the commands /sbin/route and /sbin/ifconfig on both the
client and the server.


Gavin