BINKPS is alterant.leenooks.net:24556
alterego wrote to All <=-
I've just moved Hub 3 to Linux, and changed the software to binkd and
hpt. (IE: Hub 3 is no longer a BBS - I didnt really want to maintain a second BBS).
BINKP is alterant.leenooks.net:24555
BINKPS is alterant.leenooks.net:24556
EMSI TELNET is alternat.leenooks.net:60177
EMSI TCP is alternant.leenooks.net:60179
My own binkps port is 24553. I took the BBS machine off the DMZ it had been on previously yesterday and forgot to open port 24553 in my router but it's all fixed up now. :)
What package are you using to support/offer EMSI? Thanks.
BINKP is alterant.leenooks.net:24555
BINKPS is alterant.leenooks.net:24556
BINKP is alterant.leenooks.net:24555
BINKPS is alterant.leenooks.net:24556
Is there a recommended/"standard" port for binkps? I just enabled
binkps on realitycheckBBS on port 24553.
Is there a recommended/"standard" port for binkps? I just enabled binkps on realitycheckBBS on port 24553.
Is there a recommended/"standard" port for binkps? I just enabled
binkps on realitycheckBBS on port 24553.
I dont think there is a standard, but the common seems to be 24553 for those who enable it for their first instance.
24553 is what we have been using as standard. Digital Man applied to the port authority (whoever that is) to have that port officially assigned but I don't know if that did or will happen.
24553 is what we have been using as standard. Digital Man applied
to the port authority (whoever that is) to have that port
officially assigned but I don't know if that did or will happen.
IIRC it got rejected.
Hello alterego,
24553 is what we have been using as standard. Digital Man applied
to the port authority (whoever that is) to have that port
officially assigned but I don't know if that did or will happen.
IIRC it got rejected.
I don't know what the reasoning for that rejection was.
Maybe there is
not enough of us using binkps or port 24553?
Re: Re: Hub 3
By: Blue White to alterego on Thu Apr 09 2020 04:23 pm
BINKP is alterant.leenooks.net:24555
BINKPS is alterant.leenooks.net:24556
Is there a recommended/"standard" port for binkps?
I just enabled binkps on realitycheckBBS on port 24553.
Oli wrote to Al <=-
That would be a catch-22.
"Note: It is inappropriate to use a port number until your application
has been approved for assignment."
from https://www.iana.org/form/ports-services
poindexter FORTRAN wrote to Blue White <=-
Re: Re: Hub 3
By: Blue White to alterego on Thu Apr 09 2020 04:23 pm
BINKP is alterant.leenooks.net:24555
BINKPS is alterant.leenooks.net:24556
Is there a recommended/"standard" port for binkps? I just enabled
binkps on realitycheckBBS on port 24553.
alterego wrote to Blue White <=-
What package are you using to support/offer EMSI? Thanks.
Good old ifcico.
Its really buggy, so when I get time, I'm going to see if I can take a look at the source and atleast fix the core dumps... ...deon
Oli wrote to Al <=-
That would be a catch-22.
"Note: It is inappropriate to use a port number until your
application has been approved for assignment."
from https://www.iana.org/form/ports-services
Sounds like we all need to use 24553 and make this a de facto standard.
But a port number is not enough for a standard (de facto or official). Weneed a nodelist flag, SRV record, agreement on the TLS
versions and how certificatesShould the nodelist flag support more parameters than host
are verified. Do clients have to support SNI, ESNI, TLSA records, ALPN?
and port? ...
Oli wrote to poindexter FORTRAN <=-
But a port number is not enough for a standard (de facto or official).
We need a nodelist flag, SRV record, agreement on the TLS versions and
how certificates are verified. Do clients have to support SNI, ESNI,
TLSA records, ALPN? Should the nodelist flag
Oli wrote to poindexter FORTRAN <=-
But a port number is not enough for a standard (de facto or
official). We need a nodelist flag, SRV record, agreement on the
TLS versions and how certificates are verified. Do clients have to
support SNI, ESNI, TLSA records, ALPN? Should the nodelist flag
Or, we could use binkps by arrangement, the same way we arrange session passwords with mailers we communicate with on a regular basis.
Baby steps.
Hub 3 might be a bit iffy today. I'm trying to track down 2 issues that I cant seem to create in my test envrionment.
The 2nd issue has me stumped. I've been doing some updates after the last couple of days, and I started seeing session failures.
I've spent the last 24-36 hrs debugging and tracing and cant figure it out, so I'm now wondering if it is the upstream system (or my testing hasnt triggered the sequence for the problem).
Jay/Stephan/Drew if you get this I'd be keen to see your logs and maybe turn it up (especially if you are successful getting mail from other systems).
Jay/Stephan/Drew if you get this I'd be keen to see your logs and maybe turn it up (especially if you are successful getting mail from other systems).
Sure, I can send some logs your way.
I can see mail flowing between *most* nodes connected to Hub 3, with the exception of 3:
* 21:1/100 - although a test message just got a response from 6/100
which is via 1/100.
* 21:3/110
I don't know if it's related/relevant but when I poll you I'm using IPv6 & SSL in binkd:
Just need to figure how I broke it. So I'll be progressing each commit until I find the commit that broke it - please bear with me if you see mail errors while I'm chasing this. (Least I know which commit works.)
For hub 3 nodes, sorry, I've been down the last few days.
Hub 3 is back online and processing mail.
Hub 3 is back online and processing mail.
Sorry for the outage folks :)
On 04 Sep 2024, deon said the following...
Hub 3 is back online and processing mail.
Heeeeeey! We're back! :)
Hub 3 is back online and processing mail.
Sorry for the outage folks :)
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 368 |
Nodes: | 16 (2 / 14) |
Uptime: | 41:14:38 |
Calls: | 7,885 |
Calls today: | 3 |
Files: | 12,962 |
Messages: | 5,787,515 |