On Thursday 06 September 2007 13:46:23 Poul Møller wrote:
Problem solved.
Fedora 7 (or RH) has a bug that no matter what level you set the
firewall at, the GUI always say high. If you change the level, it will
indeed change the firewall settings, but the GUI will still say high. That
being
Thanks for the hints.
I do have: next-server 10.0.0.1 #Server address on the LTSP client
side.
and I was able to manually download get /lts/vmlinuz-2.6.16.1-ltsp-2
using a Linux tftp client on the 10.0.0.x network
I'll check if some additional options are set and certainly do a sniffing
I made some detective work using wireshark (great tool) as one previously
suggested. The clue points to badly configured network (my eth1/10.0.0.x) on
the LTSP client side. I get a dest. host unreachable.
No. TimeSourceDestination Protocol
Info
28
Problem solved.
Fedora 7 (or RH) has a bug that no matter what level you set the firewall
at, the GUI always say high. If you change the level, it will indeed
change the firewall settings, but the GUI will still say high. That being
said, just turn iptables off using the command line:
service
I'm upgrading (rather re-installing) LTSP 4.2 on a fresh Fedora 7 server,
but I'm having a very annoying TFTP Timeout problem on all my clients (Both
PXE and Etherboot clients)
My setup is quite standard:
eth0 (192.168.1.x) for internet access
eth1 (10.0.0.x) for LTSP clients
In the past
Am Donnerstag, den 30.08.2007, 15:02 +0200 schrieb Poul Møller:
I'm upgrading (rather re-installing) LTSP 4.2 on a fresh Fedora 7
server, but I'm having a very annoying TFTP Timeout problem on all my
clients (Both PXE and Etherboot clients)
My setup is quite standard:
eth0 (192.168.1.x)
On Thursday 30 August 2007 20:02:55 Poul Møller wrote:
I'm upgrading (rather re-installing) LTSP 4.2 on a fresh Fedora 7 server,
but I'm having a very annoying TFTP Timeout problem on all my clients (Both
PXE and Etherboot clients)
My setup is quite standard:
eth0 (192.168.1.x) for internet
