Thanks Jim.
RE. "You should set eth1 as a trusted interface so it doesn't do any filtering".
iptables -A INPUT -i eth1 -j ACCEPT iptables -A OUTPUT -o eth1 -j ACCEPT iptables-save [I've sent the output]
..but an attempt to boot ws001 was not successful.
tail -f /var/log/messages ..gave me
Nov 26 11:11:44 tux kernel: IN=eth0 OUT= MAC= SRC=203.79.110.81 DST=203.79.110.255 LEN=260 TOS=0x00 PREC=0x00 TTL=64 ID=31 DF PROTO=UDP SPT=138 DPT=138 LEN=240 Nov 26 11:11:44 tux kernel: IN=eth0 OUT= MAC= SRC=203.79.110.81 DST=203.79.110.255 LEN=232 TOS=0x00 PREC=0x00 TTL=64 ID=32 DF PROTO=UDP SPT=138 DPT=138 LEN=212 Nov 26 11:13:08 tux kernel: IN=eth0 OUT= MAC=00:a0:cc:d9:e2:48:00:b0:8e:42:76:80:08:00 SRC=69.61.186.153 DST=203.79.110.81 LEN=48 TOS=0x00 PREC=0x00 TTL=108 ID=15181 DF PROTO=TCP SPT=4807 DPT=17300 WINDOW=64512 RES=0x00 SYN URGP=0
.. no mention of eth1, and
Tux:~# ps aux | grep dhcpd root 3834 0.0 0.3 3140 1408 ? Ss 09:29 0:00 /usr/sbin/dhcpd3 -q eth1 root 7744 0.0 0.1 1580 508 pts/0 S+ 11:19 0:00 grep dhcpd
the '-q eth1' seems new. dhcpd3 does not seem to be recognising eth1 or is querying it. Should it have been 'declared' to dhcpd3 somewhere, or should I flush iptables and start again ?
Hmm, the most important part of problem solving seems to be in asking the right question.
Adam Bogacki, [EMAIL PROTECTED]
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/
_____________________________________________________________________
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
