Red Hat Bugzilla – Bug 643738
sshd kernel option useless without networking
Last modified: 2012-05-31 02:51:41 EDT
Description of problem:
Adding the sshd kernel option starts up sshd while anaconda is running. But it doesn't care about networking, i.e. sshd is running but no remote system can access it.
Adding ip=dhcp doesn't solve the issue either, i.e. doesn't really do dhcp. First I thought this to be a bug as well but the wiki page says "to use for a network installation" so I guess the ip= option is ignored in local media installs. I don't see how that makes sense, though.
Version-Release number of selected component (if applicable):
Fedora 14 Final TC1.1
Steps to Reproduce:
1. boot dvd with sshd option
2. try to access the system from a remote machine over ssh
3. change to tty2 and check activated interfaces with ifconfig
4. notice that only lo is active
sshd active but not accessible
sshd active and accessible
There's no use in having sshd running on a local media install normally - but if your graphics driver blanks your screen while the rest of the system keeps running fine it'd be such a nice option to extract the relevant log files over ssh/sftp. Right now I have to change to tty2 and start dhclient blindly...which works, but is not really the most comfortable way of doing things.
Pass 'asknetwork sshd' and it will work.
Sounds like a fine workaround for me - but I think the default behavior should be different. I think e.g. vncconnect enables networking, so why doesn't sshd?
Should be fixed in F15 Beta.