If ppcboot sends a bootp request to a server, but the server does not
have a bootp server running - it sends back an icmp port unreachable
packet. ppcboot does not detect and handle this.
Same for tftp requests.
Are you sure?
PPCBoot uses a broadcast address for the BOOTP request, so there is no dedicated server that can send a port unreachable packet.
With TFTP you are probably correct, but even if PPCBoot detected the problem it cannot fix it.
What is your suggestion?
I'd suggest that ppcboot catch the error coming
back from the tftp connect refusal and print an
error message and stop.
As it is now, it just ignores errors and continues
to timeout and resent requests. The ppcboot
user cannot tell what is happening. The ethereal
user can see the connection refusals going back
to ppcboot, followed by a connect request to the
very same port.
Logged In: YES
If ppcboot noticed that it was getting connection refused messages
from the TFTP it could perhaps display a diagnostic as well as
continuing to retry.
Log in to post a comment.