Making progresses.
I wanted to know whether Indy was listening at all on my wired
connection when two IPs where present. It happens that the init loop
finds the WiFi connection first in GStack.Addresses, and the wired one
second.
So I tweaked the init loop so that it initialized the bindings starting
from the topmost address in GStack, downwards.
Bingo, even when it has two bindings, the TFTP answers.
But it does it only once.
First conclusion:
At startup, TFTPServer only listen to the first of its bindings.
Once it's replied to the first query, TFTPServer doesn't answer anymore
(same symptom as before).
Second guess:
The TFTPServer has automatically switched to the second binding and is
now listening on the second binding only.
Finally:
Is TIdTrivialFTPServer designed to support multiple binding when
ThreadedEvent is set to false? /Ph.
