tftp open timeout.

[fsouyri]

Hello,

Since I upgrade our cluster from the FC14 to the FC15 I have a bad problem with the tftpd server.
I have some thinstations booting over the network after the update the boot failed with the message "TFTP open timeout".

I use an "ip alias" (cluster adress) for the tftp server (next-server in the dhcp), when I use the real ip I have no problem.

I found some information about a "Service Guard environment" and an option to enable it:

"This option is required for some tftp clients. These clients reject the tftp reply received from a
different IP address than the one requested when the server’s interface is configured with
an alias IP address."

I do not see an option like that in the tftpd server of the FC15.

Best regards.

Francis

[flyingfsck]

Well, TFTP has practically no security. Therefore some clients are paranoid about the network and file system settings. That is not altogether a bad thing and there is nothing you can do about it.

[fsouyri]

I have no problem with the FC14 when I boot the thinstation (PXE boot).

I do some test from a fc15 tftp client, "tftp realip" no problem, "tftp aliasip" i have these

tftp> trace
Packet tracing on.
tftp> get /thinstation/dell/pxelinux.0
sent RRQ <file=/thinstation/dell/pxelinux.0, mode=netascii>
received DATA <block=1, 512 bytes>
sent ACK <block=1>
received DATA <block=1, 512 bytes>
sent ACK <block=1>
received DATA <block=1, 512 bytes>
sent ACK <block=1>
received DATA <block=1, 512 bytes>
sent ACK <block=1>
received DATA <block=1, 512 bytes>
sent ACK <block=1>
received DATA <block=1, 512 bytes>
sent ACK <block=1>
sent ACK <block=1>
received DATA <block=1, 512 bytes>
sent ACK <block=1>
received DATA <block=1, 512 bytes>
sent ACK <block=1>
sent ACK <block=1>
sent ACK <block=1>

Best regards.

Francis

[fsouyri]

Hello,

I do the test from a fresh install and I have the same problem.

tftp realip --> OK

tftp aliasip --> KO

How can I post a beug the the fedora project ?

Best regards.

Francis