Hier noch ein Test von DMZ / LAN und andersrum.
frank@frank-MS-7C37:~$ iperf3 -c 192.168.5.15 Connecting to host 192.168.5.15, port 5201 [ 5] local 192.168.3.213 port 44052 connected to 192.168.5.15 port 5201 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 114 MBytes 952 Mbits/sec 314 153 KBytes [ 5] 1.00-2.00 sec 112 MBytes 937 Mbits/sec 259 205 KBytes [ 5] 2.00-3.00 sec 111 MBytes 929 Mbits/sec 210 212 KBytes [ 5] 3.00-4.00 sec 111 MBytes 934 Mbits/sec 235 202 KBytes [ 5] 4.00-5.00 sec 112 MBytes 936 Mbits/sec 263 153 KBytes [ 5] 5.00-6.00 sec 111 MBytes 935 Mbits/sec 255 209 KBytes [ 5] 6.00-7.00 sec 112 MBytes 937 Mbits/sec 313 129 KBytes [ 5] 7.00-8.00 sec 111 MBytes 932 Mbits/sec 296 209 KBytes [ 5] 8.00-9.00 sec 111 MBytes 934 Mbits/sec 258 208 KBytes [ 5] 9.00-10.00 sec 111 MBytes 934 Mbits/sec 292 201 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.00 sec 1.09 GBytes 936 Mbits/sec 2695 sender [ 5] 0.00-10.00 sec 1.09 GBytes 935 Mbits/sec receiver iperf Done. frank@frank-MS-7C37:~$ iperf3 -R -c 192.168.5.15 Connecting to host 192.168.5.15, port 5201 Reverse mode, remote host 192.168.5.15 is sending [ 5] local 192.168.3.213 port 44058 connected to 192.168.5.15 port 5201 [ ID] Interval Transfer Bitrate [ 5] 0.00-1.00 sec 109 MBytes 911 Mbits/sec [ 5] 1.00-2.00 sec 109 MBytes 912 Mbits/sec [ 5] 2.00-3.00 sec 109 MBytes 912 Mbits/sec [ 5] 3.00-4.00 sec 109 MBytes 912 Mbits/sec [ 5] 4.00-5.00 sec 109 MBytes 912 Mbits/sec [ 5] 5.00-6.00 sec 108 MBytes 903 Mbits/sec [ 5] 6.00-7.00 sec 109 MBytes 912 Mbits/sec [ 5] 7.00-8.00 sec 109 MBytes 912 Mbits/sec [ 5] 8.00-9.00 sec 109 MBytes 912 Mbits/sec [ 5] 9.00-10.00 sec 109 MBytes 912 Mbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.00 sec 1.06 GBytes 913 Mbits/sec 114 sender [ 5] 0.00-10.00 sec 1.06 GBytes 911 Mbits/sec receiver iperf Done.Ansible - host_key_checking
-
Ich hatte ja hier etwas geparkt, heute Morgen mal was Ausführlicher. Es ging um
/etc/ansible/ansible.cfg
[defaults] host_key_checking = FalseIhr kennt das ja, wenn ihr einen neuen Server erstellt habt und dann Euch mit dem SSH-Key einloggen wollt, dann kommt immer diese Abfrage, die man mit Yes beantworten muss. Ok, ich deploye mal gerade einen frischen Server mittel Ansible und [hcloud](hcloud](https://github.com/hetznercloud/cli) in die Hetzner Cloud um Euch das zu zeigen.
Der Server hat automatisch meinen SSH-Key hinterlegt bekommen.
frank@debian:~$ ssh root@167.235.75.xxx The authenticity of host '167.235.75.xxx (167.235.75.xxx)' can't be established. ED25519 key fingerprint is SHA256:5ptOuOxxxxxxxxxxxxxxxxxxxxxxxx7CRqLykxzw0. This key is not known by any other names. Are you sure you want to continue connecting (yes/no/[fingerprint])? yes Warning: Permanently added '167.235.75.xxx' (ED25519) to the list of known hosts. Linux test-server 6.1.0-11-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.38-4 (2023-08-08) x86_64 The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. Last login: Sat Aug 26 06:31:52 2023 from 159.69.xx.xx root@test-server:~#Wenn man nun mittels Ansible und hcloud einen Server erstellt, meldet man sich danach auf diesem neu erstelltem Server an um ihn weiter zu konfigurieren. Um nun diesen Check da oben abzustellen, benötigt man den Eintrag in der ansible.cfg Vorher brach das Ansible Script immer mit einer Fehlermeldung ab.
-
F FrankM hat am auf dieses Thema verwiesen
-
-
-
-
-
-
Ubiquiti ER-X - iperf
Verschoben OpenWRT & Ubiquiti ER-X -
-