fat client k12linux access

[Peter Scheie]

I wrote a short how-to for myself on this a while back:


     * echo 1 >/proc/sys/net/ipv4/ip_forward
     * edit /etc/sysctl.conf to make that permanent
     * iptables -t nat -A POSTROUTING -j MASQUERADE
     * iptables-save
     * service dnsmasq start

The first two turn on forwarding, which is the primary requirement. The next two 
tell iptables to allow port forwarding; if iptables is turned off, they are 
unnecessary. The last one is to provide a DNS service to the fat client. 
Remember that thin client's apps are running on the server so they use the DNS 
server listed in /etc/resolv.conf. On the TC segment, however, dhcpd.conf tells 
clients that the nameserver is the LTSP server, meaning there needs to be a 
nameserver running on the LTSP server. That's what dnsmasq does. HTH

Peter

Barry Cisna wrote:
> Hello All,
> 
> F10-K12Linux Live Install
> 
> Having trouble with fat clients, AKA laptops being able to get the
> correct dns information from the k12linux server to gain internet
> access.
> 1. I have enabled ipv4_forwarding,in sysctl.conf and in iptables have
> set dnsmasq to -outgoing eth0 ( internal interface).
> 2. The laptops can ping both k12server nics/ltspbr0 but can not ping any
> public IP number.
> I know iptables/firewalling is hard to give advice on with the miriad of
> variables involved.
> Of course the actual TC's have no problem internet browsing. This is on
> both Linux and Winders laptops.
> Bottom line; K12linux server is not feeding non-TC machines dns info.
> 
> Thanks,
> Barry Cisna
> 
> 
> _______________________________________________
> K12Linux-devel-list mailing list
> K12Linux-devel-list at redhat.com
> https://www.redhat.com/mailman/listinfo/k12linux-devel-list
>