Création des droplets dans DO
This commit is contained in:
parent
afffbcfb82
commit
fa8e917ed0
1805
Clickhouse VM/config.xml
Normal file
1805
Clickhouse VM/config.xml
Normal file
File diff suppressed because it is too large
Load Diff
121
Clickhouse VM/users.xml
Normal file
121
Clickhouse VM/users.xml
Normal file
@ -0,0 +1,121 @@
|
|||||||
|
<clickhouse>
|
||||||
|
<!-- See also the files in users.d directory where the settings can be overridden. -->
|
||||||
|
|
||||||
|
<!-- Profiles of settings. -->
|
||||||
|
<profiles>
|
||||||
|
<!-- Default settings. -->
|
||||||
|
<default>
|
||||||
|
<!-- <async_insert>1</async_insert> -->
|
||||||
|
</default>
|
||||||
|
|
||||||
|
<!-- Profile that allows only read queries. -->
|
||||||
|
<readonly>
|
||||||
|
<readonly>1</readonly>
|
||||||
|
</readonly>
|
||||||
|
</profiles>
|
||||||
|
|
||||||
|
<!-- Users and ACL. -->
|
||||||
|
<users>
|
||||||
|
<!-- If user name was not specified, 'default' user is used. -->
|
||||||
|
<default>
|
||||||
|
<!-- See also the files in users.d directory where the password can be overridden.
|
||||||
|
|
||||||
|
Password could be specified in plaintext or in SHA256 (in hex format).
|
||||||
|
|
||||||
|
If you want to specify password in plaintext (not recommended), place it in 'password' element.
|
||||||
|
Example: <password>qwerty</password>.
|
||||||
|
Password could be empty.
|
||||||
|
|
||||||
|
If you want to specify SHA256, place it in 'password_sha256_hex' element.
|
||||||
|
Example: <password_sha256_hex>65e84be33532fb784c48129675f9eff3a682b27168c0ea744b2cf58ee02337c5</password_sha256_hex>
|
||||||
|
Restrictions of SHA256: impossibility to connect to ClickHouse using MySQL JS client (as of July 2019).
|
||||||
|
|
||||||
|
If you want to specify double SHA1, place it in 'password_double_sha1_hex' element.
|
||||||
|
Example: <password_double_sha1_hex>e395796d6546b1b65db9d665cd43f0e858dd4303</password_double_sha1_hex>
|
||||||
|
|
||||||
|
If you want to specify a previously defined LDAP server (see 'ldap_servers' in the main config) for authentication,
|
||||||
|
place its name in 'server' element inside 'ldap' element.
|
||||||
|
Example: <ldap><server>my_ldap_server</server></ldap>
|
||||||
|
|
||||||
|
If you want to authenticate the user via Kerberos (assuming Kerberos is enabled, see 'kerberos' in the main config),
|
||||||
|
place 'kerberos' element instead of 'password' (and similar) elements.
|
||||||
|
The name part of the canonical principal name of the initiator must match the user name for authentication to succeed.
|
||||||
|
You can also place 'realm' element inside 'kerberos' element to further restrict authentication to only those requests
|
||||||
|
whose initiator's realm matches it.
|
||||||
|
Example: <kerberos />
|
||||||
|
Example: <kerberos><realm>EXAMPLE.COM</realm></kerberos>
|
||||||
|
|
||||||
|
How to generate decent password:
|
||||||
|
Execute: PASSWORD=$(base64 < /dev/urandom | head -c8); echo "$PASSWORD"; echo -n "$PASSWORD" | sha256sum | tr -d '-'
|
||||||
|
In first line will be password and in second - corresponding SHA256.
|
||||||
|
|
||||||
|
How to generate double SHA1:
|
||||||
|
Execute: PASSWORD=$(base64 < /dev/urandom | head -c8); echo "$PASSWORD"; echo -n "$PASSWORD" | sha1sum | tr -d '-' | xxd -r -p | sha1sum | tr -d '-'
|
||||||
|
In first line will be password and in second - corresponding double SHA1.
|
||||||
|
-->
|
||||||
|
<password>F4stCharge</password>
|
||||||
|
|
||||||
|
<!-- List of networks with open access.
|
||||||
|
|
||||||
|
To open access from everywhere, specify:
|
||||||
|
<ip>::/0</ip>
|
||||||
|
|
||||||
|
To open access only from localhost, specify:
|
||||||
|
<ip>::1</ip>
|
||||||
|
<ip>127.0.0.1</ip>
|
||||||
|
|
||||||
|
Each element of list has one of the following forms:
|
||||||
|
<ip> IP-address or network mask. Examples: 213.180.204.3 or 10.0.0.1/8 or 10.0.0.1/255.255.255.0
|
||||||
|
2a02:6b8::3 or 2a02:6b8::3/64 or 2a02:6b8::3/ffff:ffff:ffff:ffff::.
|
||||||
|
<host> Hostname. Example: server01.clickhouse.com.
|
||||||
|
To check access, DNS query is performed, and all received addresses compared to peer address.
|
||||||
|
<host_regexp> Regular expression for host names. Example, ^server\d\d-\d\d-\d\.clickhouse\.com$
|
||||||
|
To check access, DNS PTR query is performed for peer address and then regexp is applied.
|
||||||
|
Then, for result of PTR query, another DNS query is performed and all received addresses compared to peer address.
|
||||||
|
Strongly recommended that regexp is ends with $
|
||||||
|
All results of DNS requests are cached till server restart.
|
||||||
|
-->
|
||||||
|
<networks>
|
||||||
|
<ip>::/0</ip>
|
||||||
|
</networks>
|
||||||
|
|
||||||
|
<!-- Settings profile for user. -->
|
||||||
|
<profile>default</profile>
|
||||||
|
|
||||||
|
<!-- Quota for user. -->
|
||||||
|
<quota>default</quota>
|
||||||
|
|
||||||
|
<!-- User can create other users and grant rights to them. -->
|
||||||
|
<access_management>1</access_management>
|
||||||
|
|
||||||
|
<!-- User can manipulate named collections. -->
|
||||||
|
<named_collection_control>1</named_collection_control>
|
||||||
|
|
||||||
|
<!-- User permissions can be granted here -->
|
||||||
|
<!--
|
||||||
|
<grants>
|
||||||
|
<query>GRANT ALL ON *.*</query>
|
||||||
|
</grants>
|
||||||
|
-->
|
||||||
|
</default>
|
||||||
|
</users>
|
||||||
|
|
||||||
|
<!-- Quotas. -->
|
||||||
|
<quotas>
|
||||||
|
<!-- Name of quota. -->
|
||||||
|
<default>
|
||||||
|
<!-- Limits for time interval. You could specify many intervals with different limits. -->
|
||||||
|
<interval>
|
||||||
|
<!-- Length of interval. -->
|
||||||
|
<duration>3600</duration>
|
||||||
|
|
||||||
|
<!-- No limits. Just calculate resource usage for time interval. -->
|
||||||
|
<queries>0</queries>
|
||||||
|
<errors>0</errors>
|
||||||
|
<result_rows>0</result_rows>
|
||||||
|
<read_rows>0</read_rows>
|
||||||
|
<execution_time>0</execution_time>
|
||||||
|
</interval>
|
||||||
|
</default>
|
||||||
|
</quotas>
|
||||||
|
</clickhouse>
|
||||||
Binary file not shown.
269
OpenVPN/ka2501.ovpn
Normal file
269
OpenVPN/ka2501.ovpn
Normal file
@ -0,0 +1,269 @@
|
|||||||
|
##############################################
|
||||||
|
# Sample client-side OpenVPN 2.0 config file #
|
||||||
|
# for connecting to multi-client server. #
|
||||||
|
# #
|
||||||
|
# This configuration can be used by multiple #
|
||||||
|
# clients, however each client should have #
|
||||||
|
# its own cert and key files. #
|
||||||
|
# #
|
||||||
|
# On Windows, you might want to rename this #
|
||||||
|
# file so it has a .ovpn extension #
|
||||||
|
##############################################
|
||||||
|
|
||||||
|
# Specify that we are a client and that we
|
||||||
|
# will be pulling certain config file directives
|
||||||
|
# from the server.
|
||||||
|
client
|
||||||
|
|
||||||
|
# Use the same setting as you are using on
|
||||||
|
# the server.
|
||||||
|
# On most systems, the VPN will not function
|
||||||
|
# unless you partially or fully disable
|
||||||
|
# the firewall for the TUN/TAP interface.
|
||||||
|
;dev tap
|
||||||
|
dev tun
|
||||||
|
|
||||||
|
# Windows needs the TAP-Win32 adapter name
|
||||||
|
# from the Network Connections panel
|
||||||
|
# if you have more than one. On XP SP2,
|
||||||
|
# you may need to disable the firewall
|
||||||
|
# for the TAP adapter.
|
||||||
|
;dev-node MyTap
|
||||||
|
|
||||||
|
# Are we connecting to a TCP or
|
||||||
|
# UDP server? Use the same setting as
|
||||||
|
# on the server.
|
||||||
|
;proto tcp
|
||||||
|
proto udp
|
||||||
|
|
||||||
|
# The hostname/IP and port of the server.
|
||||||
|
# You can have multiple remote entries
|
||||||
|
# to load balance between the servers.
|
||||||
|
remote vpn.yultek.dev 1194
|
||||||
|
;remote 138.197.151.172 1194
|
||||||
|
;remote my-server-2 1194
|
||||||
|
|
||||||
|
# Choose a random host from the remote
|
||||||
|
# list for load-balancing. Otherwise
|
||||||
|
# try hosts in the order specified.
|
||||||
|
;remote-random
|
||||||
|
|
||||||
|
# Keep trying indefinitely to resolve the
|
||||||
|
# host name of the OpenVPN server. Very useful
|
||||||
|
# on machines which are not permanently connected
|
||||||
|
# to the internet such as laptops.
|
||||||
|
resolv-retry infinite
|
||||||
|
|
||||||
|
# Most clients don't need to bind to
|
||||||
|
# a specific local port number.
|
||||||
|
nobind
|
||||||
|
|
||||||
|
# Downgrade privileges after initialization (non-Windows only)
|
||||||
|
;user nobody
|
||||||
|
;group nobody
|
||||||
|
|
||||||
|
# Try to preserve some state across restarts.
|
||||||
|
persist-key
|
||||||
|
persist-tun
|
||||||
|
|
||||||
|
# If you are connecting through an
|
||||||
|
# HTTP proxy to reach the actual OpenVPN
|
||||||
|
# server, put the proxy server/IP and
|
||||||
|
# port number here. See the man page
|
||||||
|
# if your proxy server requires
|
||||||
|
# authentication.
|
||||||
|
;http-proxy-retry # retry on connection failures
|
||||||
|
;http-proxy [proxy server] [proxy port #]
|
||||||
|
|
||||||
|
# Wireless networks often produce a lot
|
||||||
|
# of duplicate packets. Set this flag
|
||||||
|
# to silence duplicate packet warnings.
|
||||||
|
;mute-replay-warnings
|
||||||
|
|
||||||
|
# SSL/TLS parms.
|
||||||
|
# See the server config file for more
|
||||||
|
# description. It's best to use
|
||||||
|
# a separate .crt/.key file pair
|
||||||
|
# for each client. A single ca
|
||||||
|
# file can be used for all clients.
|
||||||
|
;ca ca.crt
|
||||||
|
;cert client.crt
|
||||||
|
;key client.key
|
||||||
|
|
||||||
|
# Verify server certificate by checking that the
|
||||||
|
# certificate has the correct key usage set.
|
||||||
|
# This is an important precaution to protect against
|
||||||
|
# a potential attack discussed here:
|
||||||
|
# http://openvpn.net/howto.html#mitm
|
||||||
|
#
|
||||||
|
# To use this feature, you will need to generate
|
||||||
|
# your server certificates with the keyUsage set to
|
||||||
|
# digitalSignature, keyEncipherment
|
||||||
|
# and the extendedKeyUsage to
|
||||||
|
# serverAuth
|
||||||
|
# EasyRSA can do this for you.
|
||||||
|
remote-cert-tls server
|
||||||
|
|
||||||
|
# If a tls-auth key is used on the server
|
||||||
|
# then every client must also have the key.
|
||||||
|
;tls-auth ta.key 1
|
||||||
|
|
||||||
|
# Select a cryptographic cipher.
|
||||||
|
# If the cipher option is used on the server
|
||||||
|
# then you must also specify it here.
|
||||||
|
# Note that v2.4 client/server will automatically
|
||||||
|
# negotiate AES-256-GCM in TLS mode.
|
||||||
|
# See also the data-ciphers option in the manpage
|
||||||
|
cipher AES-256-GCM
|
||||||
|
auth SHA256
|
||||||
|
|
||||||
|
# Enable compression on the VPN link.
|
||||||
|
# Don't enable this unless it is also
|
||||||
|
# enabled in the server config file.
|
||||||
|
#comp-lzo
|
||||||
|
|
||||||
|
# Set log file verbosity.
|
||||||
|
verb 3
|
||||||
|
|
||||||
|
# Silence repeating messages
|
||||||
|
;mute 20
|
||||||
|
|
||||||
|
key-direction 1
|
||||||
|
|
||||||
|
|
||||||
|
; script-security 2
|
||||||
|
; up /etc/openvpn/update-resolv-conf
|
||||||
|
; down /etc/openvpn/update-resolv-conf
|
||||||
|
|
||||||
|
|
||||||
|
; script-security 2
|
||||||
|
; up /etc/openvpn/update-systemd-resolved
|
||||||
|
; down /etc/openvpn/update-systemd-resolved
|
||||||
|
; down-pre
|
||||||
|
; dhcp-option DOMAIN-ROUTE .
|
||||||
|
<ca>
|
||||||
|
-----BEGIN CERTIFICATE-----
|
||||||
|
MIIDRTCCAi2gAwIBAgIUXe37kz2yqgyL2xXfvaGRzlz7ywYwDQYJKoZIhvcNAQEL
|
||||||
|
BQAwFDESMBAGA1UEAwwJSkZfc2VydmVyMB4XDTIzMDIyMDIyMDkyMVoXDTMzMDIx
|
||||||
|
NzIyMDkyMVowFDESMBAGA1UEAwwJSkZfc2VydmVyMIIBIjANBgkqhkiG9w0BAQEF
|
||||||
|
AAOCAQ8AMIIBCgKCAQEAnLdVAj0W31TtWGxwdBeqsdIHyUdVAEG8bX+CcNZDP3M3
|
||||||
|
R/gJOmenjqsqHYBe5gZcky1hkqWaD7l/LNmyzZDZ1lVEWpcAZqxbsUZKiHU30bxq
|
||||||
|
84L5qtaAOpwTsumidq2hBqoDBMdBmh18e0QEW624mui7ckXTRRG3PA0ccXtXcTYU
|
||||||
|
ntmhYtQ2oaPauSmfJZIUfZTfVZbB8FkCgu+zJtCx5hq46vIHm8KX0m1zLIeUtGsI
|
||||||
|
hkly+5v52f3sEMlddyoZZkfjRddETk2co09q3oNaP1LYxN5G+TvZDhpdE+PrDsNT
|
||||||
|
wO4uU2d9hVIP3T49heLieZ6KVxyp1FsDYzo0CNlIDwIDAQABo4GOMIGLMB0GA1Ud
|
||||||
|
DgQWBBSKeJDl8FDnjHXkuMCh6OmbshqdMjBPBgNVHSMESDBGgBSKeJDl8FDnjHXk
|
||||||
|
uMCh6OmbshqdMqEYpBYwFDESMBAGA1UEAwwJSkZfc2VydmVyghRd7fuTPbKqDIvb
|
||||||
|
Fd+9oZHOXPvLBjAMBgNVHRMEBTADAQH/MAsGA1UdDwQEAwIBBjANBgkqhkiG9w0B
|
||||||
|
AQsFAAOCAQEARIg2x4Tit/6ZydMlle6ku32t75OMCVQoe7fUkRjNe8pCkZjZXLy9
|
||||||
|
QIRwoqW3FRT8+mQjctZk3NsyLStF8Rc/fFvpjGY/hiEQ/RV1K2/IZ9hcswp/LRzQ
|
||||||
|
ElDwXhe4zlcDT10GjHYYx221SR+ijgicZcaXgb9f3uZKIrPgyb8qB4KCQS8gPtCV
|
||||||
|
1VmPM5/svVCI93G+xT92XBHa47fgV5GEn7Snah2UgFol5h7/KX/Sa2q0pfBlzqmt
|
||||||
|
CutfEbYcwSxkoLsEUIW8KMoEAIsO+KIsraS6EXlRdT82Ui+UZWVPZABlzifCl+AV
|
||||||
|
LzBrLwt2OeoEI1h65EyzzE7gDsjrE3JR/Q==
|
||||||
|
-----END CERTIFICATE-----
|
||||||
|
</ca>
|
||||||
|
<cert>
|
||||||
|
Certificate:
|
||||||
|
Data:
|
||||||
|
Version: 3 (0x2)
|
||||||
|
Serial Number:
|
||||||
|
b1:a6:3d:e9:86:99:a3:9a:13:71:db:4b:3e:64:97:1e
|
||||||
|
Signature Algorithm: sha512WithRSAEncryption
|
||||||
|
Issuer: CN=JF_server
|
||||||
|
Validity
|
||||||
|
Not Before: May 13 19:49:03 2025 GMT
|
||||||
|
Not After : Mar 22 19:49:03 2035 GMT
|
||||||
|
Subject: CN=ka2501
|
||||||
|
Subject Public Key Info:
|
||||||
|
Public Key Algorithm: id-ecPublicKey
|
||||||
|
Public-Key: (384 bit)
|
||||||
|
pub:
|
||||||
|
04:d0:ce:53:7c:45:90:12:64:5a:74:2b:51:32:0e:
|
||||||
|
58:dc:c0:71:82:2d:ba:4a:75:93:b5:57:f1:9a:54:
|
||||||
|
b5:79:3b:67:01:e3:8a:9f:fa:20:82:fc:74:b0:ba:
|
||||||
|
de:71:75:8d:d4:a6:cd:59:b9:46:40:bd:08:fc:c4:
|
||||||
|
e3:53:26:57:7f:11:f1:f8:d8:7e:0a:45:1d:f4:23:
|
||||||
|
d9:25:9b:7c:ac:63:d4:7a:b0:27:80:cb:20:e5:2f:
|
||||||
|
e4:fb:21:2f:56:12:4f
|
||||||
|
ASN1 OID: secp384r1
|
||||||
|
NIST CURVE: P-384
|
||||||
|
X509v3 extensions:
|
||||||
|
X509v3 Basic Constraints:
|
||||||
|
CA:FALSE
|
||||||
|
X509v3 Subject Key Identifier:
|
||||||
|
52:EC:0F:6C:38:BD:9A:F2:07:76:03:02:5C:A2:5D:E9:45:51:77:D0
|
||||||
|
X509v3 Authority Key Identifier:
|
||||||
|
keyid:8A:78:90:E5:F0:50:E7:8C:75:E4:B8:C0:A1:E8:E9:9B:B2:1A:9D:32
|
||||||
|
DirName:/CN=JF_server
|
||||||
|
serial:5D:ED:FB:93:3D:B2:AA:0C:8B:DB:15:DF:BD:A1:91:CE:5C:FB:CB:06
|
||||||
|
X509v3 Extended Key Usage:
|
||||||
|
TLS Web Client Authentication
|
||||||
|
X509v3 Key Usage:
|
||||||
|
Digital Signature
|
||||||
|
Signature Algorithm: sha512WithRSAEncryption
|
||||||
|
Signature Value:
|
||||||
|
69:06:93:7e:7c:88:68:5b:3a:b9:7c:3c:d2:ae:43:5e:5f:aa:
|
||||||
|
cf:9b:f9:8e:58:ff:93:3d:5f:07:d4:26:c4:c0:18:a9:46:88:
|
||||||
|
1e:8d:75:32:f7:58:ea:e5:b0:39:40:e9:a0:fc:a6:a2:19:20:
|
||||||
|
e2:dd:88:3a:4c:4c:ba:00:a0:77:da:99:41:0c:49:e1:ef:07:
|
||||||
|
4c:69:52:80:9e:e0:bc:44:a8:e8:03:45:91:94:d5:b3:90:66:
|
||||||
|
67:09:55:8d:20:cf:8f:df:c0:8e:54:17:db:6a:9d:b3:a3:ce:
|
||||||
|
b9:38:c5:86:72:46:87:b8:86:c7:ca:36:75:49:01:81:07:da:
|
||||||
|
7b:6d:92:89:73:88:c7:51:36:e1:78:65:be:b5:45:51:b8:04:
|
||||||
|
a7:1c:88:03:ba:48:4f:e3:b9:eb:e2:4c:0a:5f:1c:57:3b:f6:
|
||||||
|
c7:e9:ba:c7:c3:b0:2c:a7:b2:19:e0:9f:ff:c4:c3:66:03:65:
|
||||||
|
44:10:37:48:96:80:4a:95:ea:2e:31:57:64:eb:ad:85:ab:09:
|
||||||
|
1d:87:a7:0d:0f:99:69:8d:9e:ee:d8:9a:7a:2d:3d:a1:f9:61:
|
||||||
|
90:cc:ba:c4:eb:f8:e5:c8:fc:b0:11:b6:d6:3a:d9:ee:2d:fb:
|
||||||
|
0e:98:0a:71:51:89:c3:97:34:35:00:8f:77:0f:91:15:39:52:
|
||||||
|
8f:72:4f:7d
|
||||||
|
-----BEGIN CERTIFICATE-----
|
||||||
|
MIICozCCAYugAwIBAgIRALGmPemGmaOaE3HbSz5klx4wDQYJKoZIhvcNAQENBQAw
|
||||||
|
FDESMBAGA1UEAwwJSkZfc2VydmVyMB4XDTI1MDUxMzE5NDkwM1oXDTM1MDMyMjE5
|
||||||
|
NDkwM1owETEPMA0GA1UEAwwGa2EyNTAxMHYwEAYHKoZIzj0CAQYFK4EEACIDYgAE
|
||||||
|
0M5TfEWQEmRadCtRMg5Y3MBxgi26SnWTtVfxmlS1eTtnAeOKn/oggvx0sLrecXWN
|
||||||
|
1KbNWblGQL0I/MTjUyZXfxHx+Nh+CkUd9CPZJZt8rGPUerAngMsg5S/k+yEvVhJP
|
||||||
|
o4GgMIGdMAkGA1UdEwQCMAAwHQYDVR0OBBYEFFLsD2w4vZryB3YDAlyiXelFUXfQ
|
||||||
|
ME8GA1UdIwRIMEaAFIp4kOXwUOeMdeS4wKHo6ZuyGp0yoRikFjAUMRIwEAYDVQQD
|
||||||
|
DAlKRl9zZXJ2ZXKCFF3t+5M9sqoMi9sV372hkc5c+8sGMBMGA1UdJQQMMAoGCCsG
|
||||||
|
AQUFBwMCMAsGA1UdDwQEAwIHgDANBgkqhkiG9w0BAQ0FAAOCAQEAaQaTfnyIaFs6
|
||||||
|
uXw80q5DXl+qz5v5jlj/kz1fB9QmxMAYqUaIHo11MvdY6uWwOUDpoPymohkg4t2I
|
||||||
|
OkxMugCgd9qZQQxJ4e8HTGlSgJ7gvESo6ANFkZTVs5BmZwlVjSDPj9/AjlQX22qd
|
||||||
|
s6POuTjFhnJGh7iGx8o2dUkBgQfae22SiXOIx1E24XhlvrVFUbgEpxyIA7pIT+O5
|
||||||
|
6+JMCl8cVzv2x+m6x8OwLKeyGeCf/8TDZgNlRBA3SJaASpXqLjFXZOuthasJHYen
|
||||||
|
DQ+ZaY2e7tiaei09oflhkMy6xOv45cj8sBG21jrZ7i37DpgKcVGJw5c0NQCPdw+R
|
||||||
|
FTlSj3JPfQ==
|
||||||
|
-----END CERTIFICATE-----
|
||||||
|
</cert>
|
||||||
|
<key>
|
||||||
|
-----BEGIN PRIVATE KEY-----
|
||||||
|
MIG2AgEAMBAGByqGSM49AgEGBSuBBAAiBIGeMIGbAgEBBDCyRf14oFnDf92ZVzpH
|
||||||
|
atELaV1d2kNCpBtUko5EjiAaXQaK/HKuPoGwd5UoKzR+iF6hZANiAATQzlN8RZAS
|
||||||
|
ZFp0K1EyDljcwHGCLbpKdZO1V/GaVLV5O2cB44qf+iCC/HSwut5xdY3Ups1ZuUZA
|
||||||
|
vQj8xONTJld/EfH42H4KRR30I9klm3ysY9R6sCeAyyDlL+T7IS9WEk8=
|
||||||
|
-----END PRIVATE KEY-----
|
||||||
|
</key>
|
||||||
|
<tls-crypt>
|
||||||
|
#
|
||||||
|
# 2048 bit OpenVPN static key
|
||||||
|
#
|
||||||
|
-----BEGIN OpenVPN Static key V1-----
|
||||||
|
4c828cbf0e58f927758e9471c1b6f03b
|
||||||
|
2e77b2c634bad76df0570dd8f47184d6
|
||||||
|
3921e25c6e6cbe4af4b64aad89d12425
|
||||||
|
a9fca69ae08802b5ed583632c26678b0
|
||||||
|
cc28c481c3831d1b2204dc30cd466395
|
||||||
|
ccb8cd82cd2259c956b510c9a56e842a
|
||||||
|
8693c44dca462f0ab7be3856abe9bbe1
|
||||||
|
95a6ffd3b0237225b9497c7a0df05ad8
|
||||||
|
2f2e0a8bff97c927d2890906d0105947
|
||||||
|
fa3430fc779583772382534fb880add6
|
||||||
|
8d5592fa4ff384d3e96c560019b5835f
|
||||||
|
095da9b2fb33dbfbc1ffce9560908271
|
||||||
|
ee96e02ccecc9d51b9dda79a77704a1d
|
||||||
|
4407d7c805e6950854fe232adee02a12
|
||||||
|
b09af2d9bfe04868a9e2e942dc64eb81
|
||||||
|
9e062ab9f781e52d263195a58db72ebe
|
||||||
|
-----END OpenVPN Static key V1-----
|
||||||
|
</tls-crypt>
|
||||||
Binary file not shown.
@ -1988,3 +1988,177 @@ Démarrage du logiciel Otarcik CAN version 1.08 le 2025-05-08 à 13:37:29
|
|||||||
2025-05-08 13:38:34 Client MQTT metrics.yultek.dev déconnecté.
|
2025-05-08 13:38:34 Client MQTT metrics.yultek.dev déconnecté.
|
||||||
2025-05-08 13:38:34 Passage en mode buffering des messages MQTT pour metrics.yultek.dev
|
2025-05-08 13:38:34 Passage en mode buffering des messages MQTT pour metrics.yultek.dev
|
||||||
2025-05-08 13:38:34 Client MQTT 192.168.51.32 déconnecté.
|
2025-05-08 13:38:34 Client MQTT 192.168.51.32 déconnecté.
|
||||||
|
|
||||||
|
|
||||||
|
********************************************************************
|
||||||
|
Démarrage du logiciel Otarcik CAN version 1.08 le 2025-05-16 à 12:15:05
|
||||||
|
********************************************************************
|
||||||
|
2025-05-16 12:15:05 Chargement de la configuration système...
|
||||||
|
2025-05-16 12:15:05 Configuration système chargée avec succès!
|
||||||
|
2025-05-16 12:15:05 Initialisation du dispositif [MasterCAN]
|
||||||
|
2025-05-16 12:15:05 Démarrage d'un module CAN...
|
||||||
|
2025-05-16 12:15:05 Impossible de trouver le module CAN sur le channel 1
|
||||||
|
2025-05-16 12:15:05 Démarrage du Watchdog CAN...
|
||||||
|
2025-05-16 12:15:05 Watchdog CAN initialisé pour le module sur le channel 1
|
||||||
|
2025-05-16 12:15:05 Démarrage du logiciel OtarcikCAN
|
||||||
|
2025-05-16 12:15:05 Client MQTT metrics.yultek.dev en cours de connexion...
|
||||||
|
2025-05-16 12:15:05 Client MQTT 192.168.51.32 en cours de connexion...
|
||||||
|
2025-05-16 12:15:05 LAN Device 192.168.51.2 is now ONLINE on network
|
||||||
|
2025-05-16 12:15:05 LAN Device 192.168.50.100 is now ONLINE on network
|
||||||
|
2025-05-16 12:15:05 LAN Device 192.168.50.1 is now ONLINE on network
|
||||||
|
2025-05-16 12:15:05 LAN Device 192.168.51.32 is now ONLINE on network
|
||||||
|
2025-05-16 12:15:05 LAN Device 192.168.50.110 is now ONLINE on network
|
||||||
|
2025-05-16 12:15:05 Client MQTT 192.168.51.32 connecté.
|
||||||
|
2025-05-16 12:15:05 Client MQTT metrics.yultek.dev connecté.
|
||||||
|
2025-05-16 12:15:05 Internet Connecté...
|
||||||
|
2025-05-16 12:18:35 Client MQTT metrics.yultek.dev déconnecté.
|
||||||
|
2025-05-16 12:18:35 Passage en mode buffering des messages MQTT pour metrics.yultek.dev
|
||||||
|
2025-05-16 12:18:35 Client MQTT 192.168.51.32 déconnecté.
|
||||||
|
2025-05-16 12:18:35 Client MQTT metrics.yultek.dev en cours de connexion...
|
||||||
|
2025-05-16 12:18:35 Client MQTT 142.93.152.2 en cours de connexion...
|
||||||
|
2025-05-16 12:18:35 Sauvegarde de la configuration système...
|
||||||
|
2025-05-16 12:18:35 Client MQTT 142.93.152.2 connecté.
|
||||||
|
2025-05-16 12:18:35 Client MQTT metrics.yultek.dev connecté.
|
||||||
|
2025-05-16 12:18:57 Client MQTT metrics.yultek.dev déconnecté.
|
||||||
|
2025-05-16 12:18:57 Passage en mode buffering des messages MQTT pour metrics.yultek.dev
|
||||||
|
2025-05-16 12:18:57 Client MQTT 142.93.152.2 déconnecté.
|
||||||
|
2025-05-16 12:18:57 Client MQTT metrics.yultek.dev en cours de connexion...
|
||||||
|
2025-05-16 12:18:57 Client MQTT 142.93.152.2 en cours de connexion...
|
||||||
|
2025-05-16 12:18:57 Sauvegarde de la configuration système...
|
||||||
|
2025-05-16 12:18:57 Client MQTT 142.93.152.2 connecté.
|
||||||
|
2025-05-16 12:18:57 Client MQTT metrics.yultek.dev connecté.
|
||||||
|
2025-05-16 12:19:27 Déinitialisation du module PCAN USB ID 81
|
||||||
|
2025-05-16 12:19:27 Impossible de déinitialiser un module USB PCAN.. Error:The transmit buffer in CAN controller is full
|
||||||
|
2025-05-16 12:19:27 Client MQTT metrics.yultek.dev déconnecté.
|
||||||
|
2025-05-16 12:19:27 Passage en mode buffering des messages MQTT pour metrics.yultek.dev
|
||||||
|
2025-05-16 12:19:27 Client MQTT 142.93.152.2 déconnecté.
|
||||||
|
|
||||||
|
|
||||||
|
********************************************************************
|
||||||
|
Démarrage du logiciel Otarcik CAN version 1.08 le 2025-05-16 à 12:38:45
|
||||||
|
********************************************************************
|
||||||
|
2025-05-16 12:38:45 Chargement de la configuration système...
|
||||||
|
2025-05-16 12:38:45 Configuration système chargée avec succès!
|
||||||
|
2025-05-16 12:38:45 Initialisation du dispositif [MasterCAN]
|
||||||
|
2025-05-16 12:38:45 Démarrage d'un module CAN...
|
||||||
|
2025-05-16 12:38:45 Impossible de trouver le module CAN sur le channel 1
|
||||||
|
2025-05-16 12:38:45 Démarrage du Watchdog CAN...
|
||||||
|
2025-05-16 12:38:45 Watchdog CAN initialisé pour le module sur le channel 1
|
||||||
|
2025-05-16 12:38:45 Démarrage du logiciel OtarcikCAN
|
||||||
|
2025-05-16 12:38:45 Client MQTT metrics.yultek.dev en cours de connexion...
|
||||||
|
2025-05-16 12:38:45 Client MQTT 142.93.152.2 en cours de connexion...
|
||||||
|
2025-05-16 12:38:45 LAN Device 192.168.51.2 is now ONLINE on network
|
||||||
|
2025-05-16 12:38:45 LAN Device 192.168.50.100 is now ONLINE on network
|
||||||
|
2025-05-16 12:38:45 LAN Device 192.168.50.1 is now ONLINE on network
|
||||||
|
2025-05-16 12:38:45 LAN Device 192.168.51.32 is now ONLINE on network
|
||||||
|
2025-05-16 12:38:45 LAN Device 192.168.50.110 is now ONLINE on network
|
||||||
|
2025-05-16 12:38:45 Client MQTT 142.93.152.2 connecté.
|
||||||
|
2025-05-16 12:38:45 Client MQTT metrics.yultek.dev connecté.
|
||||||
|
2025-05-16 12:38:45 Internet Connecté...
|
||||||
|
2025-05-16 13:32:35 Client MQTT 142.93.152.2 déconnecté.
|
||||||
|
2025-05-16 13:32:45 Tentative de connexion au serveur MQTT...
|
||||||
|
2025-05-16 13:32:45 Client MQTT 142.93.152.2 en cours de connexion...
|
||||||
|
2025-05-16 13:32:49 Client MQTT 142.93.152.2 déconnecté pendant une reconnexion.
|
||||||
|
2025-05-16 13:32:59 Tentative de connexion au serveur MQTT...
|
||||||
|
2025-05-16 13:32:59 Client MQTT 142.93.152.2 en cours de connexion...
|
||||||
|
2025-05-16 13:33:03 Client MQTT 142.93.152.2 déconnecté pendant une reconnexion.
|
||||||
|
2025-05-16 13:33:13 Tentative de connexion au serveur MQTT...
|
||||||
|
2025-05-16 13:33:13 Client MQTT 142.93.152.2 en cours de connexion...
|
||||||
|
2025-05-16 13:33:17 Client MQTT 142.93.152.2 déconnecté pendant une reconnexion.
|
||||||
|
2025-05-16 13:33:27 Tentative de connexion au serveur MQTT...
|
||||||
|
2025-05-16 13:33:27 Client MQTT 142.93.152.2 en cours de connexion...
|
||||||
|
2025-05-16 13:33:32 Client MQTT 142.93.152.2 déconnecté pendant une reconnexion.
|
||||||
|
2025-05-16 13:33:42 Tentative de connexion au serveur MQTT...
|
||||||
|
2025-05-16 13:33:42 Client MQTT 142.93.152.2 en cours de connexion...
|
||||||
|
2025-05-16 13:33:46 Client MQTT 142.93.152.2 déconnecté pendant une reconnexion.
|
||||||
|
2025-05-16 13:33:56 Tentative de connexion au serveur MQTT...
|
||||||
|
2025-05-16 13:33:56 Client MQTT 142.93.152.2 en cours de connexion...
|
||||||
|
2025-05-16 13:34:00 Client MQTT 142.93.152.2 déconnecté pendant une reconnexion.
|
||||||
|
2025-05-16 13:34:10 Tentative de connexion au serveur MQTT...
|
||||||
|
2025-05-16 13:34:10 Client MQTT 142.93.152.2 en cours de connexion...
|
||||||
|
2025-05-16 13:34:14 Client MQTT 142.93.152.2 déconnecté pendant une reconnexion.
|
||||||
|
2025-05-16 13:34:24 Tentative de connexion au serveur MQTT...
|
||||||
|
2025-05-16 13:34:24 Client MQTT 142.93.152.2 en cours de connexion...
|
||||||
|
2025-05-16 13:34:29 Client MQTT 142.93.152.2 déconnecté pendant une reconnexion.
|
||||||
|
2025-05-16 13:34:39 Tentative de connexion au serveur MQTT...
|
||||||
|
2025-05-16 13:34:39 Client MQTT 142.93.152.2 en cours de connexion...
|
||||||
|
2025-05-16 13:34:43 Client MQTT 142.93.152.2 déconnecté pendant une reconnexion.
|
||||||
|
2025-05-16 13:34:53 Tentative de connexion au serveur MQTT...
|
||||||
|
2025-05-16 13:34:53 Client MQTT 142.93.152.2 en cours de connexion...
|
||||||
|
2025-05-16 13:34:57 Client MQTT 142.93.152.2 déconnecté pendant une reconnexion.
|
||||||
|
2025-05-16 13:35:07 Tentative de connexion au serveur MQTT...
|
||||||
|
2025-05-16 13:35:07 Client MQTT 142.93.152.2 en cours de connexion...
|
||||||
|
2025-05-16 13:35:11 Client MQTT 142.93.152.2 déconnecté pendant une reconnexion.
|
||||||
|
2025-05-16 13:35:21 Tentative de connexion au serveur MQTT...
|
||||||
|
2025-05-16 13:35:21 Client MQTT 142.93.152.2 en cours de connexion...
|
||||||
|
2025-05-16 13:35:26 Client MQTT 142.93.152.2 déconnecté pendant une reconnexion.
|
||||||
|
2025-05-16 13:35:36 Tentative de connexion au serveur MQTT...
|
||||||
|
2025-05-16 13:35:36 Client MQTT 142.93.152.2 en cours de connexion...
|
||||||
|
2025-05-16 13:35:40 Client MQTT 142.93.152.2 déconnecté pendant une reconnexion.
|
||||||
|
2025-05-16 13:35:50 Tentative de connexion au serveur MQTT...
|
||||||
|
2025-05-16 13:35:50 Client MQTT 142.93.152.2 en cours de connexion...
|
||||||
|
2025-05-16 13:35:52 Client MQTT 142.93.152.2 connecté.
|
||||||
|
2025-05-16 13:38:07 Client MQTT 142.93.152.2 déconnecté.
|
||||||
|
2025-05-16 13:38:17 Tentative de connexion au serveur MQTT...
|
||||||
|
2025-05-16 13:38:17 Client MQTT 142.93.152.2 en cours de connexion...
|
||||||
|
2025-05-16 13:38:21 Client MQTT 142.93.152.2 connecté.
|
||||||
|
2025-05-16 13:40:31 Client MQTT 142.93.152.2 déconnecté.
|
||||||
|
2025-05-16 13:40:41 Tentative de connexion au serveur MQTT...
|
||||||
|
2025-05-16 13:40:41 Client MQTT 142.93.152.2 en cours de connexion...
|
||||||
|
2025-05-16 13:40:45 Client MQTT 142.93.152.2 connecté.
|
||||||
|
2025-05-16 13:40:45 Client MQTT 142.93.152.2 déconnecté.
|
||||||
|
2025-05-16 13:40:55 Tentative de connexion au serveur MQTT...
|
||||||
|
2025-05-16 13:40:55 Client MQTT 142.93.152.2 en cours de connexion...
|
||||||
|
2025-05-16 13:40:59 Client MQTT 142.93.152.2 déconnecté pendant une reconnexion.
|
||||||
|
2025-05-16 13:41:09 Tentative de connexion au serveur MQTT...
|
||||||
|
2025-05-16 13:41:09 Client MQTT 142.93.152.2 en cours de connexion...
|
||||||
|
2025-05-16 13:41:13 Client MQTT 142.93.152.2 déconnecté pendant une reconnexion.
|
||||||
|
2025-05-16 13:41:23 Tentative de connexion au serveur MQTT...
|
||||||
|
2025-05-16 13:41:23 Client MQTT 142.93.152.2 en cours de connexion...
|
||||||
|
2025-05-16 13:41:28 Client MQTT 142.93.152.2 déconnecté pendant une reconnexion.
|
||||||
|
2025-05-16 13:41:38 Tentative de connexion au serveur MQTT...
|
||||||
|
2025-05-16 13:41:38 Client MQTT 142.93.152.2 en cours de connexion...
|
||||||
|
2025-05-16 13:41:42 Client MQTT 142.93.152.2 déconnecté pendant une reconnexion.
|
||||||
|
2025-05-16 13:41:52 Tentative de connexion au serveur MQTT...
|
||||||
|
2025-05-16 13:41:52 Client MQTT 142.93.152.2 en cours de connexion...
|
||||||
|
2025-05-16 13:41:56 Client MQTT 142.93.152.2 déconnecté pendant une reconnexion.
|
||||||
|
2025-05-16 13:42:06 Tentative de connexion au serveur MQTT...
|
||||||
|
2025-05-16 13:42:06 Client MQTT 142.93.152.2 en cours de connexion...
|
||||||
|
2025-05-16 13:42:10 Client MQTT 142.93.152.2 déconnecté pendant une reconnexion.
|
||||||
|
2025-05-16 13:42:20 Tentative de connexion au serveur MQTT...
|
||||||
|
2025-05-16 13:42:20 Client MQTT 142.93.152.2 en cours de connexion...
|
||||||
|
2025-05-16 13:42:25 Client MQTT 142.93.152.2 déconnecté pendant une reconnexion.
|
||||||
|
2025-05-16 13:42:35 Tentative de connexion au serveur MQTT...
|
||||||
|
2025-05-16 13:42:35 Client MQTT 142.93.152.2 en cours de connexion...
|
||||||
|
2025-05-16 13:42:39 Client MQTT 142.93.152.2 déconnecté pendant une reconnexion.
|
||||||
|
2025-05-16 13:42:49 Tentative de connexion au serveur MQTT...
|
||||||
|
2025-05-16 13:42:49 Client MQTT 142.93.152.2 en cours de connexion...
|
||||||
|
2025-05-16 13:42:53 Client MQTT 142.93.152.2 déconnecté pendant une reconnexion.
|
||||||
|
2025-05-16 13:43:03 Tentative de connexion au serveur MQTT...
|
||||||
|
2025-05-16 13:43:03 Client MQTT 142.93.152.2 en cours de connexion...
|
||||||
|
2025-05-16 13:43:07 Client MQTT 142.93.152.2 déconnecté pendant une reconnexion.
|
||||||
|
2025-05-16 13:43:17 Tentative de connexion au serveur MQTT...
|
||||||
|
2025-05-16 13:43:17 Client MQTT 142.93.152.2 en cours de connexion...
|
||||||
|
2025-05-16 13:43:22 Client MQTT 142.93.152.2 déconnecté pendant une reconnexion.
|
||||||
|
2025-05-16 13:43:32 Tentative de connexion au serveur MQTT...
|
||||||
|
2025-05-16 13:43:32 Client MQTT 142.93.152.2 en cours de connexion...
|
||||||
|
2025-05-16 13:43:36 Client MQTT 142.93.152.2 déconnecté pendant une reconnexion.
|
||||||
|
2025-05-16 13:43:46 Tentative de connexion au serveur MQTT...
|
||||||
|
2025-05-16 13:43:46 Client MQTT 142.93.152.2 en cours de connexion...
|
||||||
|
2025-05-16 13:43:50 Client MQTT 142.93.152.2 déconnecté pendant une reconnexion.
|
||||||
|
2025-05-16 13:44:00 Tentative de connexion au serveur MQTT...
|
||||||
|
2025-05-16 13:44:00 Client MQTT 142.93.152.2 en cours de connexion...
|
||||||
|
2025-05-16 13:44:04 Client MQTT 142.93.152.2 déconnecté pendant une reconnexion.
|
||||||
|
2025-05-16 13:44:14 Tentative de connexion au serveur MQTT...
|
||||||
|
2025-05-16 13:44:14 Client MQTT 142.93.152.2 en cours de connexion...
|
||||||
|
2025-05-16 13:44:14 Client MQTT 142.93.152.2 connecté.
|
||||||
|
2025-05-16 14:59:50 Client MQTT metrics.yultek.dev déconnecté.
|
||||||
|
2025-05-16 14:59:50 Passage en mode buffering des messages MQTT pour metrics.yultek.dev
|
||||||
|
2025-05-16 15:00:00 Tentative de connexion au serveur MQTT...
|
||||||
|
2025-05-16 15:00:00 Client MQTT metrics.yultek.dev en cours de connexion...
|
||||||
|
2025-05-16 15:00:00 Client MQTT metrics.yultek.dev connecté.
|
||||||
|
2025-05-16 16:43:08 Déinitialisation du module PCAN USB ID 81
|
||||||
|
2025-05-16 16:43:08 Impossible de déinitialiser un module USB PCAN.. Error:The transmit buffer in CAN controller is full
|
||||||
|
2025-05-16 16:43:08 Client MQTT metrics.yultek.dev déconnecté.
|
||||||
|
2025-05-16 16:43:08 Passage en mode buffering des messages MQTT pour metrics.yultek.dev
|
||||||
|
2025-05-16 16:43:08 Client MQTT 142.93.152.2 déconnecté.
|
||||||
|
|||||||
Binary file not shown.
Loading…
x
Reference in New Issue
Block a user