23 Feb
2023
23 Feb
'23
1:37 p.m.
That's exactly why we dictate all the keys. We send you a complete setup
file which you import into your client/router/whatever.
The file looks like this (this one does not work!!) Pull this into your
client application and bingo; you're on the 44Net. Note how we do not share
our private key? We do tell you what your private key is going to be but we
only share our public key. We even use a different PSK for each client.
And, we only support 44net routing. No internet access via us.
[Interface]
Address = 44.56.0.220/26
ListenPort = 51844
PrivateKey = AD/zd1stXzehSRe68YHf+lKGlquitR8FN0YAAL1YZWs=
[Peer]
PublicKey = nW9HaYfZeM5opuqiBdPMb1kW0Eo42+CKH6SxWvKmLWM=
PresharedKey = Ky17b00UsqJ+mcZ3QjL720UWWQZKXKLKI1H4SaB8IQk=
AllowedIPs = 44.0.0.0/9, 44.128.0.0/10
Endpoint = hamgatepa.ampr.org:51844
On Thu, Feb 23, 2023 at 1:56 PM lleachii--- via 44net <
44net(a)mailman.ampr.org> wrote:
It was noted that some users would find key
generation, etc. to be quite
advanced/expert.
It's interesting that was noted.
A main reason I understood some commercial companies generate a private
key for you - is so that they can offer you a complete Wireguard
configuration file for setup purposes. They would be unable to do that via
a public-key-only exchange/setup with the remote peer.
73,
- Lynwood
KB3VWG
_______________________________________________
44net mailing list -- 44net(a)mailman.ampr.org
To unsubscribe send an email to 44net-leave(a)mailman.ampr.org