On 27 Oct 2020, 01:21p, Avon said the following...
13:18:12 Poll BINKP node via address lookup: 21:4/100
13:18:12 Queued 1 files (1,636 bytes) for 21:4/100
13:18:12 1-Polling 21:4/100 on slot 1 via BINKP
13:18:12 1-Connecting to net4.fsxnet.nz on port 24560
13:18:13 1-Using address 184.155.113.241
13:18:19 1-Unable to connect
13:18:20 Polled 1 systems
Yup, I have it down right now. Can you take a look and make sure there
is no packet password set? I've gotten three message archives from
1/100, and all three were flagged as 'Security Violation'.
I checked, there is no packet password set, only TIC/Areafix and BinkP
Yup, I have it down right now. Can you take a look and make sure ther is no packet password set? I've gotten three message archives from 1/100, and all three were flagged as 'Security Violation'.
I checked, there is no packet password set, only TIC/Areafix and BinkP
Ok, I must have something not set right then. I just got another archive from 1/100 that HPT changed to .sec for security violation. However, if
I unzip it manually, the packets will toss just fine...
would it help if I set things to raw packets for 4/100 from 1/100 ?
BTW, is Hub 3 down? I'm seeing connections failed...
You're still using my container image?
If so, you can do SSL - just map a port to 24553 and it should work.
Ok, I must have something not set right then. I just got another arch from 1/100 that HPT changed to .sec for security violation. However, I unzip it manually, the packets will toss just fine...
would it help if I set things to raw packets for 4/100 from 1/100 ?
Alright. I think I've got it working now... I kept thinking it was a 'packer' issue somewhere. I actually had my directories swapped between BinkD and Husky. The insecure BinkD was my secure HPT, and vice versa.
The packets were a security violation because they didn't have packet passwords in them... <smack>
Would you like me to start sending compressed packets again?
You can if you want. I'll probably leave the hub to sent raw packets...
You're still using my container image?
If so, you can do SSL - just map a port to 24553 and it should work.
I've just done that, so if you and Avon want to try using the SSL connection, give it a shot. It should work now.
I've just done that, so if you and Avon want to try using the SSL connection, give it a shot. It should work now.
Nope not quite working yet
16:48:03 1-Connected by IPV4 SSL to 184.155.113.241
16:48:03 1-Connection dropped (Completed transfer Received TLS alert
Ok, thank you. Right now I'm having 'unzip' issues... Any message archive that comes in is getting set as a security violation...
Would you like me to start sending compressed packets again?You can if you want. I'll probably leave the hub to sent raw packets...
Also, Deon, is it possible to change the time within the container? The time keeps throwing me off... :)
So, any idea how to define multiple iport numbers in BinkD, without it throwing an error?
So I had some troubles with raw packets with HPT.
There was a scenario, where HPT create the same packet (filename) for
more than1 downlink, and the last one created was the winner.
Probably also delaying between "toss", "scan" and "pack" helped (ie: a 1 seconddelay)...
Ok, thank you. Right now I'm having 'unzip' issues... Any message arc that comes in is getting set as a security violation...
Hmm... pretty much all my links use zip - so I have not problems.
So, I'm going to guess you have something special with your hpt config?
Also, Deon, is it possible to change the time within the container? T time keeps throwing me off... :)
Ahh, its probably set to Melbouren time <chuckle> :)
-v /etc/localtime:/etc/localtime
No I have only ever used one to run BinkD on say 24557 etc.
I must have something else on this system listening on 24553...
Nope not quite working yet
16:48:01 Poll BINKP node via address lookup: 21:4/100
16:48:01 Queued 4 files (8,044 bytes) for 21:4/100
16:48:01 1-Polling 21:4/100 on slot 1 via BINKP
16:48:01 1-Connecting to net4.fsxnet.nz on port 24553
16:48:01 1-Using address 184.155.113.241
16:48:03 1-Connected by IPV4 SSL to 184.155.113.241
16:48:03 1-Connection dropped (Completed transfer Received TLS alert message 16:48:03 1-Connection lost
16:48:03 1-Authorization failed
16:48:03 Polled 1 systems
So, any idea how to define multiple iport numbers in BinkD, without it throwing an error?
I've tried:
iport 24560
iport 24553
I'll give that a shot when I restart the container. Oh, when you stop a container and restart, is there a way to do that without having to rename it first?
If so, you should have binkd running on the default ports inside the container- ie: 24554, but map the port outside of the container , ie -p 24560:24554.This would accept connections from outside the container on port 24560 andpatch them through into the container on port 24554.
(Thus you could still have something else outside the container use 24554.)
If you want binkd to receive multiple ports, you can patch them through withstarting docker.
-p <HOST PORT>:24554 and you can have many -p definitions that you want, goingto the same port inside the container.
If so, you should have binkd running on the default ports inside the container- ie: 24554, but map the port outside of the container , ie -p 24560:24554.This would accept connections from outside the container on port 24560 andpatch themWhy didn't I think of that when I was typing in the command? I've got it running on 24554 inside the container now.
through into the container on port 24554.
Would I forward like -p 24553:24554? That doesn't seem right. I do have -p 24560:24554 -p 24553:24553 in the command line now.
You can delete it - infact you can start it with --rm so that it auto deleteswhen it stops.
I have made it ephemeral safe, as long as you put the data you want to keepinto a path defined by -v
No, binkd doesnt understand TLS.
The container has an NGINX server in it, listening on 24553 - and will "forward" to localhost 24554.
openssl s_client -quiet -alpn binkp -connect "net4.fsxnet.nz:24553"
And you should see the familiar binkd welcome message.
You can delete it - infact you can start it with --rm so that it auto deleteswhen it stops.
That will make it easier. I think I have about 10 containers now showing when I run 'docker ps -a'.
openssl s_client -quiet -alpn binkp -connect "net4.fsxnet.nz:24553"
And you should see the familiar binkd welcome message.
I sure did! Thank you, again. :)
I can again poll using SSL so this is good :)
On 27 Oct 2020, 12:08p, deon said the following...
You're still using my container image?
Yup. It's finally up and running correctly... :)
If so, you can do SSL - just map a port to 24553 and it should
work.
I've just done that, so if you and Avon want to try using the SSL connection, give it a shot. It should work now.
Re: Re: Hub Change
By: Black Panther to deon on Mon Oct 26 2020 11:01 pm
Would I forward like -p 24553:24554? That doesn't seem right. I do
have -p 24560:24554 -p 24553:24553 in the command line now.
No, binkd doesnt understand TLS.
The container has an NGINX server in it, listening on 24553 - and will "forward" to localhost 24554.
deon, can you enable TLS 1.3 for nginx in the the docker image? it's just one config line.
I only get a TLS 1.2 session with 21:4/100 and 21:3/100
Re: Hub Change
By: Oli to deon on Tue Oct 27 2020 12:58 pm
deon, can you enable TLS 1.3 for nginx in the the docker image?
it's just one config line. I only get a TLS 1.2 session with
21:4/100 and 21:3/100
Can you test it with 3/100 - should be enabled now.
If it works, I'll commit the change to the image and publish it.
Can you test it with 3/100 - should be enabled now.No, not yet.
openssl s_client -tls1_3 -connect net3.fsxnet.nz:24553
Re: Hub Change
By: Oli to deon on Wed Oct 28 2020 09:14 am
Can you test it with 3/100 - should be enabled now.
No, not yet.
openssl s_client -tls1_3 -connect net3.fsxnet.nz:24553
OK, think I got it now...
| Sysop: | altere |
|---|---|
| Location: | Houston, TX |
| Users: | 60 |
| Nodes: | 4 (0 / 4) |
| Uptime: | 06:16:30 |
| Calls: | 516 |
| Files: | 7,007 |
| Messages: | 286,765 |