On Thu, 2010-10-14 at 19:02 +0200, Krzysztof Paliga wrote: > Hi, > > Im wondering why with the following firewall rule the thin client > refuses to boot: > > iptables -A OUTPUT -d 192.168.0.0/16 -j ACCEPT > iptables -A OUTPUT -j DROP > iptables -A INPUT -s 192.168.0.0/16 -j ACCEPT > iptables -A INPUT -j DROP > > (linked under /etc/rcS.d/S99iptables) > > Both the ltsp server & the thin client have IP in this subnets. The thin client doesn't have an IP when it starts to boot, and your rules prevents it from obtaining one.
Try adding iptables -A INPUT -j LOG before iptables -A INPUT -j DROP and iptables -A OUTPUT -j LOG before iptables -A OUTPUT -j DROP and you'll see that bootp/dhcp requests are blocked. > > When I start the firewall after the thin client has bootet, everything > works fine(inclusive server login). > > Kind regards, > chris > ------------------------------------------------------------------------------ Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb _____________________________________________________________________ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
