jfmartel/YULTek
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

VPN fonctionnel

Browse Source 
Gossage Zigbee
This commit is contained in:
jfmartel 2023-03-17 16:11:09 -04:00
parent 35ed010db8
commit 308bc6c263
22 changed files with 2079 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

BIN
Config Switch edgeos_ubnt_20230317.tar.gz Normal file
View File

Binary file not shown.

BIN
Doc interne/Notes de développement.docx
View File

Binary file not shown.

BIN
OpenVPN/Doc/Expanding The VPN To Include Additional Machines OpenVPN.pdf Normal file
View File

Binary file not shown.

BIN
OpenVPN/Doc/How To Guide Set Up & Configure OpenVPN Client_server VPN OpenVPN.pdf Normal file
View File

Binary file not shown.

BIN
OpenVPN/Doc/How to setup an Edgerouter as VPN Client.pdf Normal file
View File

Binary file not shown.

BIN
OpenVPN/Doc/Set Up and Configure an OpenVPN Server on Ubuntu 20.04 DigitalOcean.pdf Normal file
View File

Binary file not shown.

268
OpenVPN/jf.ovpn Normal file
View File

@ -0,0 +1,268 @@
##############################################
# 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 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:
22:7a:b3:cb:88:05:00:8c:df:af:02:be:af:63:f9:59
Signature Algorithm: sha256WithRSAEncryption
Issuer: CN=JF_server
Validity
Not Before: Feb 20 22:37:46 2023 GMT
Not After : May 25 22:37:46 2025 GMT
Subject: CN=jf
Subject Public Key Info:
Public Key Algorithm: id-ecPublicKey
Public-Key: (384 bit)
pub:
04:8d:38:ea:4f:29:bd:83:a9:33:a3:1c:33:8a:60:
8f:fa:19:81:00:73:44:81:98:1e:76:05:ee:f6:46:
d5:25:a8:c5:3b:bd:d6:fa:cf:c6:79:e0:b4:42:27:
80:e2:96:2d:30:50:c2:f6:9c:2c:13:f8:b9:46:b3:
0d:96:6c:9b:d2:45:15:a3:f0:4c:bc:6b:51:45:f8:
cb:59:04:b1:d0:47:b9:90:06:71:c7:eb:34:32:e2:
72:14:84:94:58:e3:34
ASN1 OID: secp384r1
NIST CURVE: P-384
X509v3 extensions:
X509v3 Basic Constraints:
CA:FALSE
X509v3 Subject Key Identifier:
C5:CE:72:8F:A3:8E:13:57:DD:0E:02:A1:24:F1:56:C3:AE:2F:65:8F
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: sha256WithRSAEncryption
Signature Value:
3b:e8:1a:3e:ac:17:17:49:7c:4d:73:55:39:e9:1b:e4:d6:7f:
6d:6d:43:6c:e2:79:41:f4:26:a4:2d:18:59:24:a0:b1:e0:db:
03:07:f9:fb:24:f6:be:ed:8c:31:3e:c7:bb:74:b6:87:ba:43:
fc:d6:fb:2f:9f:1c:eb:d1:27:ad:60:eb:ab:87:c7:46:fe:22:
75:c1:bb:fb:23:ad:ba:1d:ab:41:45:29:d6:c4:89:99:94:40:
06:c7:3a:08:fe:d3:b5:f4:e7:52:57:aa:d1:a8:ec:74:e6:c9:
ec:9e:80:e0:ba:92:92:95:55:2e:d7:b2:d8:09:ee:72:fd:12:
ac:0a:0d:dc:ba:ac:4e:34:8c:37:19:76:60:7c:bd:ba:99:b7:
e5:47:c3:4b:67:2f:a9:5c:89:95:70:2d:2c:97:45:04:64:15:
47:04:d1:48:7d:d8:40:63:6c:05:8b:dc:ed:0f:a3:ae:3a:e8:
6f:49:34:54:de:99:4b:aa:28:6d:c9:3d:db:43:60:14:40:d5:
09:87:a8:b2:88:11:4c:8c:00:71:b1:38:25:91:5f:2f:93:7b:
42:64:38:db:d2:59:48:e8:ed:2e:92:69:4e:d4:2a:3b:e3:03:
94:2c:fc:ac:bc:ff:a9:b4:1e:ca:d3:d2:b5:fd:bf:33:bd:55:
12:75:db:f1
-----BEGIN CERTIFICATE-----
MIICnjCCAYagAwIBAgIQInqzy4gFAIzfrwK+r2P5WTANBgkqhkiG9w0BAQsFADAU
MRIwEAYDVQQDDAlKRl9zZXJ2ZXIwHhcNMjMwMjIwMjIzNzQ2WhcNMjUwNTI1MjIz
NzQ2WjANMQswCQYDVQQDDAJqZjB2MBAGByqGSM49AgEGBSuBBAAiA2IABI046k8p
vYOpM6McM4pgj/oZgQBzRIGYHnYF7vZG1SWoxTu91vrPxnngtEIngOKWLTBQwvac
LBP4uUazDZZsm9JFFaPwTLxrUUX4y1kEsdBHuZAGccfrNDLichSElFjjNKOBoDCB
nTAJBgNVHRMEAjAAMB0GA1UdDgQWBBTFznKPo44TV90OAqEk8VbDri9ljzBPBgNV
HSMESDBGgBSKeJDl8FDnjHXkuMCh6OmbshqdMqEYpBYwFDESMBAGA1UEAwwJSkZf
c2VydmVyghRd7fuTPbKqDIvbFd+9oZHOXPvLBjATBgNVHSUEDDAKBggrBgEFBQcD
AjALBgNVHQ8EBAMCB4AwDQYJKoZIhvcNAQELBQADggEBADvoGj6sFxdJfE1zVTnp
G+TWf21tQ2zieUH0JqQtGFkkoLHg2wMH+fsk9r7tjDE+x7t0toe6Q/zW+y+fHOvR
J61g66uHx0b+InXBu/sjrbodq0FFKdbEiZmUQAbHOgj+07X051JXqtGo7HTmyeye
gOC6kpKVVS7XstgJ7nL9EqwKDdy6rE40jDcZdmB8vbqZt+VHw0tnL6lciZVwLSyX
RQRkFUcE0Uh92EBjbAWL3O0Po6466G9JNFTemUuqKG3JPdtDYBRA1QmHqLKIEUyM
AHGxOCWRXy+Te0JkONvSWUjo7S6SaU7UKjvjA5Qs/Ky8/6m0HsrT0rX9vzO9VRJ1
2/E=
-----END CERTIFICATE-----
</cert>
<key>
-----BEGIN PRIVATE KEY-----
MIG2AgEAMBAGByqGSM49AgEGBSuBBAAiBIGeMIGbAgEBBDBI4JXNyv7EeAsIFaPn
JBe0cJDvuYM+AGWJYcMtfQj8Sg5z+K0+Ur1IjRxj6vkyXa2hZANiAASNOOpPKb2D
qTOjHDOKYI/6GYEAc0SBmB52Be72RtUlqMU7vdb6z8Z54LRCJ4Dili0wUML2nCwT
+LlGsw2WbJvSRRWj8Ey8a1FF+MtZBLHQR7mQBnHH6zQy4nIUhJRY4zQ=
-----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>

268
OpenVPN/pascal.ovpn Normal file
View File

@ -0,0 +1,268 @@
##############################################
# 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 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:
a6:7f:64:22:94:22:4a:39:b9:48:25:9b:99:9d:ae:a7
Signature Algorithm: sha256WithRSAEncryption
Issuer: CN=JF_server
Validity
Not Before: Mar 17 19:30:32 2023 GMT
Not After : Jun 19 19:30:32 2025 GMT
Subject: CN=pascal
Subject Public Key Info:
Public Key Algorithm: id-ecPublicKey
Public-Key: (384 bit)
pub:
04:6e:d7:fc:29:a8:23:70:28:49:70:82:f4:1a:4f:
fc:e8:5a:d3:10:84:ef:0a:59:d9:3e:31:2e:5f:91:
8b:97:7e:32:c5:e4:9a:b1:df:8b:66:82:f7:a5:5a:
6d:90:ba:4d:4b:75:4e:1b:09:37:3b:23:5b:df:b8:
08:89:c7:a0:d6:3b:fa:3e:f8:b1:08:18:a6:ee:25:
02:25:b2:c5:43:ee:f5:03:82:9e:39:a0:82:d0:23:
49:eb:fe:be:3e:8f:7a
ASN1 OID: secp384r1
NIST CURVE: P-384
X509v3 extensions:
X509v3 Basic Constraints:
CA:FALSE
X509v3 Subject Key Identifier:
8E:E1:F2:13:12:D0:E0:C4:29:EA:29:E4:3D:94:2B:EC:0D:04:8F:BC
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: sha256WithRSAEncryption
Signature Value:
7d:0b:3f:f6:58:09:f2:8a:8d:0e:1e:50:c9:e8:31:f0:8f:0a:
f5:65:66:55:d3:dd:2c:5d:42:d4:0f:a5:02:ed:6a:77:e1:1d:
39:c5:46:1c:a5:38:17:89:13:f1:cd:eb:ff:b8:a5:3d:e9:85:
6f:d2:96:9b:f4:a1:09:6c:1b:84:40:70:19:2b:e1:ac:91:c2:
df:bf:09:a4:4f:c4:31:44:fe:2b:a5:60:38:97:a8:b3:01:aa:
39:43:74:90:b5:c6:fc:85:63:26:9f:7f:54:ba:de:4a:b1:ae:
6d:85:00:35:4d:15:9f:9d:10:f4:bf:bb:67:45:7e:c6:ab:ee:
7e:ad:92:4a:b4:e8:76:65:be:94:40:5a:67:83:ab:6c:d9:f9:
7d:40:bd:70:87:1f:14:4d:eb:56:50:a5:c3:7e:4a:b3:42:b5:
95:fe:f8:7f:9b:c6:c0:81:04:62:fd:94:ef:da:dd:17:01:a0:
93:14:80:31:5a:a2:fa:c7:8c:2d:7c:df:8b:40:d5:5c:ce:5f:
a8:9f:9f:48:4f:49:49:dc:cc:37:7e:f7:55:84:74:8a:cd:68:
15:60:8b:e8:4a:75:3e:83:cb:33:be:45:e1:a1:76:52:1a:b9:
09:34:38:af:6e:af:98:e3:6d:ed:c2:24:97:de:08:83:6b:d5:
45:9e:91:3a
-----BEGIN CERTIFICATE-----
MIICozCCAYugAwIBAgIRAKZ/ZCKUIko5uUglm5mdrqcwDQYJKoZIhvcNAQELBQAw
FDESMBAGA1UEAwwJSkZfc2VydmVyMB4XDTIzMDMxNzE5MzAzMloXDTI1MDYxOTE5
MzAzMlowETEPMA0GA1UEAwwGcGFzY2FsMHYwEAYHKoZIzj0CAQYFK4EEACIDYgAE
btf8KagjcChJcIL0Gk/86FrTEITvClnZPjEuX5GLl34yxeSasd+LZoL3pVptkLpN
S3VOGwk3OyNb37gIiceg1jv6PvixCBim7iUCJbLFQ+71A4KeOaCC0CNJ6/6+Po96
o4GgMIGdMAkGA1UdEwQCMAAwHQYDVR0OBBYEFI7h8hMS0ODEKeop5D2UK+wNBI+8
ME8GA1UdIwRIMEaAFIp4kOXwUOeMdeS4wKHo6ZuyGp0yoRikFjAUMRIwEAYDVQQD
DAlKRl9zZXJ2ZXKCFF3t+5M9sqoMi9sV372hkc5c+8sGMBMGA1UdJQQMMAoGCCsG
AQUFBwMCMAsGA1UdDwQEAwIHgDANBgkqhkiG9w0BAQsFAAOCAQEAfQs/9lgJ8oqN
Dh5Qyegx8I8K9WVmVdPdLF1C1A+lAu1qd+EdOcVGHKU4F4kT8c3r/7ilPemFb9KW
m/ShCWwbhEBwGSvhrJHC378JpE/EMUT+K6VgOJeoswGqOUN0kLXG/IVjJp9/VLre
SrGubYUANU0Vn50Q9L+7Z0V+xqvufq2SSrTodmW+lEBaZ4OrbNn5fUC9cIcfFE3r
VlClw35Ks0K1lf74f5vGwIEEYv2U79rdFwGgkxSAMVqi+seMLXzfi0DVXM5fqJ+f
SE9JSdzMN373VYR0is1oFWCL6Ep1PoPLM75F4aF2Uhq5CTQ4r26vmONt7cIkl94I
g2vVRZ6ROg==
-----END CERTIFICATE-----
</cert>
<key>
-----BEGIN PRIVATE KEY-----
MIG2AgEAMBAGByqGSM49AgEGBSuBBAAiBIGeMIGbAgEBBDBaXJvFX1ve+n9RXR/s
FyOJij1AEAhcbzj6Vg0PXekMwOSAkRsAltTXYM3nAaRK93OhZANiAARu1/wpqCNw
KElwgvQaT/zoWtMQhO8KWdk+MS5fkYuXfjLF5Jqx34tmgvelWm2Quk1LdU4bCTc7
I1vfuAiJx6DWO/o++LEIGKbuJQIlssVD7vUDgp45oILQI0nr/r4+j3o=
-----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>

268
OpenVPN/remoteclient.ovpn Normal file
View File

@ -0,0 +1,268 @@
##############################################
# 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 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:
d1:ae:61:45:8e:84:e3:8e:5b:92:3f:aa:bb:81:9d:59
Signature Algorithm: sha256WithRSAEncryption
Issuer: CN=JF_server
Validity
Not Before: Feb 23 20:30:31 2023 GMT
Not After : May 28 20:30:31 2025 GMT
Subject: CN=remoteclient
Subject Public Key Info:
Public Key Algorithm: id-ecPublicKey
Public-Key: (384 bit)
pub:
04:65:e9:86:35:01:c3:d7:0e:16:3d:89:90:3c:cb:
a0:5f:d2:04:f7:b6:32:84:1e:a0:dc:6a:1d:16:a0:
6f:47:a3:b5:7d:4c:39:bd:d0:70:18:34:e8:16:67:
d4:5b:4c:ca:ce:ea:f0:75:5f:55:72:09:4b:f5:dd:
80:f1:d5:db:e6:26:09:e4:34:3b:ca:89:f3:3a:40:
91:31:14:c6:ff:06:8d:8e:f9:ba:8f:47:df:40:41:
f4:6b:84:f8:e5:e8:70
ASN1 OID: secp384r1
NIST CURVE: P-384
X509v3 extensions:
X509v3 Basic Constraints:
CA:FALSE
X509v3 Subject Key Identifier:
23:F8:BF:EB:8E:A3:77:B3:2B:6A:FA:16:7A:39:B2:C2:47:31:9F:76
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: sha256WithRSAEncryption
Signature Value:
27:af:ff:e0:98:8e:d1:6c:39:d7:40:97:df:ea:5a:fc:57:31:
a2:92:0c:d3:4c:4b:74:22:9e:47:01:9b:0f:e0:a4:6c:dc:ef:
14:b7:93:0f:99:93:ec:c9:96:dc:51:58:d3:ac:eb:f1:10:48:
ba:96:54:25:32:2a:89:66:cb:ca:13:b4:75:cc:4e:2a:5d:7c:
bb:b9:15:28:c0:32:59:f0:66:e5:fe:d8:14:14:2c:fb:df:6e:
1e:b6:53:c9:f0:77:68:54:b9:21:4b:0c:a4:d6:bc:4d:c2:a3:
de:d0:9f:ef:67:68:3e:c6:d4:da:d5:6c:92:80:cf:2e:8d:04:
59:c8:39:9f:22:4a:04:28:3e:e8:cf:02:73:73:a6:59:d4:e5:
9c:77:55:41:00:5c:c2:23:61:df:44:5c:ad:a8:bc:15:57:2d:
ae:89:99:a7:33:8f:d3:75:02:21:91:f6:38:34:23:68:70:8f:
99:0f:53:27:6d:52:9a:9b:f3:62:cf:20:bc:f5:91:41:78:fc:
92:09:2f:3e:bb:2d:9b:69:39:7f:c4:b1:a8:62:64:27:3f:27:
2d:16:c4:3e:0d:51:c9:f7:4f:40:f0:fd:55:a9:44:36:31:59:
b7:08:6a:3c:28:31:8a:43:c0:b9:05:44:75:48:6d:94:24:c6:
b2:fc:f7:33
-----BEGIN CERTIFICATE-----
MIICqTCCAZGgAwIBAgIRANGuYUWOhOOOW5I/qruBnVkwDQYJKoZIhvcNAQELBQAw
FDESMBAGA1UEAwwJSkZfc2VydmVyMB4XDTIzMDIyMzIwMzAzMVoXDTI1MDUyODIw
MzAzMVowFzEVMBMGA1UEAwwMcmVtb3RlY2xpZW50MHYwEAYHKoZIzj0CAQYFK4EE
ACIDYgAEZemGNQHD1w4WPYmQPMugX9IE97YyhB6g3GodFqBvR6O1fUw5vdBwGDTo
FmfUW0zKzurwdV9VcglL9d2A8dXb5iYJ5DQ7yonzOkCRMRTG/waNjvm6j0ffQEH0
a4T45ehwo4GgMIGdMAkGA1UdEwQCMAAwHQYDVR0OBBYEFCP4v+uOo3ezK2r6Fno5
ssJHMZ92ME8GA1UdIwRIMEaAFIp4kOXwUOeMdeS4wKHo6ZuyGp0yoRikFjAUMRIw
EAYDVQQDDAlKRl9zZXJ2ZXKCFF3t+5M9sqoMi9sV372hkc5c+8sGMBMGA1UdJQQM
MAoGCCsGAQUFBwMCMAsGA1UdDwQEAwIHgDANBgkqhkiG9w0BAQsFAAOCAQEAJ6//
4JiO0Ww510CX3+pa/FcxopIM00xLdCKeRwGbD+CkbNzvFLeTD5mT7MmW3FFY06zr
8RBIupZUJTIqiWbLyhO0dcxOKl18u7kVKMAyWfBm5f7YFBQs+99uHrZTyfB3aFS5
IUsMpNa8TcKj3tCf72doPsbU2tVskoDPLo0EWcg5nyJKBCg+6M8Cc3OmWdTlnHdV
QQBcwiNh30Rcrai8FVctromZpzOP03UCIZH2ODQjaHCPmQ9TJ21SmpvzYs8gvPWR
QXj8kgkvPrstm2k5f8SxqGJkJz8nLRbEPg1RyfdPQPD9ValENjFZtwhqPCgxikPA
uQVEdUhtlCTGsvz3Mw==
-----END CERTIFICATE-----
</cert>
<key>
-----BEGIN PRIVATE KEY-----
MIG2AgEAMBAGByqGSM49AgEGBSuBBAAiBIGeMIGbAgEBBDBTe+pBwBZIEMj0jszW
fZEx67ft6630EHlFhaCHTXW9Nw25eDC2kfm2xwbjb093E++hZANiAARl6YY1AcPX
DhY9iZA8y6Bf0gT3tjKEHqDcah0WoG9Ho7V9TDm90HAYNOgWZ9RbTMrO6vB1X1Vy
CUv13YDx1dvmJgnkNDvKifM6QJExFMb/Bo2O+bqPR99AQfRrhPjl6HA=
-----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>

321
OpenVPN/server.conf Normal file
View File

@ -0,0 +1,321 @@
#################################################
# Sample OpenVPN 2.0 config file for #
# multi-client server. #
# #
# This file is for the server side #
# of a many-clients <-> one-server #
# OpenVPN configuration. #
# #
# OpenVPN also supports #
# single-machine <-> single-machine #
# configurations (See the Examples page #
# on the web site for more info). #
# #
# This config should work on Windows #
# or Linux/BSD systems. Remember on #
# Windows to quote pathnames and use #
# double backslashes, e.g.: #
# "C:\\Program Files\\OpenVPN\\config\\foo.key" #
# #
# Comments are preceded with '#' or ';' #
#################################################
# Which local IP address should OpenVPN
# listen on? (optional)
;local a.b.c.d
# Which TCP/UDP port should OpenVPN listen on?
# If you want to run multiple OpenVPN instances
# on the same machine, use a different port
# number for each one. You will need to
# open up this port on your firewall.
port 1194
# TCP or UDP server?
;proto tcp
proto udp
# "dev tun" will create a routed IP tunnel,
# "dev tap" will create an ethernet tunnel.
# Use "dev tap0" if you are ethernet bridging
# and have precreated a tap0 virtual interface
# and bridged it with your ethernet interface.
# If you want to control access policies
# over the VPN, you must create firewall
# rules for the the TUN/TAP interface.
# On non-Windows systems, you can give
# an explicit unit number, such as tun0.
# On Windows, use "dev-node" for this.
# 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 or higher,
# you may need to selectively disable the
# Windows firewall for the TAP adapter.
# Non-Windows systems usually don't need this.
;dev-node MyTap
# SSL/TLS root certificate (ca), certificate
# (cert), and private key (key). Each client
# and the server must have their own cert and
# key file. The server and all clients will
# use the same ca file.
#
# See the "easy-rsa" directory for a series
# of scripts for generating RSA certificates
# and private keys. Remember to use
# a unique Common Name for the server
# and each of the client certificates.
#
# Any X509 key management system can be used.
# OpenVPN can also use a PKCS #12 formatted key file
# (see "pkcs12" directive in man page).
ca ca.crt
cert DO_server.crt
key DO_server.key # This file should be kept secret
# Diffie hellman parameters.
# Generate your own with:
# openssl dhparam -out dh2048.pem 2048
;dh dh2048.pem
dh none
# Network topology
# Should be subnet (addressing via IP)
# unless Windows clients v2.0.9 and lower have to
# be supported (then net30, i.e. a /30 per client)
# Defaults to net30 (not recommended)
;topology subnet
# Configure server mode and supply a VPN subnet
# for OpenVPN to draw client addresses from.
# The server will take 10.8.0.1 for itself,
# the rest will be made available to clients.
# Each client will be able to reach the server
# on 10.8.0.1. Comment this line out if you are
# ethernet bridging. See the man page for more info.
server 10.8.0.0 255.255.255.0
# Maintain a record of client <-> virtual IP address
# associations in this file. If OpenVPN goes down or
# is restarted, reconnecting clients can be assigned
# the same virtual IP address from the pool that was
# previously assigned.
ifconfig-pool-persist /var/log/openvpn/ipp.txt
# Configure server mode for ethernet bridging.
# You must first use your OS's bridging capability
# to bridge the TAP interface with the ethernet
# NIC interface. Then you must manually set the
# IP/netmask on the bridge interface, here we
# assume 10.8.0.4/255.255.255.0. Finally we
# must set aside an IP range in this subnet
# (start=10.8.0.50 end=10.8.0.100) to allocate
# to connecting clients. Leave this line commented
# out unless you are ethernet bridging.
;server-bridge 10.8.0.4 255.255.255.0 10.8.0.50 10.8.0.100
# Configure server mode for ethernet bridging
# using a DHCP-proxy, where clients talk
# to the OpenVPN server-side DHCP server
# to receive their IP address allocation
# and DNS server addresses. You must first use
# your OS's bridging capability to bridge the TAP
# interface with the ethernet NIC interface.
# Note: this mode only works on clients (such as
# Windows), where the client-side TAP adapter is
# bound to a DHCP client.
;server-bridge
# Push routes to the client to allow it
# to reach other private subnets behind
# the server. Remember that these
# private subnets will also need
# to know to route the OpenVPN client
# address pool (10.8.0.0/255.255.255.0)
# back to the OpenVPN server.
push "route 192.168.10.0 255.255.255.0"
;push "route 192.168.30.0 255.255.255.0"
# To assign specific IP addresses to specific
# clients or if a connecting client has a private
# subnet behind it that should also have VPN access,
# use the subdirectory "ccd" for client-specific
# configuration files (see man page for more info).
# EXAMPLE: Suppose the client
# having the certificate common name "Thelonious"
# also has a small subnet behind his connecting
# machine, such as 192.168.40.128/255.255.255.248.
# First, uncomment out these lines:
client-config-dir ccd
;route 192.168.40.128 255.255.255.248
route 192.168.10.0 255.255.255.0
# Then create a file ccd/Thelonious with this line:
# iroute 192.168.40.128 255.255.255.248
# This will allow Thelonious' private subnet to
# access the VPN. This example will only work
# if you are routing, not bridging, i.e. you are
# using "dev tun" and "server" directives.
# EXAMPLE: Suppose you want to give
# Thelonious a fixed VPN IP address of 10.9.0.1.
# First uncomment out these lines:
;client-config-dir ccd
;route 10.9.0.0 255.255.255.252
# Then add this line to ccd/Thelonious:
# ifconfig-push 10.9.0.1 10.9.0.2
# Suppose that you want to enable different
# firewall access policies for different groups
# of clients. There are two methods:
# (1) Run multiple OpenVPN daemons, one for each
# group, and firewall the TUN/TAP interface
# for each group/daemon appropriately.
# (2) (Advanced) Create a script to dynamically
# modify the firewall in response to access
# from different clients. See man
# page for more info on learn-address script.
;learn-address ./script
# If enabled, this directive will configure
# all clients to redirect their default
# network gateway through the VPN, causing
# all IP traffic such as web browsing and
# and DNS lookups to go through the VPN
# (The OpenVPN server machine may need to NAT
# or bridge the TUN/TAP interface to the internet
# in order for this to work properly).
;push "redirect-gateway def1 bypass-dhcp"
# Certain Windows-specific network settings
# can be pushed to clients, such as DNS
# or WINS server addresses. CAVEAT:
# http://openvpn.net/faq.html#dhcpcaveats
# The addresses below refer to the public
# DNS servers provided by opendns.com.
;push "dhcp-option DNS 208.67.222.222"
;push "dhcp-option DNS 208.67.220.220"
# Uncomment this directive to allow different
# clients to be able to "see" each other.
# By default, clients will only see the server.
# To force clients to only see the server, you
# will also need to appropriately firewall the
# server's TUN/TAP interface.
client-to-client
# Uncomment this directive if multiple clients
# might connect with the same certificate/key
# files or common names. This is recommended
# only for testing purposes. For production use,
# each client should have its own certificate/key
# pair.
#
# IF YOU HAVE NOT GENERATED INDIVIDUAL
# CERTIFICATE/KEY PAIRS FOR EACH CLIENT,
# EACH HAVING ITS OWN UNIQUE "COMMON NAME",
# UNCOMMENT THIS LINE OUT.
;duplicate-cn
# The keepalive directive causes ping-like
# messages to be sent back and forth over
# the link so that each side knows when
# the other side has gone down.
# Ping every 10 seconds, assume that remote
# peer is down if no ping received during
# a 120 second time period.
keepalive 10 120
# For extra security beyond that provided
# by SSL/TLS, create an "HMAC firewall"
# to help block DoS attacks and UDP port flooding.
#
# Generate with:
# openvpn --genkey tls-auth ta.key
#
# The server and each client must have
# a copy of this key.
# The second parameter should be '0'
# on the server and '1' on the clients.
;tls-auth ta.key 0 # This file is secret
tls-crypt ta.key
# Select a cryptographic cipher.
# This config item must be copied to
# the client config file as well.
# Note that v2.4 client/server will automatically
# negotiate AES-256-GCM in TLS mode.
# See also the ncp-cipher option in the manpage
;cipher AES-256-CBC
cipher AES-256-GCM
auth SHA256
# Enable compression on the VPN link and push the
# option to the client (v2.4+ only, for earlier
# versions see below)
;compress lz4-v2
;push "compress lz4-v2"
# For compression compatible with older clients use comp-lzo
# If you enable it here, you must also
# enable it in the client config file.
;comp-lzo
# The maximum number of concurrently connected
# clients we want to allow.
;max-clients 100
# It's a good idea to reduce the OpenVPN
# daemon's privileges after initialization.
#
# You can uncomment this out on
# non-Windows systems.
user nobody
group nogroup
# The persist options will try to avoid
# accessing certain resources on restart
# that may no longer be accessible because
# of the privilege downgrade.
persist-key
persist-tun
# Output a short status file showing
# current connections, truncated
# and rewritten every minute.
status /var/log/openvpn/openvpn-status.log
# By default, log messages will go to the syslog (or
# on Windows, if running as a service, they will go to
# the "\Program Files\OpenVPN\log" directory).
# Use log or log-append to override this default.
# "log" will truncate the log file on OpenVPN startup,
# while "log-append" will append to it. Use one
# or the other (but not both).
;log /var/log/openvpn/openvpn.log
;log-append /var/log/openvpn/openvpn.log
# Set the appropriate level of log
# file verbosity.
#
# 0 is silent, except for fatal errors
# 4 is reasonable for general usage
# 5 and 6 can help to debug connection problems
# 9 is extremely verbose
verb 3
# Silence repeating messages. At most 20
# sequential messages of the same message
# category will be output to the log.
;mute 20
# Notify the client that when the server restarts so it
# can automatically reconnect.
explicit-exit-notify 1

90
Otarcik_CAN/Logs/SystemLog.txt
View File

@ -7094,3 +7094,93 @@ Démarrage du logiciel Otarcik CAN le 2023-03-15 à 17:33:01
2023-03-15 17:33:01 Dispositif [ParkerCAN] initialisé avec succès!
2023-03-15 17:35:21 Déinitialisation du module PCAN USB ID 81
2023-03-15 17:35:21 Module PCAN USB déinitialisé avec succès...
********************************************************************
Démarrage du logiciel Otarcik CAN le 2023-03-16 à 05:28:16
********************************************************************
2023-03-16 05:28:16 Démarrage du logiciel OtarcikCAN
2023-03-16 05:28:16 Chargement de la configuration système...
2023-03-16 05:28:16 Configuration système chargée avec succès!
2023-03-16 05:28:16 Initialisation du dispositif [ParkerCAN]
2023-03-16 05:28:16 Chargement de la base de données D:/Main/Dev/YULTek/Otarcik_CAN/IVT-S_all-variations_12082020.dbc
2023-03-16 05:28:16 Base de données chargée avec succès. Flags: 0x0
2023-03-16 05:28:16 Démarrage d'un module CAN...
2023-03-16 05:28:16 Initialisation d'un module PCAN. Channel:81, Baudrate:28
2023-03-16 05:28:16 Impossible d'initialiser un module USB PCAN. Erreur:The driver is not loaded
2023-03-16 05:28:16 Impossible d'initialiser le matériel CAN
2023-03-16 05:28:16 Le dispositif [ParkerCAN] n'a pas pu s'initialiser
2023-03-16 05:28:20 Déinitialisation du module PCAN USB ID 81
2023-03-16 05:28:20 Impossible de déinitialiser un module USB PCAN.. Error:The transmit buffer in CAN controller is full
********************************************************************
Démarrage du logiciel Otarcik CAN le 2023-03-16 à 05:28:50
********************************************************************
2023-03-16 05:28:50 Démarrage du logiciel OtarcikCAN
2023-03-16 05:28:50 Chargement de la configuration système...
2023-03-16 05:28:50 Configuration système chargée avec succès!
2023-03-16 05:28:50 Initialisation du dispositif [ParkerCAN]
2023-03-16 05:28:50 Chargement de la base de données D:/Main/Dev/YULTek/Otarcik_CAN/IVT-S_all-variations_12082020.dbc
2023-03-16 05:28:50 Base de données chargée avec succès. Flags: 0x0
2023-03-16 05:28:50 Démarrage d'un module CAN...
2023-03-16 05:28:50 Initialisation d'un module PCAN. Channel:81, Baudrate:28
2023-03-16 05:28:50 Impossible d'initialiser un module USB PCAN. Erreur:The driver is not loaded
2023-03-16 05:28:50 Impossible d'initialiser le matériel CAN
2023-03-16 05:28:50 Le dispositif [ParkerCAN] n'a pas pu s'initialiser
2023-03-16 05:28:52 Déinitialisation du module PCAN USB ID 81
2023-03-16 05:28:52 Impossible de déinitialiser un module USB PCAN.. Error:The transmit buffer in CAN controller is full
********************************************************************
Démarrage du logiciel Otarcik CAN le 2023-03-16 à 11:15:58
********************************************************************
2023-03-16 11:15:58 Démarrage du logiciel OtarcikCAN
2023-03-16 11:15:58 Chargement de la configuration système...
2023-03-16 11:15:58 Configuration système chargée avec succès!
2023-03-16 11:15:58 Initialisation du dispositif [ParkerCAN]
2023-03-16 11:15:58 Chargement de la base de données D:/Main/Dev/YULTek/Otarcik_CAN/IVT-S_all-variations_12082020.dbc
2023-03-16 11:15:58 Base de données chargée avec succès. Flags: 0x0
2023-03-16 11:15:58 Démarrage d'un module CAN...
2023-03-16 11:15:58 Initialisation d'un module PCAN. Channel:81, Baudrate:28
2023-03-16 11:15:58 Impossible d'initialiser un module USB PCAN. Erreur:The driver is not loaded
2023-03-16 11:15:58 Impossible d'initialiser le matériel CAN
2023-03-16 11:15:58 Le dispositif [ParkerCAN] n'a pas pu s'initialiser
2023-03-16 11:16:33 Déinitialisation du module PCAN USB ID 81
2023-03-16 11:16:33 Impossible de déinitialiser un module USB PCAN.. Error:The transmit buffer in CAN controller is full
********************************************************************
Démarrage du logiciel Otarcik CAN le 2023-03-17 à 09:52:31
********************************************************************
2023-03-17 09:52:31 Démarrage du logiciel OtarcikCAN
2023-03-17 09:52:31 Chargement de la configuration système...
2023-03-17 09:52:31 Configuration système chargée avec succès!
2023-03-17 09:52:31 Initialisation du dispositif [ParkerCAN]
2023-03-17 09:52:31 Chargement de la base de données D:/Main/Dev/YULTek/Otarcik_CAN/IVT-S_all-variations_12082020.dbc
2023-03-17 09:52:31 Base de données chargée avec succès. Flags: 0x0
2023-03-17 09:52:31 Démarrage d'un module CAN...
2023-03-17 09:52:31 Initialisation d'un module PCAN. Channel:81, Baudrate:28
2023-03-17 09:52:31 Impossible d'initialiser un module USB PCAN. Erreur:The driver is not loaded
2023-03-17 09:52:31 Impossible d'initialiser le matériel CAN
2023-03-17 09:52:31 Le dispositif [ParkerCAN] n'a pas pu s'initialiser
2023-03-17 09:53:34 Déinitialisation du module PCAN USB ID 81
2023-03-17 09:53:34 Impossible de déinitialiser un module USB PCAN.. Error:The transmit buffer in CAN controller is full
********************************************************************
Démarrage du logiciel Otarcik CAN le 2023-03-17 à 09:53:38
********************************************************************
2023-03-17 09:53:38 Démarrage du logiciel OtarcikCAN
2023-03-17 09:53:38 Chargement de la configuration système...
2023-03-17 09:53:38 Configuration système chargée avec succès!
2023-03-17 09:53:38 Initialisation du dispositif [ParkerCAN]
2023-03-17 09:53:38 Chargement de la base de données D:/Main/Dev/YULTek/Otarcik_CAN/IVT-S_all-variations_12082020.dbc
2023-03-17 09:53:38 Base de données chargée avec succès. Flags: 0x0
2023-03-17 09:53:38 Démarrage d'un module CAN...
2023-03-17 09:53:38 Initialisation d'un module PCAN. Channel:81, Baudrate:28
2023-03-17 09:53:38 Impossible d'initialiser un module USB PCAN. Erreur:The driver is not loaded
2023-03-17 09:53:38 Impossible d'initialiser le matériel CAN
2023-03-17 09:53:38 Le dispositif [ParkerCAN] n'a pas pu s'initialiser
2023-03-17 09:53:47 Déinitialisation du module PCAN USB ID 81
2023-03-17 09:53:47 Impossible de déinitialiser un module USB PCAN.. Error:The transmit buffer in CAN controller is full

2
Otarcik_CAN/Sources/Gui/GeneralStatusPage.ui
View File

@ -6,7 +6,7 @@
<rect>
<x>0</x>
<y>0</y>
<width>1456</width>
<width>1725</width>
<height>527</height>
</rect>
</property>

BIN
Otarcik_CAN/debug/Otarcik_CAN.exe
View File

Binary file not shown.

2
Otarcik_CAN/ui_GeneralStatusPage.h
View File

@ -27,7 +27,7 @@ public:
{
if (CGeneralStatusPage->objectName().isEmpty())
CGeneralStatusPage->setObjectName(QString::fromUtf8("CGeneralStatusPage"));
CGeneralStatusPage->resize(1456, 527);
CGeneralStatusPage->resize(1725, 527);
mGenMsgTextEdit = new QTextEdit(CGeneralStatusPage);
mGenMsgTextEdit->setObjectName(QString::fromUtf8("mGenMsgTextEdit"));
mGenMsgTextEdit->setGeometry(QRect(30, 20, 1141, 451));

580
ZigBee/CP210x_Universal_Windows_Driver/CP210x_Universal_Windows_Driver_ReleaseNotes.txt Normal file
View File

@ -0,0 +1,580 @@
RELEASE NOTES
=============
Silicon Labs Virtual COM Port (VCP) Universal Driver for Windows 10 version 1803 and later, windows 11
Package version: 11.2.0
Release date: 2022-10-21
This package contains a Virtual COM Port Universal driver for Microsoft
Windows 10 version 1803 and later, windows 11 versions of Windows for use with Silicon Labs VCP USB Serial Bridges. These devices
include the CP2102N, CP2102, CP2103, CP2104, CP2105, CP2108, CP2109.
OS VERSIONS
-----------
This package provides the CP210x VCP driver for the following versions
of Windows:
- Windows 10 version 1803 and later (x64, x86)
- Windows 11 (x64)
CHOOSING VCP DRIVER VERSION
---------------------------
VCP drivers of version 11.1.0 and later are released for Microsoft
Windows 10 version 1803 and later, windows 11 versions of Windows as Universal Drivers.
This means they do not work on older version of Windows
such as Window 7 and 8.1. You should use this driver if you only need
support for Windows 10 version 1803 and later, windows 11, or you need the Universal driver. If you require
support on older versions of Windows, you should use the legacy VCP driver
which can be found on the Silicon Labs web site. The legacy Windows VCP
drivers have version numbers less than 10.0.0.
CONTENTS
--------
The VCP driver package contains the following files and directories:
- silabser.inf -- Driver information file
- SLAB_License_Agreement_VCP_Windows.txt -- Software License
- CP210x_Universal_Windows_Driver_ReleaseNotes.txt -- this file
Additional files needed by installer
- silabser.cat
- x64/silabser.sys
- x86/silabser.sys
INSTALLING
----------
The VCP driver is automatically installed by Windows Update for CP210x with
alternate PID values of 0xEA63, 0xEA7A, and 0xEA7B. These are not default
values.
Otherwise, unzip the .zip file and you will have a directory containing the
driver installer files.
### Prompted install ###
If Windows prompts you to install a driver for a CP210x device
(for example, if you plug a CP210x into your computer):
1. Use the dialog to browse for the driver location
2. Locate the driver folder (that you previously unzipped)
3. Follow the instructions
### Manual install ###
1. Using Windows File Explorer, locate the driver folder
(that you previously unzipped)
2. Right click on the silabser.inf file and select Install
3. Follow the instructions
UNINSTALLING
------------
1. The device must be plugged in
2. Run Device Manager
3. Locate the device you want to uninstall
4. Right click on the device and choose "uninstall"
5. Follow the instructions
SETUP REGISTRY KEY
------------------
Registry keys are used for setting some parameters of the serial port
For setting these parameters, we have 2 ways:
- Modify registry value using registry editor of Windows
- Modify registry value using INF file
### Modify the registry key's value in Registry Editor ###
1. Open Command Prompt on windows => type command: regedit
2. Registry tree is displayed
3. Registry key is allocated at 3 position:
- Parameters keys: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\silabser
- Software keys: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\<ClassID>\
- Hardware keys: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\deviceID\
4. Right-click each key => select modify => edit value for key
### Enable the registry key in driver's INF file ###
1. To enable the registry key, Please remove character ';' to uncomment the statement
2. Registry key is allocated at 3 position:
- Parameters keys: [silabser.AddService.AddReg] directives
- Software keys: [silabser.AddReg] directives
- Hardware keys: [SiLabsDDInstallSection.HW.AddReg] directives
SUPPORT
-------
For technical support please visit the Silicon Labs support site:
https://www.silabs.com/support
******************************************************************************
RELEASE NOTES FOR 11.2.0 (2022-10-21)
Changes for VCP Driver
==============================================================================
MCUSW-415 | Remove code paths for XP vs not XP which is used for
| UsingWindows2000.
MCUSW-416 | Improve debug statement readability by adding device specific
| information.
MCUSW-523 | add instruction how to setting up registry in .inf file.
MCUSW-532 | Fix Automatic handshaking on RTS/CTS, and driver buffers
| overran at high baud rate.
MCUSW-1285 | add DisableIoctlIOCTL_SERIAL_PURGE in .inf file to prevent data
| lost in close.
******************************************************************************
RELEASE NOTES FOR 11.1.0 (2022-03-21)
Changes for VCP Driver
==============================================================================
MCUSW-803 | CP210x device needs to send Xoff to the other side device
| (FTDI for example) when Windows goes to sleep
MCUSW-1038 | Fix DFx problem on Windows 11
MCUSW-1039 | Do HLK DFx testing for Windows VCP driver version 11.1.0
MCUSW-1045 | Update file version and driver version for Windows VCP
| driver version 11.1.0
MCUSW-1047 | Make the Windows VCP driver pass SDV
MCUSW-1048 | Microsoft Windows Certified ("WHQL Certified") for Windows 11
| version 21H2
MCUSW-1049 | Using Dynamic api to make Windows VCP driver to be compatible
| with different versions of Windows (Mininum required is Windows
| 10 version 1803)
******************************************************************************
RELEASE NOTES FOR 11.0.0 (2021-11-05)
Changes for VCP Driver
==============================================================================
MCUSW-176 | Add report SERIAL_ERROR_QUEUEOVERRUN when driver-side receive
| buffer is overrun
MCUSW-889 | Fixed HLK Test error: Static Tools Logo Test
MCUSW-749 | Fixed issue that RTS is not set to high when Windows goes to
| sleep to make sure incoming data to CP210x won't be lost when
| Windows is in sleeping state
MCUSW-841 | Removed installer to make a standalone driver package. Users
| need to use INF file to install the driver instead
MCUSW-906 | Add Microsoft Windows Certified ("WHQL Certified") for Windows 11
| version 21H2
******************************************************************************
RELEASE NOTES FOR 10.1.10 (2021-01-13)
Changes for VCP Driver
==============================================================================
MCUSW-651 | Support baud rate up to 2187500 for CP2102, CP2104, CP2109
MCUSW-685 | Fixed the Blue Screen issue when running Windows Hardware Lab
| Kit for customized driver
MCUSW-783 | Microsoft Windows Certified (aka "WHQL Certified") for Windows
| 10 version 20H2 (2020-10-20)
******************************************************************************
RELEASE NOTES FOR 10.1.9 (2020-07-30)
Changes for VCP Driver
==============================================================================
MCUSW-566 | Remove sanity/error checking on IOCTL_SERIAL_SET_BAUD_RATE for
| CP2103 devices.
MCUSW-596 | Microsoft Windows Certified (aka "WHQL Certified") for Windows
| 10 version 2004 (2020-05-27)
MCUSW-619 | Support for Directed PoFx (DFx - Directed Power Management
| Framework).
******************************************************************************
RELEASE NOTES FOR 10.1.8 (2019-06-24 (DriverVer = 06/20/2019,10.1.8.2466))
Changes for VCP Driver
==============================================================================
MCUSW-412 | Certified for Windows 10 RS6.
MCUSW-484 | WDFVERIFY() added to the driver. Configurable via Registry.
MCUSW-493 | Improved the tagging/tracking and parent-hierarchy of framework
| objects and framework object reference counts.
MCUSW-495 | Clear RTS on CloseHandle().
MCUSW-508 | IOCTL_SERIAL_GET_COMMSTATUS refactored to reduce USB-bus
| bandwidth, while still offering timely reporting.
MCUSW-518 | WDFVerifier parameter ForceLogsInMiniDump Registry parameter
| added for improved supportability.
MCUSW-519 | Resolve an SDV-identified issue: do not double-complete a
| Request on error paths.
MCUSW-526 | Creates the framework USB device object with client contract
| version USBD_CLIENT_CONTRACT_VERSION_602/0x602 (I.e. Register
| with "new" (to Windows 8) Windows USB driver stack).
******************************************************************************
RELEASE NOTES FOR 10.1.7 (2019-03-26 (DriverVer = 03/26/2019,10.1.7.2399))
Changes for VCP Driver
==============================================================================
MCUSW-473 | Fix length of nul-terminated legacy Dos Name string written to
| HARDWARE\DEVICEMAP\SERIALCOMM Registry key.
MCUSW-483 | Fixed bug for Max Baud rate for CP2101, CP2104, CP2105 and
| CP2108 devices.
******************************************************************************
RELEASE NOTES FOR 10.1.6 (2019-03-19 (DriverVer = 03/15/2019,10.1.6.2388))
Changes for VCP Driver
==============================================================================
MCUSW-445 | Fix a blue-screen system crash bug with handling of ioctl
| IOCTL_SERIAL_WAIT_ON_MASK during power state changes.
******************************************************************************
RELEASE NOTES FOR 10.1.5 (2019-02-19 (DriverVer = 02/19/2019,10.1.5.2368))
Changes for VCP Driver
==============================================================================
MCUSW-414 | Implement an undocumented Registry-configured feature to ignore
| IOCTL_SERIAL_PURGE.
MCUSW-417 | Read many of the Registry "parameter"-type settings first from
| the "parameters key" and then from the "hardware key", with the
| "hardware key" taking precedence (allows "driver wide, all
| devices" setting, but provides the capability to specify per-
| device settings (before we only supported per-device
| settings)).
|
MCUSW-439 | Fixed a bug whereby Close()-Open() on a CP2102N could get USB
| data toggle confused (I.e. issue USB CLEAR_FEATURE(HALT) to
| bulk endpoints to reset data toggle back to DATA0).
MCUSW-449 | Fix a Max Baud Rate bug (use device-specific MaxBauds (from the
| data-sheets): 3 Mbaud for CP2102N, 1 Mbaud for all other CP210x
| devices.).
MCUSW-450 | Fix Verification BSOD (race condition in the VCP device driver
| that can cause double completions): Only call
| DetachForCompletionUNcancelable on success of UNmark as
| cancelable in handling of IOCTL_SERIAL_WAIT_ON_MASK-related
| requests.
******************************************************************************
RELEASE NOTES FOR 10.1.4 (2018-12-07 (DriverVer = 11/26/2018,10.1.4.2290))
Changes for VCP Driver
==============================================================================
MCUSW-134 | Fixed an issue with handling of IOCTL_SERIAL_SET_WAIT_MASK,
| IOCTL_SERIAL_WAIT_ON_MASK, with the SERIAL_EV_RXCHAR event and
| data arriving from the device into the driver. Previously, an
| indication of arriving data was made before making the data
| available, causing, in some conditions, subsequent requests for
| data after notification of data available to not deliver any
| data.
MCUSW-144 | Onecore-based editions of Windows 10 (I.e. Windows 10 IoT Core)
| do not, by design, create PortName entries in the Registry to
| specify the device's legacy DOS name (I.e. COM<n).
| Consequently, VCP enhanced to not treat this as a failing
| condition and to continue without creating legacy COM<n> DOS
| devices.
MCUSW-148 | Rearchitected into two VCP driver packages:
| 1) Windows 7 and later Desktop Editions x86 and x64 driver
| package, and
| 2) Windows Universal (10 and later; Desktop, tablet, mobile,
| embedded) x86, x64, ARM, ARM64 driver package.
MCUSW-214 | Windows 10 Universal driver release (I.e. no Windows 7, 8 or
| 8.1 support)
MCUSW-352 | Workaround to issue where close during receipt of serial data
| caused CP2102N to hang.
MCUSW-369 | Certified for Windows 10 RS5.
MCUSW-393 | Fix bug due to some BaudRate-related math causing a divide-by-
| zero.
MCUSW-396 | Be defensive against the impossible case of getting a NULL
| object in the object completion routine.
******************************************************************************
RELEASE NOTES FOR 10.1.3 (2018-05-29)
Changes for VCP Driver
==============================================================================
MCUSW-326 | Clear DTR on CloseHandle().
******************************************************************************
RELEASE NOTES FOR 10.1.2 (2018-05-14)
Changes for VCP Driver
==============================================================================
MCUSW-134 | Fixed an issue with handling of IOCTL_SERIAL_SET_WAIT_MASK,
| IOCTL_SERIAL_WAIT_ON_MASK, with the SERIAL_EV_RXCHAR event and
| data arriving from the device into the driver. Previously, an
| indication of arriving data was made before making the data
| available, causing, in some conditions, subsequent requests for
| data after notification of data available to not deliver any
| data.
MCUSW-211 | Windows 10 Universal driver release (I.e. no Windows 7, 8 or
| 8.1 support)
MCUSW-288 | Fix IOCTL_SERIAL_GET_PROPERTIES.
MCUSW-291 | Fix IOCTL_SERIAL_GET_PROPERTIES/SERIAL_COMMPROP for CP210x-like
| "Voice MB v2.0" device.
MCUSW-315 | Certified for RS4/1803.
******************************************************************************
RELEASE NOTES FOR 10.1.1 (DriverVer=11/15/2017,10.1.1.1951)
Changes for VCP Driver
==============================================================================
MCUSW-134 | Fixed an issue with handling of IOCTL_SERIAL_SET_WAIT_MASK,
| IOCTL_SERIAL_WAIT_ON_MASK, with the SERIAL_EV_RXCHAR event
| and data arriving from the device into the driver. Previously,
| an indication of arriving data was made before making the data
| available, causing, in some conditions, subsequent requests
| for data after notification of data available to not deliver
| any data.
******************************************************************************
LEGACY HISTORY
--------------
Everything below is the shared development history before creation of the
Windows 10 Universal driver. Everything above is development history of
the Universal driver.
******************************************************************************
RELEASE NOTES FOR 6.7.5 (2017-10-13)
Changes for VCP Driver
==============================================================================
MCUSW-17 | IOCTL_SERIAL_GET_STATUS TransmittedCount fixed.
MCUSW-19 | CP210x_GET_CONFIG_DESCRIPTOR_IOCTL returned byte count fixed.
MCUSW-21 | Revert IOCTL_SERIAL_GET_COMMSTATUS behaviour to return cached
| information (reverse slowdown reported with v6.7.4 in some
| applications)
|
| Improve windbg logging, w.r.t. doing less when logging is not
| enabled (say, Release builds), or when particular subsystem is
| not enabled for logging.
|
MCUSW-110 | Windows 10 certified against RS2 (Creators Update).
MCUSW-207 | In a failed initialization, discard a reference to dynamically
| allocated memory once memory has been freed.
MCUSW-234 | timestamp SHA2 Signatures with SHA2 timestamps
******************************************************************************
RELEASE NOTES FOR 6.7.4.261 (2017/01/30)
- Device Guard compliant
- CP210XFW-747: Add 3 new parallel PIDs one each for the single-, dual- &
quad-port CP210x devices (to be distributed via Windows Update)
- CP210XFW-741: Fix driver to use correct interface string index for the
multi-interface CP210x devices (CP2105 & CP2108). Return iProduct string
for other CP210x devices.
- CP210XFW-713: Add protection against IRP_MJ_CLOSE coming before
IRP_MJ_CLEANUP. In such case EvtFileCleanup callback was called with 0
FileObject, causeing a crash. Serenum is suspected of causing this, even
though there is no proof except that it's present, was introduced recently
and this crash was never registered before.
- CP210XFW-691: Fixed race between timer activation and request cancelation
during processing of read rwquests.
- Changed raw WDF read request timer to our wrapper.
- CP210XFW-693: bugfix: WMI command "wmic path Win32_SerialPort get
Availability^, DeviceID^, Name" is unable to enumerate the port.
- CP210XFW-686: EvtRequestCancel for wait mask IRP crashed because the
request was already completed. It didn't serialize well with other places
that can complete it. It looked like XOff IRP may have the same proble. This
patch is adding an extra check into *all* other EvtRequestCancel functions
to make sure this doesn't happen again.
- Changed IOCTLs returning polled-cached MDMSTS to explicitly read the
status. Use reg value DisableHwAccessInModemStatusIoctls to revert this
new functionality to old behavior.
- Improved debug prints.
- SerialDbgPrintEx used 1K of stack for the string, reduced to 256.
- Resolved many static Code Analysis warnings
- Added accounting for data in chip's TX queue. Added translation of
COMM_STATUS::ulErrors into SERIAL_EV_BREAK and SERIAL_EV_ERR.
- CP210XFW-549, CP210XFW-536, CP210XFW-546: Generate events for
IOCTL_SERIAL_SET_WAIT_MASK from COMM_STATUS::ulErrors. Can be disabled by
DisableCommStatusPolling reg value.
- Added spinlock around ModemStatus change detection. Refactored modem
status event signalling to use common function.
- Move passive level functions into the paged section.
- MCUFW-740: Made device close operation wait for chip's Tx queue to empty.
Added registry settings DisableTxEmptyCheckInClose and
TxEmptyTimeoutOnCloseInMs.
- Improve control transfer debug prints and clean up code, otherwise no
functional changes.
- MCUFW-740: Fixed EV_TXEMPTY to account for bytes in chip's Tx queue.
- MCUFW-740: New functions to sync access to comm error storage from
multiple threads.
- Added DisableTxEmptyCheckInGetCommStatusIoctl reg value.
- Refactor control request I/O. MCUFW-740: Fixed
IOCTL_SERIAL_GET_COMMSTATUS.
- MCUFW-740: Made device close operation wait for chip's Tx queue to empty.
Added registry settings DisableTxEmptyCheckInClose and
TxEmptyTimeoutOnCloseInMs.
- CP210XFW-648: Set a three second timeout on
WdfUsbTargetDeviceSendControlTransferSynchronously().
******************************************************************************
RELEASE NOTES FOR 6.7.3 (2016/03/03)
- Down-rev the verison of KMDF the driver uses (CP210XFW-591. Use version of
KMDF natively included on Windows release)
- Bug fix of blue-screen system crash (CP210XFW-575. driver tries to clear a
Cancel Routine in a Request that doesn't have it.)
******************************************************************************
RELEASE NOTES FOR 6.7.2 (2015/11/23)
- Unified Windows 7, 8, 8.1 & 10 support (XP, Vista and Server 2003
available in version 6.7).
- ARM support added for Windows 10 and Windows 10 IoT Core.
- Silicon Labs-specific Serial Enumeration driver silabenm removed in favor
of the Windows "in-box" serenm.
- UpperFilter Serial Enumeration driver not enabled by default
- Updated to latest Microsoft build tools
- Resolved /W4 compilation warnings
- Resolved code analysis warnings
- Added a registry value ControlHandShakeForcedSetBits that can force
certain bits in the ControlHandShake variable to always be set.
- Add SAL-annotations to API header files.
- Bugfix an invalid memory access on device stop.
- Standardize branding Properties resources across all deliverables.
- Digitally sign all signable deliverables.
- Rewrote driver synchronization for data transmission paths.
- Resolve bugs arising from extended stress test.
- Added diagnostic variables to device extension.
- Bugfix a Write IRP stuck forever cauding bugcheck 9f-4 if call to USB
returns with error.
- Bugfix "packetized write" timeout may fail to act. And improved debug
prints.
- New reg value DisableS0Idle (default: 0) to replace EnablePowerManagewment
(default: 0 which actually ment "enable"). Also, DisableS0Idle=1 now
forces AllowIdleWhileOpen to 0.
- Driver ignores BreakOnEntry, DebugLevel and DebugFlag in registry.
- New CP2108 bug workarounds - GET_LINE_CTL byte swap and tx_empty().
- Fixed crash in read path.
- Simplified, commented and synchronized with NEWSTUFF EvtIoStop and
EvtIoResume.
- Fixed memory leak on device removal when multiple devices are present.
- Bugfix Read IRP may never complete if other read IRPs are already waiting
when it arrives.
- Add CP2102N part numbers. Hnadle new part numbers in
WriteLatch()/ReadLatch().
- Resolve HCK INF warnings that became errors on HLK.
- Bugfix: Potential invalid memory access on device stop.
- Fixed possible memory overrun when writing CP2108 latch.
- Cumulative collection of improvements (due to code analysis, application
of latest toolset, etc.) and bug fixes.
******************************************************************************
RELEASE NOTES FOR 6.7.1 (2015/06/29)
- Added certification for Windows 10 Preview (Note: Windows 10 only;
use v6.7 for Windows prior to Windows 10)
******************************************************************************
RELEASE NOTES FOR 6.7 (2014/04/11)
- Added vendor-specific commands to the driver that do not affect normal
operation with standard CP210x devices.
- Modified write behavior to packetize data as a work around for a rare
USB 2.0 hub behavior seen only in Windows XP (x86).
******************************************************************************
RELEASE NOTES FOR 6.6.1 (2013/10/24)
- Added certification for Windows 8.1
- Added support for CP2108 devices
- Corrected bug where OS would hang on repetition of many rapid open/closes on
certain systems.
******************************************************************************
RELEASE NOTES FOR 6.6
- Moving installer format to DPInst
- Supported under Windows 8
- Corrected bug in total write timeout calculation
- Corrected bug where EV_BREAK event could be misreported based on incoming
data
- Corrected another BSOD corner case regarding write cancellation
******************************************************************************
RELEASE NOTES FOR 6.5.3
- Corrected BSOD corner case for a write cancellation
- Corrected memory leak that occurs when a device is plugged/unplugged
rapidly enough to allow driver startup function to fail
******************************************************************************
RELEASE NOTES FOR 6.5
- Corrected BSOD corner case issue for handling control requests
- Corrected issue where USB 3.0 hubs would deliver data to the driver out
of order
******************************************************************************
RELEASE NOTES FOR 6.4
- Corrected multiple BSOD issues by updating request handling for control
requests to the USB device, and the write completion method
- Corrected device removal routine to also undo the COM port naming in the
registry at removal time instead of when the device is closed after the
removal.
******************************************************************************
RELEASE NOTES FOR 6.3a
- Updated to 3.2 DriverInstaller to correct a bug seen when updating from an
old driver installer version
******************************************************************************
RELEASE NOTES FOR 6.3
- Corrected a bug introduced in 6.2 which caused BSOD during surprise removal.
- Corrected a bug found in I/O cancellation corner case
******************************************************************************
RELEASE NOTES FOR 6.2
- Corrected return value for DeviceIoControl() and other COM API functions
once the device is removed to properly show ERROR_ACCESS_DENIED (0x05)
instead of ERROR_BAD_COMMAND in GetLastError()
- Corrected bug in DTR/RTS reporting latency seen if you set DTR/RTS and ask
for it before the device has reported it to the host - now when it is
written it reads back immediately
- Corrected several USB requests that were improperly defined as device
requests when they are actually interface requests - this doesn't exhibit
and bugs in current single interface devices but was changed to be complete
and correct
- Added support for CP2104 and CP2105 devices
******************************************************************************
RELEASE NOTES FOR 6.1
- Corrected a memory leak which could bog the system down after extended use
of a contiuously opened COM port, and conditionally yield bluescreens on
certain systems
- Corrected a problem where an IO reqest would sometimes return a busy
status to user mode, instead the queue is restarted if necessary before
adding an IO request to the queue
- Corrected a condition which would blue screen on cancelling write request
that hasn't been fully sent out USB
- Corrected the Capabilites return value, which incorrectly reported that
timeouts are not supported
- Corrected several Queue size return values, which affected behavior in the
MSCOMM control
- Corrected DTR/RTS value on device insertion, visible when Serial
Enumeration is disabled
- Corrected the ability to override Baud Rate and Line Control from the INF
file
******************************************************************************
RELEASE NOTES FOR 6.0
- Corrected multiple blue screens and driver hangs related to race
conditions in the driver
- Corrected problem where driver hangs when 4 or more devices are connected
to a single transaction translator hub
- Corrected bugs that prohibited serial enumeration
- Corrected problem where IO requests were not completed/cancelled on a
close
- Corrected problem with dialing out or PPP connections
- Created IO queueing mechanism so that multiple reads, writes, etc. can be
queued and waited on


35
ZigBee/CP210x_Universal_Windows_Driver/SLAB_License_Agreement_VCP_Windows.txt Normal file
View File

@ -0,0 +1,35 @@
LICENSE AGREEMENT
SILICON LABS VCP DRIVER
IMPORTANT: READ CAREFULLY BEFORE AGREEING TO TERMS
THIS PRODUCT CONTAINS THE SILICON LABS VCP DRIVER AND INSTALLER PROGRAMS AND OTHER THIRD PARTY SOFTWARE.TOGETHER THESE PRODUCTS ARE REFERRED TO AS THE "LICENSED SOFTWARE". USE OF THE LICENSED SOFTWARE IS SUBJECT TO THE TERMS OF THIS LICENSE AGREEMENT. DOWNLOADING THE LICENSED SOFTWARE AND INDICATING YOUR CONSENT TO THE TERMS OF THIS LICENSE CONSTITUTES A BINDING AGREMENT BETWEEN SILICON LABORATORIES, INC. ("SILICON LABS") AND YOU OR YOUR EMPLOYER (IF APPLICABLE). IF YOU ARE ACCEPTING THE TERMS OF THIS AGREEMENT ON BEHALF YOUR EMPLOYER, THE TERMS "YOU" AND "YOUR" REFER TO YOUR EMPLOYER. WRITTEN APPROVAL IS NOT A PREREQUISITE TO THE VALIDITY OR ENFORCEABILITY OF THIS AGREEMENT. IF THESE TERMS ARE CONSIDERED AN OFFER BY SILICON LABS, ACCEPTANCE IS EXPRESSLY LIMITED TO THESE TERMS.
IF YOU DO NOT AGREE WITH ALL OF THE TERMS OF THIS LICENSE AGREEMENT, YOU MUST NOT USE THE LICENSED SOFTWARE AND YOU MUST DELETE ALL OF COPIES OF THE LICENSED SOFTWARE FROM YOUR COMPUTER.
1. LICENSE: The Licensed Software is and will remain the property of Silicon Labs or a third party from whom Silicon Labs has the authorization to distribute to you subject to the terms of this Agreement. This Licensed Software is protected by state, federal, and international copyright laws. Subject at all times to your compliance with the terms of this License Agreement, Silicon Labs grants to you a nonexclusive license to use the Licensed Software as described in this License Agreement. Silicon Labs may revoke this license at any time if you fail to comply with the terms of this License Agreement. Certain parts of the Licensed Software, including DPInst.exe, are licensed from Microsoft Corporation. For information concerning licensing DPInst.exe and the redistributable pieces of WDF used in the driver, refer to the license.rtf file in the 7600.16385.1 version of the Windows Driver Kit, available through Microsoft.
2. CONTENTS OF THE LICENSED SOFTWARE: The Licensed Software consists of the following items:
a. Driver binaries
b. INF file that describes the driver installation
c. DPInst.exe that provides the GUI interface to install the drivers
d. XML file that describes the DPInst.exe and GUI items
3. INSTALLATION AND USE RIGHTS:
a. You may download and install the Licensed Software on one or more computers and make any number of copies.
b. You may internally evaluate the Licensed Software. If you elect to use the Licensed Software for any other purpose, including modification and distribution, then the following additional terms apply to you.
c. You may modify only the INF and XML files. You may modify these files with information concerning your company or your company's products.
d. You may not modify the driver binary files or the DPInst.exe files.
e. You may redistribute to your customers the Licensed Software only with the modified INF and XML files. Your redistribution may be in any form, including physical media and Internet downloads.
4. RESTRICTIONS:
a. You may not use the Licensed Software with any integrated circuit products other than those designed and manufactured by Silicon Labs.
b. Except as provided above, you may not redistribute, sublicense, assign, rent or lease any portion of the Licensed Software to any third party.
c. You may not reverse engineer, decompile, disassemble, modify, translate, or make any attempt to discover the source code of the Licensed Software. You may not work around any technical limitation in the Licensed Software.
d. Except as provided above, you may not modify or create derivative works from the Licensed Software.
e. You may not modify or distribute the Licensed Software so that any part of it becomes subject to an excluded license. An excluded license is one that requires, as a condition of use, modification or distribution, that the software be disclosed or distributed in source code form, or that others have the right to modify it.
f. You may not obscure or remove any product identification, copyright or other notices that appear on the Licensed Software, including any notices from third parties.
g. You may not redistribute any modified or unmodified version of the Licensed Software to any third party as a standalone product. You may not redistribute any modified or unmodified version of the Licensed Software to any third party who has not accepted the terms of an end-user license agreement that contains terms at least as protective of Silicon Labs' rights as those contained in this License Agreement.
5. WARRANTY: Silicon Labs does not warrant that the Licensed Software will meet your requirements or that operation of the Licensed Software will be uninterrupted or error-free. You agree that the Licensed Software is provided "AS IS" and that Silicon Labs makes no other warranties regarding the Licensed Software. SILICON LABS DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT, RELATED TO THE LICENSED SOFTWARE, ITS USE OR ANY INABILITY TO USE IT, THE RESULTS OF ITS USE AND THIS AGREEMENT. YOU MAY HAVE OTHER RIGHTS, WHICH VARY FROM STATE TO STATE.
6. DISCLAIMER OF DAMAGES: IN NO EVENT WILL SILICON LABS BE LIABLE TO YOU FOR ANY SPECIAL, CONSEQUENTIAL, INDIRECT, OR SIMILAR DAMAGES, INCLUDING ANY LOST PROFITS OR LOST DATA ARISING OUT OF THE USE OR INABILITY TO USE THE LICENSED SOFTWARE EVEN IF SILICON LABS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE LIMITATION OR EXCLUSION OF LIABILITY FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THE ABOVE LIMITATION OR EXCLUSION MAY NOT APPLY TO YOU. IN NO CASE SHALL SILICON LABS' CUMULATIVE LIABILITY TO YOU FOR ALL PURPOSES EXCEED FIFTY UNITED STATES DOLLARS ($50). The disclaimers and limitations set forth above will apply regardless of whether you accept the Licensed Software.
7. TERM AND TERMINATION: The term of this Agreement and the License granted herein shall begin upon use of the Licensed Software and continue in perpetuity unless you breach any of the obligations set out under this Agreement. Upon any breach of this Agreement by you, the license granted hereunder shall terminate immediately and you shall cease all use of the Licensed Software and return or destroy all copies of the Licensed Software to Silicon Labs immediately. Termination of this License upon your breach is only one remedy available to Silicon Labs. In addition to termination of this Agreement upon your breach, Silicon Labs shall be entitled to seek any and all other available remedies, at law or at equity, arising from your breach. Termination of this Agreement shall not affect your customers' ability to continue using copies of the modified or unmodified Licensed Software they obtained from you.
8. EXPORT: You shall comply with all applicable federal, provincial, state and local laws, regulations and ordinances including but not limited to applicable U.S. Export Administration Laws and Regulations. You shall not export or re-export, or allow the export or re-export of the Licensed Software to any country specified in the then-current Supplement No. 1 to Part 740, or, in violation of the embargo provisions in Part 746, of the U.S. Export Administration Regulations (or any successor regulations or supplement), except in compliance with and with all licenses and approvals required under applicable export laws and regulations, including without limitation, those of the U.S. Department of Commerce.
9. GENERAL: This Agreement will be governed by the laws of the State of Texas and any applicable federal laws or regulations. The waiver by either Party of any default or breach of this Agreement shall not constitute a waiver of any other or subsequent default or breach. This Agreement constitutes the complete and exclusive statement of the mutual understanding between you and Silicon Labs with respect to this subject matter herein. This Agreement may only be modified by a written addendum, which has been signed by both you and Silicon Labs.
BY CLICKING "I ACCEPT THE TERMS OF THIS AGREEMENT" YOU AGREE TO ACCEPT AND COMPLY WITH THE TERMS OF THIS LICENSE AGREEMENT WITH SILICON LABORATORIES INC.


BIN
ZigBee/CP210x_Universal_Windows_Driver/arm/silabser.sys Normal file
View File

Binary file not shown.

BIN
ZigBee/CP210x_Universal_Windows_Driver/arm64/silabser.sys Normal file
View File

Binary file not shown.

BIN
ZigBee/CP210x_Universal_Windows_Driver/silabser.cat Normal file
View File

Binary file not shown.

247
ZigBee/CP210x_Universal_Windows_Driver/silabser.inf Normal file
View File

@ -0,0 +1,247 @@
;/*++
;
;Module Name:
;
; SILABSER.INF
;
; Copyright 2019, Silicon Laboratories Inc.
;
;Abstract:
; Installation INF for Silicon Labs CP210x device
;
;--*/
[Version]
Signature="$WINDOWS NT$"
Class=Ports
ClassGuid={4D36E978-E325-11CE-BFC1-08002BE10318}
Provider=%Provider%
DriverVer = 10/04/2022,11.2.0.167
CatalogFile = silabser.cat
PnpLockDown=1
; ================= Device section =====================
[Manufacturer]
%ManufacturerName%=SiLabsModelsSection, NTamd64.10.0...17134, NTarm.10.0...17134, NTarm64.10.0...17134, NTx86.10.0...17134
; "Architecture must be specified in INF Models sections names" -- meaning lots of
; cut'n'paste duplication in these next four per-Architecture ModelsSections
;Models sections (one per CPU Architecture)
;Models section for installation of x64 driver on Windows 10 and above
[SiLabsModelsSection.NTamd64.10.0...17134]
%USB\VID_10C4&PID_EA60.DeviceDesc% =SiLabsDDInstallSection, USB\VID_10C4&PID_EA60
%USB\VID_10C4&PID_EA63.DeviceDesc% =SiLabsDDInstallSection, USB\VID_10C4&PID_EA63
%USB\VID_10C4&PID_EA70&Mi_00.DeviceDesc%=SiLabsDDInstallSection, USB\VID_10C4&PID_EA70&Mi_00
%USB\VID_10C4&PID_EA70&Mi_01.DeviceDesc%=SiLabsDDInstallSection, USB\VID_10C4&PID_EA70&Mi_01
%USB\VID_10C4&PID_EA71&Mi_00.DeviceDesc%=SiLabsDDInstallSection, USB\VID_10C4&PID_EA71&Mi_00
%USB\VID_10C4&PID_EA71&Mi_01.DeviceDesc%=SiLabsDDInstallSection, USB\VID_10C4&PID_EA71&Mi_01
%USB\VID_10C4&PID_EA71&Mi_02.DeviceDesc%=SiLabsDDInstallSection, USB\VID_10C4&PID_EA71&Mi_02
%USB\VID_10C4&PID_EA71&Mi_03.DeviceDesc%=SiLabsDDInstallSection, USB\VID_10C4&PID_EA71&Mi_03
%USB\VID_10C4&PID_EA7A&Mi_00.DeviceDesc%=SiLabsDDInstallSection, USB\VID_10C4&PID_EA7A&Mi_00
%USB\VID_10C4&PID_EA7A&Mi_01.DeviceDesc%=SiLabsDDInstallSection, USB\VID_10C4&PID_EA7A&Mi_01
%USB\VID_10C4&PID_EA7B&Mi_00.DeviceDesc%=SiLabsDDInstallSection, USB\VID_10C4&PID_EA7B&Mi_00
%USB\VID_10C4&PID_EA7B&Mi_01.DeviceDesc%=SiLabsDDInstallSection, USB\VID_10C4&PID_EA7B&Mi_01
%USB\VID_10C4&PID_EA7B&Mi_02.DeviceDesc%=SiLabsDDInstallSection, USB\VID_10C4&PID_EA7B&Mi_02
%USB\VID_10C4&PID_EA7B&Mi_03.DeviceDesc%=SiLabsDDInstallSection, USB\VID_10C4&PID_EA7B&Mi_03
;Models section for installation of ARM (32-bit) driver on Windows 10 and above
[SiLabsModelsSection.NTarm.10.0...17134]
%USB\VID_10C4&PID_EA60.DeviceDesc% =SiLabsDDInstallSection, USB\VID_10C4&PID_EA60
%USB\VID_10C4&PID_EA63.DeviceDesc% =SiLabsDDInstallSection, USB\VID_10C4&PID_EA63
%USB\VID_10C4&PID_EA70&Mi_00.DeviceDesc%=SiLabsDDInstallSection, USB\VID_10C4&PID_EA70&Mi_00
%USB\VID_10C4&PID_EA70&Mi_01.DeviceDesc%=SiLabsDDInstallSection, USB\VID_10C4&PID_EA70&Mi_01
%USB\VID_10C4&PID_EA71&Mi_00.DeviceDesc%=SiLabsDDInstallSection, USB\VID_10C4&PID_EA71&Mi_00
%USB\VID_10C4&PID_EA71&Mi_01.DeviceDesc%=SiLabsDDInstallSection, USB\VID_10C4&PID_EA71&Mi_01
%USB\VID_10C4&PID_EA71&Mi_02.DeviceDesc%=SiLabsDDInstallSection, USB\VID_10C4&PID_EA71&Mi_02
%USB\VID_10C4&PID_EA71&Mi_03.DeviceDesc%=SiLabsDDInstallSection, USB\VID_10C4&PID_EA71&Mi_03
%USB\VID_10C4&PID_EA7A&Mi_00.DeviceDesc%=SiLabsDDInstallSection, USB\VID_10C4&PID_EA7A&Mi_00
%USB\VID_10C4&PID_EA7A&Mi_01.DeviceDesc%=SiLabsDDInstallSection, USB\VID_10C4&PID_EA7A&Mi_01
%USB\VID_10C4&PID_EA7B&Mi_00.DeviceDesc%=SiLabsDDInstallSection, USB\VID_10C4&PID_EA7B&Mi_00
%USB\VID_10C4&PID_EA7B&Mi_01.DeviceDesc%=SiLabsDDInstallSection, USB\VID_10C4&PID_EA7B&Mi_01
%USB\VID_10C4&PID_EA7B&Mi_02.DeviceDesc%=SiLabsDDInstallSection, USB\VID_10C4&PID_EA7B&Mi_02
%USB\VID_10C4&PID_EA7B&Mi_03.DeviceDesc%=SiLabsDDInstallSection, USB\VID_10C4&PID_EA7B&Mi_03
;Models section for installation of ARM (64-bit) driver on Windows 10 and above
[SiLabsModelsSection.NTarm64.10.0...17134]
%USB\VID_10C4&PID_EA60.DeviceDesc% =SiLabsDDInstallSection, USB\VID_10C4&PID_EA60
%USB\VID_10C4&PID_EA63.DeviceDesc% =SiLabsDDInstallSection, USB\VID_10C4&PID_EA63
%USB\VID_10C4&PID_EA70&Mi_00.DeviceDesc%=SiLabsDDInstallSection, USB\VID_10C4&PID_EA70&Mi_00
%USB\VID_10C4&PID_EA70&Mi_01.DeviceDesc%=SiLabsDDInstallSection, USB\VID_10C4&PID_EA70&Mi_01
%USB\VID_10C4&PID_EA71&Mi_00.DeviceDesc%=SiLabsDDInstallSection, USB\VID_10C4&PID_EA71&Mi_00
%USB\VID_10C4&PID_EA71&Mi_01.DeviceDesc%=SiLabsDDInstallSection, USB\VID_10C4&PID_EA71&Mi_01
%USB\VID_10C4&PID_EA71&Mi_02.DeviceDesc%=SiLabsDDInstallSection, USB\VID_10C4&PID_EA71&Mi_02
%USB\VID_10C4&PID_EA71&Mi_03.DeviceDesc%=SiLabsDDInstallSection, USB\VID_10C4&PID_EA71&Mi_03
%USB\VID_10C4&PID_EA7A&Mi_00.DeviceDesc%=SiLabsDDInstallSection, USB\VID_10C4&PID_EA7A&Mi_00
%USB\VID_10C4&PID_EA7A&Mi_01.DeviceDesc%=SiLabsDDInstallSection, USB\VID_10C4&PID_EA7A&Mi_01
%USB\VID_10C4&PID_EA7B&Mi_00.DeviceDesc%=SiLabsDDInstallSection, USB\VID_10C4&PID_EA7B&Mi_00
%USB\VID_10C4&PID_EA7B&Mi_01.DeviceDesc%=SiLabsDDInstallSection, USB\VID_10C4&PID_EA7B&Mi_01
%USB\VID_10C4&PID_EA7B&Mi_02.DeviceDesc%=SiLabsDDInstallSection, USB\VID_10C4&PID_EA7B&Mi_02
%USB\VID_10C4&PID_EA7B&Mi_03.DeviceDesc%=SiLabsDDInstallSection, USB\VID_10C4&PID_EA7B&Mi_03
;Models section for installation of x86 driver on Windows 10 and above
[SiLabsModelsSection.NTx86.10.0...17134]
%USB\VID_10C4&PID_EA60.DeviceDesc% =SiLabsDDInstallSection, USB\VID_10C4&PID_EA60
%USB\VID_10C4&PID_EA63.DeviceDesc% =SiLabsDDInstallSection, USB\VID_10C4&PID_EA63
%USB\VID_10C4&PID_EA70&Mi_00.DeviceDesc%=SiLabsDDInstallSection, USB\VID_10C4&PID_EA70&Mi_00
%USB\VID_10C4&PID_EA70&Mi_01.DeviceDesc%=SiLabsDDInstallSection, USB\VID_10C4&PID_EA70&Mi_01
%USB\VID_10C4&PID_EA71&Mi_00.DeviceDesc%=SiLabsDDInstallSection, USB\VID_10C4&PID_EA71&Mi_00
%USB\VID_10C4&PID_EA71&Mi_01.DeviceDesc%=SiLabsDDInstallSection, USB\VID_10C4&PID_EA71&Mi_01
%USB\VID_10C4&PID_EA71&Mi_02.DeviceDesc%=SiLabsDDInstallSection, USB\VID_10C4&PID_EA71&Mi_02
%USB\VID_10C4&PID_EA71&Mi_03.DeviceDesc%=SiLabsDDInstallSection, USB\VID_10C4&PID_EA71&Mi_03
%USB\VID_10C4&PID_EA7A&Mi_00.DeviceDesc%=SiLabsDDInstallSection, USB\VID_10C4&PID_EA7A&Mi_00
%USB\VID_10C4&PID_EA7A&Mi_01.DeviceDesc%=SiLabsDDInstallSection, USB\VID_10C4&PID_EA7A&Mi_01
%USB\VID_10C4&PID_EA7B&Mi_00.DeviceDesc%=SiLabsDDInstallSection, USB\VID_10C4&PID_EA7B&Mi_00
%USB\VID_10C4&PID_EA7B&Mi_01.DeviceDesc%=SiLabsDDInstallSection, USB\VID_10C4&PID_EA7B&Mi_01
%USB\VID_10C4&PID_EA7B&Mi_02.DeviceDesc%=SiLabsDDInstallSection, USB\VID_10C4&PID_EA7B&Mi_02
%USB\VID_10C4&PID_EA7B&Mi_03.DeviceDesc%=SiLabsDDInstallSection, USB\VID_10C4&PID_EA7B&Mi_03
;DDInstall section
[SiLabsDDInstallSection]
AddReg=silabser.AddReg
CopyFiles=Silabser_CopyFiles_FileListSection
FeatureScore=0x40
;DDInstall.Services section
[SiLabsDDInstallSection.Services]
AddService = silabser,0x00000002,silabser.AddService
[silabser.AddService]
DisplayName = %silabser.SvcDesc%
ServiceType = 1
StartType = 3
ErrorControl = 1
ServiceBinary = %12%\silabser.sys
AddReg = silabser.AddService.AddReg
; Per-Service-level registry entries (the "parameters key")
[silabser.AddService.AddReg]
HKR, Parameters\Wdf, ForceLogsInMiniDump, 0x00010001, 1
HKR, Parameters, DebugLevel, 0x00010001, 0
HKR, Parameters, DebugFlag, 0x00010001, 0x1c01817
;To break on entry if requested in Parameters
;HKR, Parameters, BreakOnEntry, 0x00010001,1
; common registry entries
; Per-Driver-level registry entries (the "software key")
[silabser.AddReg]
HKR,,NTMPDriver,,silabser.sys
HKR,,RateLimitPurgeMS, 0x10001, 0x64, 0x00, 0x00, 0x00
;To override the default value for BaudRate/LineControl
HKR,,OverrideDefaultPortSettings, 0x10001, 01,00,00,00
HKR,,InitialBaudRate, 0x10001, 00,C2,01,00 ;115200 initial baud rate
HKR,,InitialLineControl,, "8N1" ;8-bits, No parity, 1 stop bit
HKR,,PortSubClass,1,01
HKR,,EnumPropPages32,,"MsPorts.dll,SerialPortPropPageProvider"
;Prepare to hack ControlHandShake
;HKR,,ControlHandShakeForcedSetBits,0x10001,01,00,00,00
;DDInstall.HW section
[SiLabsDDInstallSection.HW]
AddReg=SiLabsDDInstallSection.HW.AddReg
; Per-device-level registry entries (the "hardware key")
[SiLabsDDInstallSection.HW.AddReg]
;Amount of time the device must be idle before idling out
HKR,,"SelectiveSuspendTimeout",0x00010001,10000
HKR,,"DisableHwAccessInModemStatusIoctls",0x00010001,1
HKR,,"DisableIoctlIOCTL_SERIAL_PURGE",0x00010001,1
; Attention! The EnablePowerManagewment value is no longer supported.
; To disable Selective Suspend, uncomment the following line:
; HKR,,"DisableS0Idle",0x00010001,1
; opt-in to DFx
HKR,"WDF","WdfDirectedPowerTransitionEnable",0x00010001,1
;To disable the checking TxEmpty in Get Comm Status Ioctl, uncomment the following line:
;HKR,,"DisableTxEmptyCheckInGetCommStatusIoctl",0x00010001,1
;To disable the checking TxEmpty in Ioctl Wait Mask, uncomment the following line:
;HKR,,"DisableTxEmptyCheckInIoctlWaitMask",0x00010001,1
;To disable the checking remaining data in Tx queue, uncomment the following line:
;HKR,,"DisableTxEmptyCheckInClose",0x00010001,1
;To disable purge In close, uncomment the following line:
;HKR,,"DisablePurgeInClose",0x00010001,1
;Don't use polling to get Comm Status, uncomment the following line:
;HKR,,"DisableCommStatusPolling",0x00010001,1
;To Skipping external naming, uncomment the following line:
;HKR,,"SerialSkipExternalNaming",0x00010001,1
;To allow device to idle with an open handle, uncomment the following line:
;HKR,,"AllowIdleWhileOpen",0x00010001,1
;To set the maximum time the close operation will wait for Tx queue to empty, uncomment the following line:
;HKR,,"TxEmptyTimeoutOnCloseInMs",0x00010001,30000
;To disable the port, uncomment the following line:
;HKR,,"DisablePort",0x00010001,1
;To obtain the polling interval to get information from the CP210x device, uncomment the following line:
;HKR,,"EventMaskPollingInterval",0x00010001,80
; To obtain the number of read requests that the framework will queue to receive data from the CP210x device, uncomment the following line:
;HKR,,"ContinuousReaderNumPendingReads",0x00010001,1
; To use of the custom 'dummy wait' code, uncomment the following line:
;HKR,,"EnableCustomWait",0x00010001,1
; To set DTR for serial, uncomment the following line:
;HKR,,"SetDTROnOpen",0x00010001,1
; To set RTS for serial, uncomment the following line:
;HKR,,"SetRTSOnOpen",0x00010001,1
[Silabser_CopyFiles_FileListSection]
silabser.sys
[SourceDisksNames]
1=%Disk_Description%,"silabser.cat"
[SourceDisksFiles.amd64]
silabser.sys = 1,\x64
[SourceDisksFiles.arm]
silabser.sys = 1,\arm
[SourceDisksFiles.arm64]
silabser.sys = 1,\arm64
[SourceDisksFiles.x86]
silabser.sys = 1,\x86
[DestinationDirs]
Silabser_CopyFiles_FileListSection = 12 ; 13 = Driver package's Driver Store directory (%WINDIR%\System32\DriverStore\FileRepository); 12 = Drivers directory (%SystemRoot%\system32\drivers)) (make sure "ServiceBinary =" matches usage of 12 vs. 13)
;---------------------------------------------------------------;
[Strings]
; For provider, enter your Company Legal/Official/Long/Full Name
Provider="Silicon Laboratories Inc."
; For ManufacturerName, enter your Company "Colloquial" Name
ManufacturerName="Silicon Labs"
Disk_Description= "Silicon Labs CP210x USB to UART Bridge Installation Disk"
USB\VID_10C4&PID_EA60.DeviceDesc= "Silicon Labs CP210x USB to UART Bridge"
USB\VID_10C4&PID_EA63.DeviceDesc= "Silicon Labs CP210x USB to UART Bridge"
USB\VID_10C4&PID_EA70&Mi_00.DeviceDesc="Silicon Labs Dual CP2105 USB to UART Bridge: Enhanced COM Port"
USB\VID_10C4&PID_EA70&Mi_01.DeviceDesc="Silicon Labs Dual CP2105 USB to UART Bridge: Standard COM Port"
USB\VID_10C4&PID_EA71&Mi_00.DeviceDesc="Silicon Labs Quad CP2108 USB to UART Bridge: Interface 0"
USB\VID_10C4&PID_EA71&Mi_01.DeviceDesc="Silicon Labs Quad CP2108 USB to UART Bridge: Interface 1"
USB\VID_10C4&PID_EA71&Mi_02.DeviceDesc="Silicon Labs Quad CP2108 USB to UART Bridge: Interface 2"
USB\VID_10C4&PID_EA71&Mi_03.DeviceDesc="Silicon Labs Quad CP2108 USB to UART Bridge: Interface 3"
USB\VID_10C4&PID_EA7A&Mi_00.DeviceDesc="Silicon Labs Dual CP2105 USB to UART Bridge: Enhanced COM Port"
USB\VID_10C4&PID_EA7A&Mi_01.DeviceDesc="Silicon Labs Dual CP2105 USB to UART Bridge: Standard COM Port"
USB\VID_10C4&PID_EA7B&Mi_00.DeviceDesc="Silicon Labs Quad CP2108 USB to UART Bridge: Interface 0"
USB\VID_10C4&PID_EA7B&Mi_01.DeviceDesc="Silicon Labs Quad CP2108 USB to UART Bridge: Interface 1"
USB\VID_10C4&PID_EA7B&Mi_02.DeviceDesc="Silicon Labs Quad CP2108 USB to UART Bridge: Interface 2"
USB\VID_10C4&PID_EA7B&Mi_03.DeviceDesc="Silicon Labs Quad CP2108 USB to UART Bridge: Interface 3"
silabser.SvcDesc="Silicon Labs CP210x USB to UART Bridge Driver"

BIN
ZigBee/CP210x_Universal_Windows_Driver/x64/silabser.sys Normal file
View File

Binary file not shown.

BIN
ZigBee/CP210x_Universal_Windows_Driver/x86/silabser.sys Normal file
View File

Binary file not shown.