After much ado I think I have finally sorted IPv6 connectivity to the 1/100 HUB.
This also means 21:1/101 should be reachable via IPv6 as is 3:770/1
After much ado I think I have finally sorted IPv6 connectivity to the
1/100 HUB.
This also means 21:1/101 should be reachable via IPv6 as is 3:770/1
Yup, looks reachable now from my end, except for port 24556:
This also means 21:1/101 should be reachable via IPv6 as is 3:770/1
Just tried our connectoin to 3:770/1 as well and it's also working:
--------------------- POLL v1.12 A47 2021/09/29 Wed, Oct 13 2021 (loglevel 1) + 2021.10.13 04:10:13 Sending to all nodes of session type ALL + 2021.10.13 04:10:13 Queued 1 files (305 bytes) for 3:770/1
+ 2021.10.13 04:10:13 1-Polling 3:770/1 on slot 1 via BINKP
+ 2021.10.13 04:10:13 1-Connecting to agency.bbs.nz on port 24554
🎉 🤪 🥳
¿ ¿ ¿
???
On 13 Oct 2021 at 04:27p, Oli pondered and said...
🎉 🤪 🥳
???
I'm assuming you are seeing question marks or strange characters.
In a UTF-8 terminal, they are icons :)
it's emojiish for exciting / very good / time to celebrate / party on
On 14 Oct 2021 at 10:00a, Oli pondered and said...
it's emojiish for exciting / very good / time to celebrate / party
on
thanks sir.. indeed!
now to try and get the secure stuff working on 24553 .. not yet sure how ;-)
On 14 Oct 2021 at 10:00a, Oli pondered and said...
it's emojiish for exciting / very good / time to celebrate / party
on
thanks sir.. indeed!
now to try and get the secure stuff working on 24553 .. not yet sure how ;-)
Re: Re: 21:1/100
By: Avon to Oli on Thu Oct 14 2021 05:09 pm
¿ ¿ ¿
???
I'm assuming you are seeing question marks or strange characters.
_ _ _
???
I'm assuming you are seeing question marks or strange characters.
Yup, in Mystic it looks like trying to BBS over a modem during a
lightning storm... ;)
https://ibb.co/k170Cwr
On 13 Oct 2021, Avon said the following...
After much ado I think I have finally sorted IPv6 connectivity to the 1/100 HUB.
Yup, looks reachable now from my end, except for port 24556:
now to try and get the secure stuff working on 24553 .. not yet sure h ;-)
# apt-get install nginx
then add the following to /etc/nginx.conf
stream {
server {
listen 24553 ssl;
listen [::]:24553 ssl;
ssl_protocols TLSv1.2 TLSv1.3;
ssl_certificate /srv/certs/fidonet-rsa.key;
ssl_certificate_key /srv/certs/fidonet-rsa.crt;
ssl_certificate /srv/certs/fidonet-ed25519.key;
ssl_certificate_key /srv/certs/fidonet-ed25519.crt;
proxy_pass 127.0.0.1:24554;
}
}
You also need to create a cert (can be self-signed). Of course you can
put the certs in any path you like.
ecdsa cert:
$ openssl genpkey -algorithm ed25519 > fidonet-ed25519.key
$ openssl req -new -x509 -nodes -days 1200 -key fidonet-ed25519.key -out fidonet-ed25519.crt -text -subj "/CN=localhost"
rsa cert:
openssl req -new -newkey rsa -days 1200 -nodes -x509 -keyout fidonet-rsa.key -out fidonet-rsa.crt -text -subj "/CN=localhost"
Alternatively use a letsencrypt cert.
restart nginx:
$ systemctl restart nginx
then add the following to /etc/nginx.conf
stream {
server {
listen 24553 ssl;
listen [::]:24553 ssl;
ssl_protocols TLSv1.2 TLSv1.3;
ssl_certificate /srv/certs/fidonet-rsa.key;
ssl_certificate_key /srv/certs/fidonet-rsa.crt;
ssl_certificate /srv/certs/fidonet-ed25519.key;
ssl_certificate_key /srv/certs/fidonet-ed25519.crt;
proxy_pass 127.0.0.1:24554;
}
}
OK done, but commented out for now while I sort the certs.
Question, what is /srv dir for? This sort of stuff?
You also need to create a cert (can be self-signed). Of course you
can put the certs in any path you like.
OK, so not /srv necessarily?
I know little about this (yet) but am I correct to assume a Lets Encrypt cert would be better / more well known? Not sure I am stating this correctly.
Why for the self signed stuff 1200 days?
If I created self signed stuff
how could anyone trust it compared to something like Lets Encrypt that is third party?
Alternatively use a letsencrypt cert.
Something I'm thinking (will wait until I hear from you) may be the
better way to go? Also something I have not ever done but would like to learn how etc. :)
restart nginx:
$ systemctl restart nginx
OK will hold off that until I sort the certs.
Will I also need to have something configured in BinkD to talk to nginx?
I'd better read the nginx man.
Can you test 24556 IPv6 please. I think this is now sorted.
It works! Here's some fireworks to celibate! :)
OK will hold off that until I sort the certs.
$ nginx -t
is also very helpful for testing the config (it doesn't start nginx).
On 15 Oct 2021 at 08:12a, Oli pondered and said...
OK will hold off that until I sort the certs.
$ nginx -t
is also very helpful for testing the config (it doesn't start
nginx).
Have sent you a netmail. The certs don't seem to be trusted.
Have sent you a netmail. The certs don't seem to be trusted.
The example configuration was wrong, I swapped key and crt files.
| Sysop: | digital man |
|---|---|
| Location: | Riverside County, California |
| Users: | 1,042 |
| Nodes: | 16 (0 / 16) |
| Uptime: | 01:34:58 |
| Calls: | 500,919 |
| Calls today: | 6 |
| Files: | 109,372 |
| D/L today: |
16,787 files (2,541M bytes) |
| Messages: | 305,076 |
| Posted today: | 7 |