Red Hat Bugzilla – Bug 471082
telnet not answering
Last modified: 2009-01-06 13:23:11 EST
Description of problem:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Additional info:Responding "connection refused."
Can you give me more information on how you started the installation exactly?
Yes, sorry. I specify the command 'text telnet dhcp ksdevice=aa:bb:cc:dd:ee:ff' . I have tried this on two machines with multiple nics, therefore the ksdevice. I wait for the target machine to respond to ping, then telnet to it.
(In reply to comment #2)
> Yes, sorry. I specify the command 'text telnet dhcp ksdevice=aa:bb:cc:dd:ee:ff'
> . I have tried this on two machines with multiple nics, therefore the ksdevice.
> I wait for the target machine to respond to ping, then telnet to it.
Try booting with:
text telnet ip=dhcp ksdevice=aa:bb:cc:dd:ee:ff
Same result. However, the dhcp isn't the problem. I can see the address being assigned in /var/log/messages. And, as noted above, I wait for a ping response before telnetting.
*** Bug 472453 has been marked as a duplicate of this bug. ***
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.
More information and reason for this action is here:
Fix will be in anaconda-184.108.40.206-1.
Correction, will be fixed in anaconda-220.127.116.11-1.
Just tried with Anaconda 11.5.0. Unfortunately, an ip isn't being requested over dhcp.
And, if I try specifying ip=[addr], the machine doesn't appear to accept the address. It doesn't
respond to ping. Note that I have tailed /var/log/messages on the dhcp server to
ascertain that no address is requested over dhcp. So, maybe telnet is OK now,
but I'm a step short of that over dhcp or static address specification.
You're seeing a different bug now, not related to the telnet fix.
OK. So is it possible to have the fix in Anaconda-1.4.x, please? I need to do remote installs, and vnc isn't a workable option. I can't be the only one with this problem. Would be very helpful as there's no other way with F10.
We don't do official updates for the anaconda package, so backporting this fix doesn't really make much sense. Occassionally, the Fedora Unity project does make updated media that includes a newer anaconda, but this is nothing we officially regularly do. So it's really best not to rely on that.