RainManHood<------
Guys,
I am not sure what I am doing wrong in here.
I got 2 findonet point and while the Main one (2:250/1.2) works ok, I got the second one trying to send Netmail using the Main 2:250/1.2.
I got the second point 2:341/66.86 configured as an AKA 1 in exec/scfg
and the sbbsecho.ini
----
[node:2:341/66]
Name = zruspas-Spain
Comment =
Archive = None
PacketType = 2+
PacketPwd =
AreaFix = true
AreaFixPwd = pwd
SessionPwd = pwd
TicFilePwd = pwd
Inbox =
Outbox =
Passive = false
Direct = false
Notify = true
Keys =
Status = Normal
Route = 2:341/66
GroupHub =
BinkpHost = bbs.zruspas.org
BinkpPort = 24554
BinkpPoll = true
BinkpAllowPlainAuth = false
BinkpAllowPlainText = true
BinkpSourceAddress =
----
For the other node:
---
[node:2:250/1]
Name = FIDO UK
Comment = Vince Coen
Archive = None
PacketType = 2+
PacketPwd =
AreaFix = true
AreaFixPwd = pwd
SessionPwd = pwd
TicFilePwd = pwd
Inbox =
Outbox =
Passive = false
Direct = false
Notify = true
Keys =
Status = Normal
Route = 2:250/1
GroupHub = LOCAL-UK,FIDO-UK,FIDO2-NEWS
BinkpHost = applewood.dtdns.net
BinkpPort = 24554
BinkpPoll = true
BinkpAllowPlainAuth = false
BinkpAllowPlainText = true
BinkpSourceAddress =
---
I am sure something very simple is there I am overlooking.
RainManHood<------
Re: Multiple Fido Points --- Synchronet config
By: Rmh to All on Fri Jun 01 2018 06:15 pm
Guys,
I am not sure what I am doing wrong in here.
I got 2 findonet point and while the Main one (2:250/1.2) works ok, I got the second one trying to send Netmail using the Main 2:250/1.2.
I got the second point 2:341/66.86 configured as an AKA 1 in exec/scfg
and the sbbsecho.ini
----
[node:2:341/66]
Name = zruspas-Spain
Comment =
Archive = None
PacketType = 2+
PacketPwd =
AreaFix = true
AreaFixPwd = pwd
SessionPwd = pwd
TicFilePwd = pwd
Inbox =
Outbox =
Passive = false
Direct = false
Notify = true
Keys =
Status = Normal
Route = 2:341/66
GroupHub =
BinkpHost = bbs.zruspas.org
BinkpPort = 24554
BinkpPoll = true
BinkpAllowPlainAuth = false
BinkpAllowPlainText = true
BinkpSourceAddress =
----
For the other node:
---
[node:2:250/1]
Name = FIDO UK
Comment = Vince Coen
Archive = None
PacketType = 2+
PacketPwd =
AreaFix = true
AreaFixPwd = pwd
SessionPwd = pwd
TicFilePwd = pwd
Inbox =
Outbox =
Passive = false
Direct = false
Notify = true
Keys =
Status = Normal
Route = 2:250/1
GroupHub = LOCAL-UK,FIDO-UK,FIDO2-NEWS
BinkpHost = applewood.dtdns.net
BinkpPort = 24554
BinkpPoll = true
BinkpAllowPlainAuth = false
BinkpAllowPlainText = true
BinkpSourceAddress =
---
I am sure something very simple is there I am overlooking.
I spoke with the node and this is what's happening from the other side:
When calling from 2:341/66
====
+ 12:12 [20586] call to 2:341/66.86@fidonet
12:12 [20586] trying 185.5.52.214...
12:12 [20586] connected
+ 12:12 [20586] session with 34819.s.time4vps.cloud (185.5.52.214)
- 12:12 [20586] OPT CRAM-MD5-38051eced112af072baf8509df9d9ebc CRYPT
+ 12:12 [20586] Remote requests MD mode
+ 12:12 [20586] Remote requests CRYPT mode
- 12:12 [20586] SYS Unicyber BBS
- 12:12 [20586] ZYZ Gonzalo Fernandez Ordas
- 12:12 [20586] LOC Hertfordshire,UK
- 12:12 [20586] NDL 115200,TCP,BINKP
- 12:12 [20586] TIME Sat Jun 02 2018 10:12:52 GMT+0000 (UTC)
- 12:12 [20586] VER BinkIT/2.3,JSBinkP/1.106,sbbs3.17a/Linux binkp/1.1
+ 12:12 [20586] addr: 2:250/1.2@fidonet
+ 12:12 [20586] addr: 2:341/86@fidonet
? 12:12 [20586] called 2:341/66.86@fidonet, but remote has no such AKA
+ 12:12 [20586] done (to 2:341/66.86@fidonet, failed, S/R: 0/0 (0/0 bytes))
12:12 [20586] session closed, quitting...
====
THere it shows 2:341/86 and not the point 2:341/66.86, then it says the AKA does not exist!
When calling myself to the node (som from 2:341/66.86 to 2:341/66)
=====
01 Jun 17:48:48 [23114] session with 34819.s.time4vps.cloud (185.5.52.214)
- 01 Jun 17:48:48 [23114] OPT CRYPT
+ 01 Jun 17:48:48 [23114] Remote requests CRYPT mode
- 01 Jun 17:48:48 [23114] SYS Unicyber BBS
- 01 Jun 17:48:48 [23114] ZYZ Gonzalo Fernandez Ordas
- 01 Jun 17:48:48 [23114] LOC Hertfordshire,UK
- 01 Jun 17:48:48 [23114] NDL 115200,TCP,BINKP
- 01 Jun 17:48:48 [23114] TIME Fri Jun 01 2018 15:49:01 GMT+0000 (UTC)
- 01 Jun 17:48:48 [23114] VER BinkIT/2.3,JSBinkP/1.106,sbbs3.17a/Linux binkp/1.1
+ 01 Jun 17:48:49 [23114] addr: 2:341/66.86@fidonet
+ 01 Jun 17:48:49 [23114] addr: 2:250/1.2@fidonet
? 01 Jun 17:48:49 [23114] unexpected password digest from the remote
+ 01 Jun 17:48:49 [23114] done (from 2:341/66.86@fidonet, OK, S/R: 0/0 (0/0 bytes))
=====
But I got the AKA defined!
As a test I polled your node and the response looks correct:
Attempting poll for node 2:250/1.2@fidonet
JSBinkP/1.106 callout to 2:250/1.2@fidonet started
Connection to bbs.unicyber.co.uk:24554 successful
Sent M_NUL command args: SYS Vertrauen
Sent M_NUL command args: ZYZ Rob Swindell
Sent M_NUL command args: LOC Riverside County, California
Sent M_NUL command args: NDL 115200,TCP,BINKP
Sent M_NUL command args: TIME Sat Jun 02 2018 14:23:29 GMT-0700 (PDT)
Sent M_NUL command args: VER BinkIT/2.4,JSBinkP/1.106,sbbs3.17a/Linux binkp/1.1 Sent M_ADR command args: 1:103/705@fidonet 21:1/183@fsxnet
Got M_NUL command args: OPT CRAM-MD5-0f1906a94da36a376d20a94c571ff2cf CRYPT Got M_NUL command args: SYS Unicyber BBS
Got M_NUL command args: ZYZ Gonzalo Fernandez Ordas
Got M_NUL command args: LOC Hertfordshire,UK
Got M_NUL command args: NDL 115200,TCP,BINKP
Got M_NUL command args: TIME Sat Jun 02 2018 21:23:29 GMT+0000 (UTC)
Got M_NUL command args: VER BinkIT/2.3,JSBinkP/1.106,sbbs3.17a/Linux binkp/1.1 Peer version: BinkIT/2.3,JSBinkP/1.106,sbbs3.17a/Linux binkp/1.1 Got M_ADR command args: 2:250/1.2@fidonet 2:341/66.86@fidonet
Attempting poll for node 2:250/1.2@fidonet
JSBinkP/1.106 callout to 2:250/1.2@fidonet started
Connection to bbs.unicyber.co.uk:24554 successful
Sent M_NUL command args: SYS Vertrauen
Sent M_NUL command args: ZYZ Rob Swindell
Sent M_NUL command args: LOC Riverside County, California
Sent M_NUL command args: NDL 115200,TCP,BINKP
Sent M_NUL command args: TIME Sat Jun 02 2018 14:23:29 GMT-0700 (PDT)
Sent M_NUL command args: VER BinkIT/2.4,JSBinkP/1.106,sbbs3.17a/Linux binkp/1.1 Sent M_ADR command args: 1:103/705@fidonet 21:1/183@fsxnet
Got M_NUL command args: OPT CRAM-MD5-0f1906a94da36a376d20a94c571ff2cf CRYPT Got M_NUL command args: SYS Unicyber BBS
Got M_NUL command args: ZYZ Gonzalo Fernandez Ordas
Got M_NUL command args: LOC Hertfordshire,UK
Got M_NUL command args: NDL 115200,TCP,BINKP
Got M_NUL command args: TIME Sat Jun 02 2018 21:23:29 GMT+0000 (UTC)
Got M_NUL command args: VER BinkIT/2.3,JSBinkP/1.106,sbbs3.17a/Linux binkp/1.1 Peer version: BinkIT/2.3,JSBinkP/1.106,sbbs3.17a/Linux binkp/1.1 Got M_ADR command args: 2:250/1.2@fidonet 2:341/66.86@fidonet
So... I'd say the problem is on the polling node's side.
RainManHood<---
Attempting poll for node 2:250/1.2@fidonet
JSBinkP/1.106 callout to 2:250/1.2@fidonet started
Connection to bbs.unicyber.co.uk:24554 successful
Sent M_NUL command args: SYS Vertrauen
Sent M_NUL command args: ZYZ Rob Swindell
Sent M_NUL command args: LOC Riverside County, California
Sent M_NUL command args: NDL 115200,TCP,BINKP
Sent M_NUL command args: TIME Sat Jun 02 2018 14:23:29 GMT-0700
(PDT) Sent M_NUL command args: VER
BinkIT/2.4,JSBinkP/1.106,sbbs3.17a/Linux binkp/1.1 Sent M_ADR
command args: 1:103/705@fidonet 21:1/183@fsxnet Got M_NUL command
args: OPT CRAM-MD5-0f1906a94da36a376d20a94c571ff2cf CRYPT Got M_NUL
command args: SYS Unicyber BBS Got M_NUL command args: ZYZ Gonzalo
Fernandez Ordas Got M_NUL command args: LOC Hertfordshire,UK
Got M_NUL command args: NDL 115200,TCP,BINKP
Got M_NUL command args: TIME Sat Jun 02 2018 21:23:29 GMT+0000 (UTC)
Got M_NUL command args: VER BinkIT/2.3,JSBinkP/1.106,sbbs3.17a/Linux
binkp/1.1 Peer version: BinkIT/2.3,JSBinkP/1.106,sbbs3.17a/Linux
binkp/1.1 Got M_ADR command args: 2:250/1.2@fidonet
2:341/66.86@fidonet
So... I'd say the problem is on the polling node's side.
This is when I get when I send a request to the areamgr:
----
ZDDDDDDDDDDDDDDDDDDDDDDDDzzzz
3 Subj: Areafix reply: security violation
3 Attr: Private
3 To : Gonzalo Fernandez Ordas (2:250/1.2) #1
3 From: areamgr (2:341/66)
3 Date: Sun Jun 03 2018 05:07 pm UTC (1.8 hours from now) @DDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDzzzzzz
your system is unknown
Following is the original message text --------------------------------------
%HELP
--------------------------------------
-+- hpt/lnx 1.9.0-cur 01-07-10 areafix
-----
RainManHood<------
I am sending a netmail to 2:341/66 and I see in the netmail editor: 2:341/66.86 (which is correctly my point).
But when the netmail is being sent it says: in the sbbsecho logs:
--
03-06-2018 15:07:59 Created NetMail (5.msg) from Gonzalo Fernandez Ordas (2:250/1.2) to areamgr (2:341/66), attr: 0181, subject: <subject>
For some reason it's just getting the Main from my system (2:250/1.2) and not AKA 1 which should be areamgr (2:341/66.86)
Ahh.. AKA matching is a tricky corner of FTN to be sure. I have three AKA's in one of my nets and have the one I want to send mail as listed first so that is the AKA that is used when sending mail from that net.
Ahh.. AKA matching is a tricky corner of FTN to be sure. I have three AKA's in one of my nets and have the one I want to send mail as listed first so that is the AKA that is used when sending mail from that net.
It sounds to me like you should apply for a node and connect to all your links with that without having this issue.
You could switch your aka's to list this point first and recycle sbbs. I'm thinking (but don't know) that might cause problems in your setup too.
RainManHood<------
correction... "automated aka matching is a tricky [...]"
every traditional FTN package that i'm aware of that allows you to write netmail has a specific option in the header to choose the FROM name (generally your's) and the FROM address... this is generally only available when editing the netmail message's header...
THe Node's tosser says:
---
1 17:07:57 Start
1 17:07:57 Start tossing...
7 17:07:57 pkt: /var/spool/ftn/unsecure/s9rfrnys.tos [2:250/1.2]
A 17:07:57 pkt: /var/spool/ftn/unsecure/s9rfrnys.tos No Link for 2:250/1.2, processing only Netmail
8 17:07:58 areafix: Security violation from 2:250/1.2
---
It sounds to me like you should apply for a node and connect to all your links with that without having this issue.
That might be actually a solution for it...
ANy tips on how to setup a node?
Tooling of nay sort for the Nodelist Al?
correction... "automated aka matching is a tricky [...]"
Well said.. :)
every traditional FTN package that i'm aware of that allows you to
write netmail has a specific option in the header to choose the FROM
name (generally your's) and the FROM address... this is generally
only available when editing the netmail message's header...
If I understood Rmh's situation correctly Synchronet did this when the message was written and at scan SBBSecho used the first AKA in the
list.
Having two points in the same zone sounds like a recipe for disaster.
Using an editor like Golded or timed and a tosser like FMail, FE or
hpt might be possible but I don't think I'll try that myself.. :)
Re: Multiple Fido Points --- Synchronet config
By: Digital Man to Rmh on Sat Jun 02 2018 02:34 pm
Attempting poll for node 2:250/1.2@fidonet
JSBinkP/1.106 callout to 2:250/1.2@fidonet started
Connection to bbs.unicyber.co.uk:24554 successful
Sent M_NUL command args: SYS Vertrauen
Sent M_NUL command args: ZYZ Rob Swindell
Sent M_NUL command args: LOC Riverside County, California
Sent M_NUL command args: NDL 115200,TCP,BINKP
Sent M_NUL command args: TIME Sat Jun 02 2018 14:23:29 GMT-0700 (PDT) Sent M_NUL command args: VER BinkIT/2.4,JSBinkP/1.106,sbbs3.17a/Linux binkp/1.1 Sent M_ADR command args: 1:103/705@fidonet 21:1/183@fsxnet Got M_NUL command args: OPT CRAM-MD5-0f1906a94da36a376d20a94c571ff2cf CRYPT Got M_NUL command args: SYS Unicyber BBS
Got M_NUL command args: ZYZ Gonzalo Fernandez Ordas
Got M_NUL command args: LOC Hertfordshire,UK
Got M_NUL command args: NDL 115200,TCP,BINKP
Got M_NUL command args: TIME Sat Jun 02 2018 21:23:29 GMT+0000 (UTC) Got M_NUL command args: VER BinkIT/2.3,JSBinkP/1.106,sbbs3.17a/Linux binkp/1.1 Peer version: BinkIT/2.3,JSBinkP/1.106,sbbs3.17a/Linux binkp/1.1 Got M_ADR command args: 2:250/1.2@fidonet 2:341/66.86@fidonet
So... I'd say the problem is on the polling node's side.
Digital Man,
This is when I get when I send a request to the areamgr:
----
ZDDDDDDDDDDDDDDDDDDDDDDDDzzzz
3 Subj: Areafix reply: security violation
3 Attr: Private
3 To : Gonzalo Fernandez Ordas (2:250/1.2) #1
3 From: areamgr (2:341/66)
3 Date: Sun Jun 03 2018 05:07 pm UTC (1.8 hours from now) @DDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDzzzzzz
your system is unknown
Following is the original message text --------------------------------------
%HELP
--------------------------------------
-+- hpt/lnx 1.9.0-cur 01-07-10 areafix
-----
For some reason it's just getting the Main from my system (2:250/1.2) and not AKA 1 which should be areamgr (2:341/66.86)
From the strong you showed me before it just picks up the 1st fidonet definition front he command args (by the look of it..)
RainManHood<---
Digital Man,
There is something I don't have entirely clear.
I am sending a netmail to 2:341/66 and I see in the netmail editor: 2:341/66.86 (which is correctly my point).
But when the netmail is being sent it says: in the sbbsecho logs:
--
03-06-2018 15:07:59 Created NetMail (5.msg) from Gonzalo Fernandez Ordas (2:250/1.2) to areamgr (2:341/66), attr: 0181, subject: <subject>
every traditional FTN package that i'm aware of that allows you to write netmail has a specific option in the header to choose the FROM name (generally your's) and the FROM address... this is generally only available when editing the netmail message's header...
RainManHood<---
Re: Multiple Fido Points --- Synchronet config
By: mark lewis to Al on Sun Jun 03 2018 11:50 pm
every traditional FTN package that i'm aware of that allows you to write netmail has a specific option in the header to choose the FROM name (generally your's) and the FROM address... this is generally only available when editing the netmail message's header...
Not sure Synchronet got anything like that. I haven't seen it though.
Maybe Digital Man or Deuce might know ...
It sounds to me like you should apply for a node and connect to all
your links with that without having this issue.
That might be actually a solution for it...
Having two points in the same zone sounds like a recipe for disaster.
it is not... it is no different than having multiple nodes in the same zone... you can even have multiple points with the same boss with no problems... the key factor is being abl eto choose the desired from name and address...
NOTE: when i say "from name" i mean being able to choose between your real name and any nicknames associated with the same user account... the from address choice would be from the system's address list since they are all valid for that system...
Using an editor like Golded or timed and a tosser like FMail,
FE or hpt might be possible but I don't think I'll try that myself.. :)
i wouldn't try it with than and sbbs unless they fully support sbbs...
Synchronet did *not* allow the NetMail author to choose the system AKA
for the NetMail origin/source address... until today. Now it does, but this change requires use of SBBSecho v3.05 or later as well.
So... I'd say the problem is on the polling node's side.
Digital Man,
This is when I get when I send a request to the areamgr:
----
Not really sure what you're trying to tell me here.
RainManHood<---
03-06-2018 15:07:59 Created NetMail (5.msg) from Gonzalo Fernandez
Ordas (2:250/1.2) to areamgr (2:341/66), attr: 0181, subject:
<subject>
Okay, I think I addressed this with SBBSecho rev 3.84. Update from CVS and try that.
RainManHood<---
As usual, thanks very much for your help and continous support, that's very much appreciated.
That might be actually a solution for it...
It probably would but after reading mark lewis's comments and seeing the changes Digital Man has made to SBBSecho I don't think you'll need to do that. A point address should work for you, even two (or more) of them.. :)
RainManHood<---
As usual, thanks very much for your help and continous support, that's
very much appreciated.
Thank you for the detailed problem report.
RainManHood<---
As usual, thanks very much for your help and continous support, that's
very much appreciated.
Thank you for the detailed problem report.
| Sysop: | Winzlo |
|---|---|
| Location: | Minnesota, USA |
| Users: | 11 |
| Nodes: | 16 (0 / 16) |
| Uptime: | 495929:17:09 |
| Calls: | 82 |
| Files: | 1,070 |
| D/L today: |
27 files (11,920K bytes) |
| Messages: | 286,851 |