Red Hat Bugzilla – Bug 985425
remote ssh logins allowed after waiting at least 5 minutes. Shall be immediately, together with login screen display.
Last modified: 2015-06-29 08:05:37 EDT
Description of problem:
Takes minutes until ssh connections are allowed after rebooting. Seems to be an iptables related problem
Version-Release number of selected component (if applicable):
Install rawhide, upgrade to latest versions of packages, reboot the machine into rawhide, wait until console shows login screen.
Remotely login via ssh -- you'll have to wait about 5 minutes after console login is shown until you can login using ssh!
Steps to Reproduce:
1. Install rawhide, upgrade to latest versions of packages, reboot the machine into rawhide, wait until console shows login screen.
2. Remotely login via ssh -- you'll have to wait about 5 minutes after console login is shown until you can login using ssh!
Takes minutes until remote ssh logins are allowed after showing console login screen.
Allow remote ssh logins as soon als console login screen is shown.
Looks like ssh connections are disallowed after starting by iptables rules. After some time ssh connections are allowd.
This bug appears to have been reported against 'rawhide' during the Fedora 20 development cycle.
Changing version to '20'.
More information and reason for this action is here:
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora 'version'
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 20 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.