Hey Oli,

I'm going to be switching routers, I have a MikroTik Hex router that I'm going to use for a while.

The downside is I'll loose the Tor config, so if you are still connecting over Tor you'll need to change to binkp/binkps. (From memory you have those details).

I could look at moving the tor stuff to the Pi as well - its not something I know a lot about, so if there is something quick and easy (and a docker container), I can set it up quickly, otherwise it'll go on the list of things I need (and want) to do.

...ëîåï

... I predict that today will be remembered until tomorrow!
--- SBBSecho 3.11-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

deon wrote (2020-12-13):

Hey Oli,

I'm going to be switching routers, I have a MikroTik Hex router that I'm going to use for a while.

The downside is I'll loose the Tor config, so if you are still connecting over Tor you'll need to change to binkp/binkps. (From memory you have
those details).

No problem, I have both addresses in the binkd node config and can easily switch between them.

#node 21:3/100@fsxnet uvacs3kkxy....p4lxamniid.onion
node 21:3/100@fsxnet -pipe "gnutls-cli --logfile /dev/null --no-ca-verification --strict-tofu --disable-sni *H:24553"

but binkps (TLS) is down too at the moment (the TLS proxy answers the connection, but then I get a timeout)

I could look at moving the tor stuff to the Pi as well - its not
something I know a lot about, so if there is something quick and easy
(and a docker container), I can set it up quickly, otherwise it'll go on the list of things I need (and want) to do.

It's just two config lines in /etc/tor/torrc:

HiddenServiceDir /var/lib/tor/hidden_service/binkd
HiddenServicePort 24554 127.0.0.1:24554

For most mails your node polls my node over TLS anyway. The Tor stuff is just nice to have experimental stuff (and IMHO easier to setup than TLS).

---
* Origin: (21:3/102)

deon wrote (2020-12-13):

Hey Oli,

I'm going to be switching routers, I have a MikroTik Hex router that I'm going to use for a while.

The IPv6 address doesn't work.

---
* Origin: (21:3/102)

Re: Tor
By: Oli to deon on Sun Dec 13 2020 11:59 am

Hey Oli,

deon wrote (2020-12-13):

I'm going to be switching routers, I have a MikroTik Hex router that I'm going to use for a while.

The IPv6 address doesn't work.

Thanks - yes, I'm aware.

Because of the new router, all my IPs changed (argh...) - and I'm about to change ISPs anyway (which hopefully will give me static IPv4 and IPv6 addresses).

So I've turned off IPv6 temporarily, and I'll get it back on soon.

Everything should resolve to an IPv4 address for now.

...ëîåï

... Men and women are two different species, descended from different animals. --- SBBSecho 3.11-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

Re: Tor
By: Oli to deon on Sun Dec 13 2020 11:50 am

Howdy,

but binkps (TLS) is down too at the moment (the TLS proxy answers the connection, but then I get a timeout)

Ahh, I lost my internal DNS which this was dependant on.

I think I fixed it - but havent test it yet.

...ëîåï

... I've got Parkinson's disease. And he's got mine.
--- SBBSecho 3.11-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

deon wrote (2020-12-14):

The IPv6 address doesn't work.

Thanks - yes, I'm aware.

Because of the new router, all my IPs changed (argh...) - and I'm about
to change ISPs anyway (which hopefully will give me static IPv4 and IPv6 addresses).

So I've turned off IPv6 temporarily, and I'll get it back on soon.

Everything should resolve to an IPv4 address for now.

I still get an IPv6 address from DNS and binkd tries to connect to it by default.

$ dig aaaa net3.fsxnet.nz

;; ANSWER SECTION:
net3.fsxnet.nz. 3600 IN CNAME n3.z21.bbs.leenooks.net. n3.z21.bbs.leenooks.net. 300 IN CNAME fidohub.leenooks.net. fidohub.leenooks.net. 300 IN CNAME l.dlcm.co.
l.dlcm.co. 300 IN CNAME ae380d0e19b1.sn.mynetname.net. ae380d0e19b1.sn.mynetname.net. 60 IN AAAA 2001:8003:f00:3204:9445:1867:cc21:bf4c

---
* Origin: (21:3/102)