6:12 p.m.
* William Douglas:
That looks a little suspicious to me but I am not sure
what is mounted
where.
Your comment made me wonder if I had made a mistake when mounting the
partitions. I ran through the process again, and was finally able to
boot the resulting Clear Linux server. Thank you for helping me get to
this point.
One thing that stands out for me is that /etc is almost empty. It looks
like this system is as "barebone" as it gets, and that I am missing
some basic packages and configuration files (sshd_config among them).
-Ralph
6:20 p.m.
New subject: How to install on Hetzner CX cloud servers
That's by design. Our defaults are generally in /usr/share/defaults, or in the case of
SSHD compiled in. If you create the appropriate file in /etc the config settings will
take effect.
More details in 'man stateless' and
https://docs.01.org/clearlinux/latest/guides/clear/stateless.html
-Rob
On 3/31/20, 3:12 PM, "Ralph Seichter" <abbot(a)monksofcool.net> wrote:
* William Douglas:
That looks a little suspicious to me but I am not sure
what is mounted
where.
Your comment made me wonder if I had made a mistake when mounting the
partitions. I ran through the process again, and was finally able to
boot the resulting Clear Linux server. Thank you for helping me get to
this point.
One thing that stands out for me is that /etc is almost empty. It looks
like this system is as "barebone" as it gets, and that I am missing
some basic packages and configuration files (sshd_config among them).
-Ralph
_______________________________________________
Dev mailing list -- dev(a)lists.clearlinux.org
To unsubscribe send an email to dev-leave(a)lists.clearlinux.org
6:40 p.m.
New subject: How to install on Hetzner CX cloud servers
* Robert A. Nesius:
That's by design. Our defaults are generally in
/usr/share/defaults,
or in the case of SSHD compiled in.
It was not meant as a complaint. Being new to Clear Linux, I'll just
have to learn how things are done in this particular distribution, now
that I got the minimal server running. The sshd configuration stood
out to me, because I always disable password-based access.
I also need to set up IPv6 networking, timezone, admin user, etc. which
I guess I will be doing manually, like we did in the olden days. ;-)
-Ralph
6:56 p.m.
New subject: How to install on Hetzner CX cloud servers
On 3/31/20 3:40 PM, Ralph Seichter wrote:
* Robert A. Nesius:
IPv6: You shouldn't need to. systemd-networkd will setup ipv6 if your
router advertises it, which, in most cloud based environments, is the
case. Even NetworkManager does this properly I think.
time/date: timedatectl set-timezone ...
user admin: `useradd` :)
The installer does stuff like this for you. Even in a cloud setting this
may be useful: boot the server live ISO and install to an EBS volume and
you can use the TUI functionality to set these up. If you need to deploy
at scale, there are different tools.
Auke
That's by design. Our defaults are generally
in /usr/share/defaults,
or in the case of SSHD compiled in.
It was not meant as a complaint. Being new to
Clear Linux, I'll just
have to learn how things are done in this particular distribution, now
that I got the minimal server running. The sshd configuration stood
out to me, because I always disable password-based access.
I also need to set up IPv6 networking, timezone, admin user, etc. which
I guess I will be doing manually, like we did in the olden days. ;-)
7:15 p.m.
New subject: How to install on Hetzner CX cloud servers
* Auke Kok:
IPv6: You shouldn't need to.
Unfortunately I only see link-local IPv6 addresses, nothing of the /64
network assigned to this server.
time/date: timedatectl set-timezone ...
I needed to run "swupd bundle-add tzdata" first. Not that this was hard
to figure out.
user admin: `useradd` :)
Of course. I said "like in the olden days", did I not? :-) I am aware
that these steps are usually handled by the installer, but the way I set
this machine up, I have to make do without it.
-Ralph
12:59 p.m.
New subject: How to install on Hetzner CX cloud servers
* Auke Kok:
systemd-networkd will setup ipv6 if your router
advertises it, which,
in most cloud based environments, is the case. Even NetworkManager
does this properly I think.
Looks like Hetzner's infrastructure advertises IPv6 in a way that is not
easily picked up. I have now set up IPv6 manually in Clear Linux, as is
currently required for Gentoo Linux as well for Hetzner CX VMs.
After installing the NetworkManager bundle, I found that the following
configuration works for me:
----- 8< ----- snip ----- 8< -----
[connection]
id=wired
uuid=GENERATEDUUID
type=ethernet
interface-name=ens3
permissions=
timestamp=1585755915
[ethernet]
mac-address-blacklist=
[ipv4]
dns=213.133.98.98;213.133.100.100;213.133.99.99;
dns-search=horus-it.de;
method=auto
[ipv6]
addr-gen-mode=eui64
address1=2a01:222:333::1/64,fe80::1
dns-search=
method=manual
[proxy]
----- 8< ----- snip ----- 8< -----
Note that IPv6 routing in Hetzner's environment uses fe80::1 as the
default gateway. This fails if addr-gen-mode is set to stable-privacy
instead of eui64.
-Ralph
7:35 p.m.
New subject: How to install on Hetzner CX cloud servers
On 3/31/2020 3:12 PM, Ralph Seichter wrote:
* William Douglas:
the "man stateless" manual page tries to explain this and lists a set
of common things... it's quite useful to get the idea of things at least
That looks a little suspicious to me but I am not
sure what is mounted
where.
Your comment made me wonder if I had made a mistake when mounting the
partitions. I ran through the process again, and was finally able to
boot the resulting Clear Linux server. Thank you for helping me get to
this point.
One thing that stands out for me is that /etc is almost empty. It looks
like this system is as "barebone" as it gets, and that I am missing
some basic packages and configuration files (sshd_config among them).
9:09 p.m.
New subject: How to install on Hetzner CX cloud servers
* Arjan van de Ven:
the "man stateless" manual page tries to
explain this and lists a set
of common things... it's quite useful to get the idea of things at
least
I used that manual page as a reference, but unfortunately it contains a
mistake concerning sshd configuration.
Creating /etc/ssh/sshd_config and adding a "Port" entry, as is the usual
method and recommended on the manual page, does not work with the
current Clear Linux version.
Instead, one needs to override /usr/lib/systemd/system/sshd.socket by
creating /etc/systemd/system/sshd.socket and changing ListenStream
there. My thanks to Robert Nesius for pointing that method out to me.
-Ralph
11:48 p.m.
New subject: How to install on Hetzner CX cloud servers
On 3/31/20 6:09 PM, Ralph Seichter wrote:
* Arjan van de Ven:
Ralph,
`man stateless` contains the following *exact* text since before March 2017:
```
To modify the listening port of sshd, one needs to determine
whether sshd.socket or sshd.service is enabled first, since
the methods for changing the port number depend on whether
sshd(8) is controlling the port number, or whether systemd(1)
is:
systemctl is-enabled sshd.socket
If enabled, the sshd.socket unit should be edited to modify the
port:
systemctl edit --full sshd.socket
And, the user should modify the port number at ListenStream= to
the desired new port number.
If sshd.service is enabled, the user should create, and edit a
new /etc/ssh/sshd_config file:
mkdir -p /etc/ssh/ vi /etc/ssh/sshd_config
And add a line in that file that reads:
Port 10022
to, for instance, change the port number sshd.service will
listen on to port 10022.
```
If you still do see a problem, please open a github issue here:
https://github.com/clearlinux/clr-man-pages/issues
Auke
the "man stateless" manual page tries
to explain this and lists a set
of common things... it's quite useful to get the idea of things at
least
I used that manual page as a reference, but unfortunately it contains a
mistake concerning sshd configuration.
Creating /etc/ssh/sshd_config and adding a "Port" entry, as is the usual
method and recommended on the manual page, does not work with the
current Clear Linux version.
Instead, one needs to override /usr/lib/systemd/system/sshd.socket by
creating /etc/systemd/system/sshd.socket and changing ListenStream
there. My thanks to Robert Nesius for pointing that method out to me.
9:36 a.m.
New subject: How to install on Hetzner CX cloud servers
* Auke Kok:
systemctl is-enabled sshd.socket
If enabled, the sshd.socket unit should be edited to modify the port:
[...]
Please bear with me, I may have misunderstood what this test is supposed
to return:
$ systemctl is-enabled sshd.socket
static
Does this qualify as "enabled" in the above sense?
I want to emphasise that I am not looking for faults, real or perceived,
in Clear Linux. I am grateful for the support provided by you and other
mailing list members. If I miss something, or misunderstand, please just
let me know.
Thanks,
Ralph
1:05 a.m.
New subject: How to install on Hetzner CX cloud servers
On 4/1/20 6:36 AM, Ralph Seichter wrote:
* Auke Kok:
Huh
well, it was supposed to return `enabled` and I'm sure it did when I
wrote that 3+ years back, but, `static` isn't even what I'm getting
myself here now, which is `disabled` even though it is `enabled`.
This certainly therefore needs to be rectified in the manual page and
made to properly reflect the actual status here - which is that
sshd.socket is usually enabled by default in ClearLinux....
I best go fix that man page over the weekend now...
Auke
systemctl is-enabled sshd.socket
If enabled, the sshd.socket unit should be edited to modify the port:
[...]
Please bear with me, I may have misunderstood what this test is supposed
to return:
$ systemctl is-enabled sshd.socket
static
Does this qualify as "enabled" in the above sense?
I want to emphasise that I am not looking for faults, real or perceived,
in Clear Linux. I am grateful for the support provided by you and other
mailing list members. If I miss something, or misunderstand, please just
let me know.
1089
days inactive
1093
days old
10 comments
4 participants
participants (4)
-
Arjan van de Ven -
Auke Kok -
Nesius -
Ralph Seichter