two network cards for ltsp server

Uwe Geercken uwe.geercken at datamelt.com
Sun Jul 1 17:51:10 BST 2007


hello gavin,

I don't get it working.

I have tested it now with a brand new client with 192.168.1.14. now I can ping
192.168.0.1 and 192.168.0.251 (my ISDN box which does dhcp and dns). but I
don't get internet access on the client. only on the server 192.168.1.1.

here are the server details:

=======================
root at feldberg:~# ifconfig
eth0      Protokoll:Ethernet  Hardware Adresse 00:18:E7:16:25:EE  
          inet Adresse:192.168.1.1  Bcast:192.168.1.255  Maske:255.255.255.0
          inet6 Adresse: fe80::218:e7ff:fe16:25ee/64
Gültigkeitsbereich:Verbindung
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:443 errors:0 dropped:0 overruns:0 frame:0
          TX packets:213 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenlänge:1000 
          RX bytes:45960 (44.8 KiB)  TX bytes:22307 (21.7 KiB)
          Interrupt:20 Basisadresse:0x6f00 

eth1      Protokoll:Ethernet  Hardware Adresse 00:0D:56:D2:D7:86  
          inet Adresse:192.168.0.1  Bcast:192.168.0.255  Maske:255.255.255.0
          inet6 Adresse: fe80::20d:56ff:fed2:d786/64
Gültigkeitsbereich:Verbindung
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:176 errors:0 dropped:0 overruns:0 frame:0
          TX packets:374 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenlänge:100 
          RX bytes:100151 (97.8 KiB)  TX bytes:57220 (55.8 KiB)
          Basisadresse:0xddc0 Speicher:fe9e0000-fea00000 

lo        Protokoll:Lokale Schleife  
          inet Adresse:127.0.0.1  Maske:255.0.0.0
          inet6 Adresse: ::1/128 Gültigkeitsbereich:Maschine
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:76 errors:0 dropped:0 overruns:0 frame:0
          TX packets:76 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenlänge:0 
          RX bytes:5976 (5.8 KiB)  TX bytes:5976 (5.8 KiB)

root at feldberg:~# 

root at feldberg:~# route
Kernel IP Routentabelle
Ziel            Router          Genmask         Flags Metric Ref    Use Iface
192.168.1.0     *               255.255.255.0   U     0      0        0 eth0
192.168.0.0     *               255.255.255.0   U     0      0        0 eth1
link-local      *               255.255.0.0     U     1000   0        0 eth1
default         intern          0.0.0.0         UG    0      0        0 eth1
root at feldberg:~# 


>>>> and here the client details:

eth0      Protokoll:Ethernet  Hardware Adresse 00:02:55:F4:BD:78  
          inet Adresse:192.168.1.14  Bcast:192.168.1.255  Maske:255.255.255.0
          inet6 Adresse: fe80::202:55ff:fef4:bd78/64
Gültigkeitsbereich:Verbindung
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:216 errors:0 dropped:0 overruns:0 frame:0
          TX packets:529 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenlänge:1000 
          RX bytes:23468 (22.9 KiB)  TX bytes:56830 (55.4 KiB)

lo        Protokoll:Lokale Schleife  
          inet Adresse:127.0.0.1  Maske:255.0.0.0
          inet6 Adresse: ::1/128 Gültigkeitsbereich:Maschine
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:160 errors:0 dropped:0 overruns:0 frame:0
          TX packets:160 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenlänge:0 
          RX bytes:11836 (11.5 KiB)  TX bytes:11836 (11.5 KiB)

Kernel IP Routentabelle
Ziel            Router          Genmask         Flags Metric Ref    Use Iface
192.168.1.0     *               255.255.255.0   U     0      0        0 eth0
link-local      *               255.255.0.0     U     1000   0        0 eth0
default         192.168.1.1     0.0.0.0         UG    0      0        0 eth0
=======================================

mybe it is simply a DNS problem?

rgds and thanks for your neverending help to everybody.

uwe





Zitat von Gavin McCullagh <gmccullagh at gmail.com>:

> 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
> 
> 
> -- 
> edubuntu-users mailing list
> edubuntu-users at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/edubuntu-users
> 





More information about the edubuntu-users mailing list