On 04/04/2014 11:56 AM, sergioszy wrote:
>
> Dear all,
>
> after installing 13.1, I really sorry, lot of things not working. Too
> complex now.
>
> Can not login from local subnet using ssh, even after modify
> /etc/ssh/sshd_config
First, be sure SSH is running, as a default install will not have it
running. You can use Yast to start the service, and set it to auto-start
in the future.
After that, you should make sure that the firewall is not blocking TCP 22,
which you also do via Yast: Security: Firewall. Add ‘Secure Shell’ from
the list of allowed services, save and that should be it. To load this
from the command line:
Code:
sudo /sbin/yats firewall
> Pings from pcs in local subnet not responding too.
The default firewall does not block ICMP echo requests, so this isn’t the
firewall unless you’ve customized it to block somehow.
> And more, but I need this two basic things to continue.
>
> From 13.1 to other computers not problems at all. I can login into
> others linux using ssh.
Ask the 13.1 box a bit about itself and post back the results:
On 04/05/2014 10:56 PM, jetchisel pecked at the keyboard and wrote:
> To check if the firewall is up
>
> Code:
> --------------------
> rcSuSEfirewall2 status
> --------------------
Unless you are using systemd in which case it would be:
systemctl status SuSEfirewall2
Change the status with start, stop, enable for the function you are
looking for. Systemctl is <tab><tab> friendly.
On 2014-04-06 13:44, Ken Schneider wrote:
> On 04/05/2014 10:56 PM, jetchisel pecked at the keyboard and wrote:
>> To check if the firewall is up
>>
>> Code:
>> --------------------
>> rcSuSEfirewall2 status
>> --------------------
>
> Unless you are using systemd in which case it would be:
Nope. Even in that case, the rc… syntax works. There was a decision to
keep in openSUSE the rc… links, and even more, make sure that
services that don’t have it create it or the package will not build in OBS.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
On 04/06/2014 09:18 AM, Carlos E. R. pecked at the keyboard and wrote:
> On 2014-04-06 13:44, Ken Schneider wrote:
>> On 04/05/2014 10:56 PM, jetchisel pecked at the keyboard and wrote:
>>> To check if the firewall is up
>>>
>>> Code:
>>> --------------------
>>> rcSuSEfirewall2 status
>>> --------------------
>> Unless you are using systemd in which case it would be:
> Nope. Even in that case, the rc… syntax works. There was a decision to
> keep in openSUSE the rc… links, and even more, make sure that
> services that don’t have it create it or the package will not build in OBS.
>
That is true, for now. At some point they will go away.
Once you get used to using systemctl and it’s <tab><tab> capabilities it
becomes easier to use. You can even use ‘systemctl start <tab><tab>’ and
it will (I believe) only show services that are not started. Therefore I
find it to actually more intuitive.
>>> Unless you are using systemd in which case it would be:
>> Nope. Even in that case, the rc… syntax works. There was a decision to
>> keep in openSUSE the rc… links, and even more, make sure that
>> services that don’t have it create it or the package will not build in
>> OBS.
>>
>
> That is true, for now. At some point they will go away.
No, they will not. It is official openSUSE policy to keep them, and
enforce adding them with an automated check in OBS.
See:
+++···························
Date: Wed, 29 Jan 2014 13:48:05 +0100
From: Ludwig Nussel <...@suse.de>
To: openSUSE Factory list <opensuse-factory@opensuse.org>
Subject: [opensuse-factory] rc* symlinks and systemd
Hi,
openSUSE has a packing policy of requiring rc* symlinks for each
init script. So for e.g. /etc/init.d/foo there must be a symlink
/usb/sbin/rcfoo → /etc/init.d/foo. There is an rpmlint check for this
policy (suse-missing-rclink).
…
···························+±
And it was accepted, none refused.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
As you can see there are two start-up scripts one in /etc/init.d/ssh and /usr/lib/systemd/system/sshd.service
And if you run
file /usr/sbin/rcsshd
/usr/sbin/rcsshd: symbolic link to `/etc/init.d/sshd'
You will see that rcsshd points to /usr/sbin/sshd
head /etc/init.d/sshd
#! /bin/sh
# Copyright (c) 1995-2000 SuSE GmbH Nuernberg, Germany.
#
# Author: Jiri Smid <feedback@suse.de>
#
# /etc/init.d/sshd
#
# and symbolic its link
#
# /usr/sbin/rcsshd
So if you have a package that do not have a startup script in /etc/init.d and you have it in /usr/lib/systemd or /etc/systemd then it is not required for you to create an rc ;), which will build just fine either locally or on the OBS server itself.