I thoroughly checked the setup for my FTN number both on my end and on the hub end, and I cannot figure out why the node number comes up incorrectly when I do an areafix command.

I assigned node /35 to this system and it shows as node /0 when I get my areafix response.

The end result is that I don't get a response. It says that the account doesn't exist.

Has anyone ever had this problem? I AM getting messages inbound and outbound, so the conferences are configured correctly. Just cannot get areafix to work.

Mike Dippel
hobby-bbs.com

---
þ Synchronet þ Hobby BBS - Sun City Center, FL
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Incorrect Node Number
By: Mike Dippel to All on Wed Nov 17 2021 10:48 pm

I thoroughly checked the setup for my FTN number both on my end and on the hub end, and I cannot figure out why the node number comes up incorrectly when I do an areafix command.

I assigned node /35 to this system and it shows as node /0 when I get my areafix response.

The end result is that I don't get a response. It says that the account doesn't exist.

Has anyone ever had this problem? I AM getting messages inbound and outbound, so the conferences are configured correctly. Just cannot get areafix to work.

No.

I asked you the following question already (among others), which you never answered:

When you send that netmail message, what FTN address does the BBS tell you that its sending from?

Answering that question would be a good start towards solving your problem.

I also suggested, more than once, that you look at your sbbsecho.log file for when that netmail message gets exported and packed - it will log the source/origin address. What is that address? You never answered that question either.
--
digital man

Synchronet "Real Fact" #125:
Synchronet switched from CVS to Git on August 23, 2020 - git.synchro.net
Norco, CA WX: 57.3øF, 80.0% humidity, 0 mph SSE wind, 0.00 inches rain/24hrs --- SBBSecho 3.14-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

From the sbbsecho.log:

2021-11-18 09:07:09 Exporting NetMail message #79 from Mike Dippel to areafix (954:895/1)
2021-11-18 09:07:09 Created NetMail (1.msg) from Mike Dippel (954:895/35) to areafix (954:895/1), attr: 0183, subject: HOBBYBBS
2021-11-18 09:07:09 Packing NetMail (1.msg) from Mike Dippel (954:895/35) to areafix (954:895/1), attr: 0183, subject: HOBBYBBS
2021-11-18 09:07:09 Node (954:895/1) successfully locked via: ../fido/outbound.3ba\037f0001.bsy
2021-11-18 09:07:09 Adding NetMail (1.msg) to new packet for 954:895/1: ../fido/outbound.3ba\037f0001.cut
2021-11-18 09:07:10 Deleting C:\sbbs\fido\netmail\1.msg (from line 5350) 2021-11-18 09:07:10 Touching outgoing semfile: ../data/binkout.now
2021-11-18 09:07:10 Writing 1 areas to ../data/badareas.lst
2021-11-18 09:07:10 Deleting ../fido/outbound.3ba\037f0001.bsy (from line 3040) 2021-11-18 09:07:10 Deleting C:\sbbs\ctrl\sbbsecho.bsy (from line 3046) 2021-11-18 09:07:10 SBBSecho (PID 4936) exiting with error level 0, NetMail(0 imported, 1 exported, 1 packed)

I believe the last part of the log is referring to an import of HobbyNet areas. I AM receiving echomail now.

The FTN sending from is:
Mike Dippel (954:895/0)

That node is not defined anywhere in the setup.

Mike Dippel

---
ï¿­ Synchronet ï¿­ Hobby BBS - Sun City Center, FL
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Incorrect Node Number
By: Mike Dippel to Digital Man on Thu Nov 18 2021 09:16 am

From the sbbsecho.log:

2021-11-18 09:07:09 Exporting NetMail message #79 from Mike Dippel to areafix (954:895/1)
2021-11-18 09:07:09 Created NetMail (1.msg) from Mike Dippel (954:895/35) to areafix (954:895/1), attr: 0183, subject: HOBBYBBS
2021-11-18 09:07:09 Packing NetMail (1.msg) from Mike Dippel (954:895/35) to areafix (954:895/1), attr: 0183, subject: HOBBYBBS
2021-11-18 09:07:09 Node (954:895/1) successfully locked via: ../fido/outbound.3ba\037f0001.bsy
2021-11-18 09:07:09 Adding NetMail (1.msg) to new packet for 954:895/1: ../fido/outbound.3ba\037f0001.cut
2021-11-18 09:07:10 Deleting C:\sbbs\fido\netmail\1.msg (from line 5350) 2021-11-18 09:07:10 Touching outgoing semfile: ../data/binkout.now 2021-11-18 09:07:10 Writing 1 areas to ../data/badareas.lst
2021-11-18 09:07:10 Deleting ../fido/outbound.3ba\037f0001.bsy (from line 3040) 2021-11-18 09:07:10 Deleting C:\sbbs\ctrl\sbbsecho.bsy (from line 3046) 2021-11-18 09:07:10 SBBSecho (PID 4936) exiting with error level 0, NetMail(0 imported, 1 exported, 1 packed)

I believe the last part of the log is referring to an import of HobbyNet areas. I AM receiving echomail now.

The FTN sending from is:
Mike Dippel (954:895/0)

That node is not defined anywhere in the setup.

Everything in the log indicates it's exporting/sending from 954:895/35, so it does not appear from the information given, to be a problem on the sending/SBBS/SBBSecho side. The next step would be to examine the incoming packet (.pkt file) or stored message (.msg file) on the receiving side to see what sending/origin address is reflected in those files.

There are multiple places where the originating node number can be (and often is) represented in a packet or stored message file. If you use a utility like pktdump (included with Synchronet, for dumping packets) or fmsgdump (also included with Synchronet, for dumping FTN .msg files), you can see the header fields and the metadata (i.e. FTN kludge lines, aka control paragraphs) and that could perhaps give us the clue needed to solve your mystery.
--
digital man

Synchronet "Real Fact" #124:
The Loons - "Ten Inch Men" with Rob on drums: https://youtu.be/EBSlpojM4j0 Norco, CA WX: 61.8øF, 71.0% humidity, 0 mph SW wind, 0.00 inches rain/24hrs
--- SBBSecho 3.14-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

On 11/18/2021 9:25 AM, Digital Man wrote to Mike Dippel:

Re: Incorrect Node Number
By: Mike Dippel to Digital Man on Thu Nov 18 2021 09:16 am

From the sbbsecho.log:

2021-11-18 09:07:09 Exporting NetMail message #79 from Mike Dippel to areafix (954:895/1)
2021-11-18 09:07:09 Created NetMail (1.msg) from Mike Dippel (954:895/35) to
areafix (954:895/1), attr: 0183, subject: HOBBYBBS
2021-11-18 09:07:09 Packing NetMail (1.msg) from Mike Dippel (954:895/35) to
areafix (954:895/1), attr: 0183, subject: HOBBYBBS
2021-11-18 09:07:09 Node (954:895/1) successfully locked via: ../fido/outbound.3ba\037f0001.bsy
2021-11-18 09:07:09 Adding NetMail (1.msg) to new packet for 954:895/1: ../fido/outbound.3ba\037f0001.cut
2021-11-18 09:07:10 Deleting C:\sbbs\fido\netmail\1.msg (from line 5350) 2021-11-18 09:07:10 Touching outgoing semfile: ../data/binkout.now 2021-11-18 09:07:10 Writing 1 areas to ../data/badareas.lst
2021-11-18 09:07:10 Deleting ../fido/outbound.3ba\037f0001.bsy (from line 3040) 2021-11-18 09:07:10 Deleting C:\sbbs\ctrl\sbbsecho.bsy (from line 3046) 2021-11-18 09:07:10 SBBSecho (PID 4936) exiting with error level 0, NetMail(0 imported, 1 exported, 1 packed)

I believe the last part of the log is referring to an import of HobbyNet areas. I AM receiving echomail now.

The FTN sending from is:
Mike Dippel (954:895/0)

That node is not defined anywhere in the setup.

Everything in the log indicates it's exporting/sending from 954:895/35, so it
does not appear from the information given, to be a problem on the sending/SBBS/SBBSecho side. The next step would be to examine the incoming packet (.pkt file) or stored message (.msg file) on the receiving side to see
what sending/origin address is reflected in those files.

There are multiple places where the originating node number can be (and often
is) represented in a packet or stored message file. If you use a utility like
pktdump (included with Synchronet, for dumping packets) or fmsgdump (also included with Synchronet, for dumping FTN .msg files), you can see the header
fields and the metadata (i.e. FTN kludge lines, aka control paragraphs) and that could perhaps give us the clue needed to solve your mystery.

From the log file on my hub (PXecho.log) a typical response is:

16:43:02 - Orig 954:895/35 Dest 954:895/1
16:43:02 + New Netmail From Mike Dippel (954:895/0)
16:43:02 ! Insecured AREAFIX Request. Node Address : 954:895/0
16:43:02 % AREAFIX Request Activated!
16:43:02 - Using Host Address: 954:895/1
16:43:02 ! AREAFIX SECURITY ERROR!
16:43:02 ! No Account Established
16:43:02 > Creating AreaFix Request Report for 954:895/0

I can see from this that Mike Dippel is assigned 954:895/0 on the Synchronet system.
How do I change the node address to /35

I will have to take some time to locate the pktdump results.

Mike Dippel

--- Platinum Xpress/Win/WINServer v7.0
* Origin: The Hobby Line! BBS (3:640/1116)

On 11/18/2021 9:25 AM, Digital Man wrote to Mike Dippel:

There are multiple places where the originating node number can be (and often
is) represented in a packet or stored message file. If you use a utility like
pktdump (included with Synchronet, for dumping packets) or fmsgdump (also included with Synchronet, for dumping FTN .msg files), you can see the header
fields and the metadata (i.e. FTN kludge lines, aka control paragraphs) and that could perhaps give us the clue needed to solve your mystery.
--

Could you please provide the executable to use pktdump?

Mike
--- Platinum Xpress/Win/WINServer v7.0
* Origin: The Hobby Line! BBS (3:640/1116)

Re: RE: Incorrect Node Number
By: Mike Dippel to Digital Man on Thu Nov 18 2021 03:05 pm

On 11/18/2021 9:25 AM, Digital Man wrote to Mike Dippel:

Re: Incorrect Node Number
By: Mike Dippel to Digital Man on Thu Nov 18 2021 09:16 am

From the sbbsecho.log:

2021-11-18 09:07:09 Exporting NetMail message #79 from Mike Dippel to areafix (954:895/1)
2021-11-18 09:07:09 Created NetMail (1.msg) from Mike Dippel (954:895/35) to
areafix (954:895/1), attr: 0183, subject: HOBBYBBS
2021-11-18 09:07:09 Packing NetMail (1.msg) from Mike Dippel (954:895/35) to
areafix (954:895/1), attr: 0183, subject: HOBBYBBS
2021-11-18 09:07:09 Node (954:895/1) successfully locked via: ../fido/outbound.3ba\037f0001.bsy
2021-11-18 09:07:09 Adding NetMail (1.msg) to new packet for 954:895/1: ../fido/outbound.3ba\037f0001.cut
2021-11-18 09:07:10 Deleting C:\sbbs\fido\netmail\1.msg (from line 5350) 2021-11-18 09:07:10 Touching outgoing semfile: ../data/binkout.now 2021-11-18 09:07:10 Writing 1 areas to ../data/badareas.lst
2021-11-18 09:07:10 Deleting ../fido/outbound.3ba\037f0001.bsy (from line 3040) 2021-11-18 09:07:10 Deleting C:\sbbs\ctrl\sbbsecho.bsy (from line 3046) 2021-11-18 09:07:10 SBBSecho (PID 4936) exiting with error level 0, NetMail(0 imported, 1 exported, 1 packed)

I believe the last part of the log is referring to an import of HobbyNet areas. I AM receiving echomail now.

The FTN sending from is:
Mike Dippel (954:895/0)

That node is not defined anywhere in the setup.

Everything in the log indicates it's exporting/sending from 954:895/35, so it
does not appear from the information given, to be a problem on the sending/SBBS/SBBSecho side. The next step would be to examine the incoming packet (.pkt file) or stored message (.msg file) on the receiving side to see
what sending/origin address is reflected in those files.

There are multiple places where the originating node number can be (and often
is) represented in a packet or stored message file. If you use a utility like
pktdump (included with Synchronet, for dumping packets) or fmsgdump (also included with Synchronet, for dumping FTN .msg files), you can see the header
fields and the metadata (i.e. FTN kludge lines, aka control paragraphs) and that could perhaps give us the clue needed to solve your mystery.

From the log file on my hub (PXecho.log) a typical response is:

16:43:02 - Orig 954:895/35 Dest 954:895/1
16:43:02 + New Netmail From Mike Dippel (954:895/0)
16:43:02 ! Insecured AREAFIX Request. Node Address : 954:895/0
16:43:02 % AREAFIX Request Activated!
16:43:02 - Using Host Address: 954:895/1
16:43:02 ! AREAFIX SECURITY ERROR!
16:43:02 ! No Account Established
16:43:02 > Creating AreaFix Request Report for 954:895/0

I can see from this that Mike Dippel is assigned 954:895/0 on the Synchronet system.

No, what you're seeing is that your PX software is interpretting the packet or stored message as from that /0 address. That does not mean that Mike Dippel was "assigned" a /0 address on the Synchronet system.

How do I change the node address to /35

We're trying to determine that. I asked you too look at the packets or stored messages on your receiving/areafix side.

I will have to take some time to locate the pktdump results.

Okay.
--
digital man

Sling Blade quote #3:
Karl (re: killing Doyle): That second one just plum near cut his head in two. Norco, CA WX: 70.3øF, 58.0% humidity, 0 mph SW wind, 0.00 inches rain/24hrs
--- SBBSecho 3.14-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: RE: Incorrect Node Number
By: Mike Dippel to Digital Man on Thu Nov 18 2021 03:16 pm

On 11/18/2021 9:25 AM, Digital Man wrote to Mike Dippel:

There are multiple places where the originating node number can be (and often
is) represented in a packet or stored message file. If you use a utility like
pktdump (included with Synchronet, for dumping packets) or fmsgdump (also included with Synchronet, for dumping FTN .msg files), you can see the header
fields and the metadata (i.e. FTN kludge lines, aka control paragraphs) and that could perhaps give us the clue needed to solve your mystery.
--

Could you please provide the executable to use pktdump?

Did you look in your Synchronet exec directory? It should already be there.
--
digital man

Breaking Bad quote #18:
Already, Operation: TBD, thanks for nothing Gomey. - Hank
Norco, CA WX: 70.3øF, 58.0% humidity, 0 mph SW wind, 0.00 inches rain/24hrs
--- SBBSecho 3.14-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Mike Dippel wrote to Digital Man <=-

From the log file on my hub (PXecho.log) a typical response is:

16:43:02 - Orig 954:895/35 Dest 954:895/1
16:43:02 + New Netmail From Mike Dippel (954:895/0)
16:43:02 ! Insecured AREAFIX Request. Node Address : 954:895/0
16:43:02 % AREAFIX Request Activated!
16:43:02 - Using Host Address: 954:895/1
16:43:02 ! AREAFIX SECURITY ERROR!
16:43:02 ! No Account Established
16:43:02 > Creating AreaFix Request Report for 954:895/0

I can see from this that Mike Dippel is assigned 954:895/0 on the Synchronet system. How do I change the node address to /35

I know nothing about Wildcat or Irex, but I think you're mistaken in
your log reading. Look at the very first line there above. It says
"Orig 954:895/35". The second line (which is generated by the hub,
either WC or Irex) says it's from 954:895/0.

So.... Your statement that Mike Dippel is assigned 954:895/0 on the
Synchronet system is incorrect. That assignment is being done on the
receiving system. Something is misconfigured in WC/Irex that says
Mike Dippel's address is /0 instead of /35. That's where you need to
be looking. The Synchronet side is set up correctly.



... So easy, a child could do it. Child sold separately.
--- MultiMail/Linux v0.52
þ Synchronet þ Palantir BBS * palantirbbs.ddns.net * Pensacola, FL
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: RE: Incorrect Node Number
By: Digital Man to Mike Dippel on Thu Nov 18 2021 12:44 pm

I used the command line to execute pktdump. I know it is looking for me to insert a .msg file, but the .msg deletes immediately after it is sent. Nothing is left in the /fido/outbound or outbound.3ba directory to process.

Is there a setting I can change to ensure the packet is not deleted right away? Mike

---
þ Synchronet þ Hobby BBS - Sun City Center, FL
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: RE: Incorrect Node Number
By: Mike Dippel to Digital Man on Thu Nov 18 2021 05:13 pm

Re: RE: Incorrect Node Number
By: Digital Man to Mike Dippel on Thu Nov 18 2021 12:44 pm

I used the command line to execute pktdump. I know it is looking for me to insert a .msg file, but the .msg deletes immediately after it is sent.

pktdump is used to dump packets (e.g. .pkt files), not .msg files.

Nothing is left in the /fido/outbound or outbound.3ba directory to process.

Is there a setting I can change to ensure the packet is not deleted right away? Mike

You could simply not run the mailer. It's the mailer that sends and then deletes the packet after it is sent, not Synchronet or SBBSecho.

Or you could capture the packet on the receiving system and dump it on there. --
digital man

Synchronet "Real Fact" #96:
Synchronet v3.14a was released in December of 2006 (1 year after v3.13a). Norco, CA WX: 59.3øF, 77.0% humidity, 0 mph SSE wind, 0.00 inches rain/24hrs --- SBBSecho 3.14-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

On 11/19/2021 5:49 PM, Digital Man wrote to Mike Dippel:

By: Mike Dippel to Digital Man on Thu Nov 18 2021 05:13 pm

Re: RE: Incorrect Node Number
By: Digital Man to Mike Dippel on Thu Nov 18 2021 12:44 pm

I used the command line to execute pktdump. I know it is looking for me to
insert a .msg file, but the .msg deletes immediately after it is sent.

pktdump is used to dump packets (e.g. .pkt files), not .msg files.

Nothing is left in the /fido/outbound or outbound.3ba directory to process.

Is there a setting I can change to ensure the packet is not deleted right away? Mike

You could simply not run the mailer. It's the mailer that sends and then deletes the packet after it is sent, not Synchronet or SBBSecho.

Or you could capture the packet on the receiving system and dump it on there.
--
digital man

Thanks. I'll give it a try.

Mike
--- Platinum Xpress/Win/WINServer v7.0
* Origin: The Hobby Line! BBS (3:640/1116)