Firefox as local app and networking

[M Rathburn]

Howdy folks!  I've tried the three suggestions given, but no love.  I don't
believe I have an 'abnormal' setup here, but let me give more details...

We have a PC network that connects to a hardware firewall/router/switch,
which connects to the internet.  That router scheme is 192.168.1.1.  eth0 of
the LTSP server plugs into this router and has a reserved IP address of
192.168.1.25.

We have a switch which all of the thin clients connect to.  eth1 of the LTSP
plugs into this switch (along side the thin clients).  eth1 has static
address of 192.168.0.254.

Here is /etc/network/interfaces:

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eth0
iface eth0 inet dhcp

auto eth1
iface eth1 inet static
    address 192.168.0.254
    netmask 255.255.255.0
    network 192.168.0.0
    broadcast 192.168.0.255


Here is /etc/ltsp/dhcpd.conf:

#
# Default LTSP dhcpd.conf config file.
#

authoritative;

subnet 192.168.0.0 netmask 255.255.255.0 {
    range 192.168.0.20 192.168.0.250;
    option domain-name "example.com";
    option domain-name-servers 192.168.0.1;
    option broadcast-address 192.168.0.255;
    option routers 192.168.0.1;
#    next-server 192.168.0.1;
#    get-lease-hostnames true;
    option subnet-mask 255.255.255.0;
    option root-path "/opt/ltsp/i386";
    if substring( option vendor-class-identifier, 0, 9 ) = "PXEClient" {
        filename "/ltsp/i386/pxelinux.0";
    } else {
        filename "/ltsp/i386/nbi.img";
    }
}


Mickey, I tried your suggestion of uncommenting the 'net.ipv4.ip_forward=1'
line in /etc/sysctl.conf, then added a static route entry into the
192.168.1.1 firewall.  While I could, from the 192.168.1.x network, now
successfully 'ping' the 192.168.0.254 server (which I couldn't before),
still can't see the internet running Firefox as a local app on the thin
client.  Not running as a local app still works fine.

Gavin, I followed the instructions given at
https://wiki.edubuntu.org/ThinClientHowtoNAT, but to no avail.  I did notice
that the instructions said to edit the /etc/network/options file.  I didn't
have an options file at all, so I created it.  Also noticed that its says
that 'By default the ltsp network uses 192.168.0.0/24'.  Doesn't it really
use 192.168.0.0/254?

Jonathan, I tried your suggestion of altering dhcpd.conf with the
192.168.1.1 router info.  No luck there either.  Looking at the thin client
after this change, it had this info:

address: 192.168.0.21  broadcast: 192.168.0.255  netmask: 255.255.255.0
gateway: 192.168.1.1  dns0: 192.168.1.1  rootserver: 192.168.0.254

Could still browse the internet just fine using Firefox on a thin client
running from the server, but running as a local app didn't work.


Where's the missing link in all this?  After trying each suggestion, I
reversed out and tried the next so as to avoid confusion.  Is the answer in
a combination of all of the above?

Thanks!

-Mike Rathburn
 Children First Florida