From Newsgroup: alt.bbs.synchronet

Here's output from sbbsecho.log:

2021-01-10 23:49:45 Exported: 1 msgs fidonet_fidotest -> FIDOTEST 2021-01-10 23:49:45 Exported: 1 msgs total
2021-01-10 23:49:45 Sending packet (/sbbs/temp/sbbsecho/5ffbf509.pkt, 0.7KB) from 1:104/116 to 1:15/1
2021-01-10 23:49:45 Routing packet (/sbbs/temp/sbbsecho/5ffbf509.pkt) to 1:15/0 2021-01-10 23:49:45 File (../fido/outbound/5ffbf509.pkt, 0.7KB) for 1:15/0 added to BSO/FLO file: ../fido/outbound/000f0000.clo
2021-01-10 23:49:45 SBBSecho (PID 24040) exiting with error level 0, Packets(0 imported, 1 sent), EchoMail(0 imported, 1 exported)
2021-01-10 23:49:55 Unpacking bundle: /sbbs/fido/inbound/ffa7ff8c.mog (5.1KB) 2021-01-10 23:49:55 Importing /sbbs/fido/inbound/06b34335.pkt (Type 2e, 21.4KB) from 1:15/0 to 1:104/116
2021-01-10 23:49:55 Imported: 1 msgs fidonet_bible <- BIBLE
2021-01-10 23:49:55 Imported: 1 msgs fidonet_fido-req <- FIDO-REQ 2021-01-10 23:49:55 Imported: 2 msgs fidonet_fidotest <- FIDOTEST 2021-01-10 23:49:55 Imported: 2 msgs fidonet_memories <- MEMORIES 2021-01-10 23:49:55 Imported: 1 msgs fidonet_minister <- MINISTER 2021-01-10 23:49:55 Imported: 1 msgs fidonet_taglines <- TAGLINES 2021-01-10 23:49:55 Imported: 7 msgs fidonet_syncprog <- SYNC_PROGRAMMING 2021-01-10 23:49:55 Imported: 15 msgs total
2021-01-10 23:49:55 Sending packet (/sbbs/temp/sbbsecho/5ffbf513.pkt, 12.8KB) from 1:104/116 to 1:15/1
2021-01-10 23:49:55 Routing packet (/sbbs/temp/sbbsecho/5ffbf513.pkt) to 1:15/0 2021-01-10 23:49:55 File (../fido/outbound/5ffbf513.pkt, 12.8KB) for 1:15/0 added to BSO/FLO file: ../fido/outbound/000f0000.clo
2021-01-10 23:49:55 SBBSecho (PID 24053) exiting with error level 0, Bundles(1 unpacked, 0 sent), Packets(1 imported, 1 sent), EchoMail(15 imported, 0 exported)

Message was created in FIDOTEST at 23:49:45... You can see that it was properly exported.

Again, anything helps.

Best regards,
Dream Master

---
þ Synchronet þ Caught in a Dream - Coming Soon!
--- Synchronet 3.18c-Win32 NewsLink 1.113
* Vertrauen - Riverside County, California - telnet://vert.synchro.net
--- Synchronet 3.19c-Linux NewsLink 1.113

From Newsgroup: alt.bbs.synchronet

To: Dream Master
Re: Additional Detail
By: Dream Master to All on Sun Jan 10 2021 11:55 pm

Here's output from sbbsecho.log:

2021-01-10 23:49:45 Exported: 1 msgs fidonet_fidotest -> FIDOTEST 2021-01-10 23:49:45 Exported: 1 msgs total
2021-01-10 23:49:45 Sending packet (/sbbs/temp/sbbsecho/5ffbf509.pkt, 0.7KB) from 1:104/116 to 1:15/1
2021-01-10 23:49:45 Routing packet (/sbbs/temp/sbbsecho/5ffbf509.pkt) to 1:15/0

See that "Routing packet" line? That's a little unusual. Is 1:15/0 your hub? If not, then it appears you have a misplaced route setup. EchoMail is not normally routed, so something weird is afoot

Message was created in FIDOTEST at 23:49:45... You can see that it was properly exported.

Yeah, but I'm guessing you have 1:15/1 configured in SBBSecho to route to 1:15/0. I'm not sure why, but that doesn't seem right.
--
digital man

This Is Spinal Tap quote #3:
How much more black could this be? and the answer is none. None more black. Norco, CA WX: 68.2øF, 20.0% humidity, 2 mph SE wind, 0.00 inches rain/24hrs
--- Synchronet 3.18c-Win32 NewsLink 1.113
* Vertrauen - Riverside County, California - telnet://vert.synchro.net
--- Synchronet 3.19c-Linux NewsLink 1.113

From Newsgroup: alt.bbs.synchronet

To: Dream Master
Re: Additional Detail
By: Digital Man to Dream Master on Mon Jan 11 2021 10:58 am

See that "Routing packet" line? That's a little unusual. Is 1:15/0 your hub? If not, then it appears you have a misplaced route setup. EchoMail is not normally routed, so something weird is afoot
Yeah, but I'm guessing you have 1:15/1 configured in SBBSecho to route to 1:15/0. I'm not sure why, but that doesn't seem right. --

Dr Master,

Also check your /sbbs/data/areas.bbs. The node number next to each echotag should be your hub. If you used init-fido door to setup fido, and then were assigned a different hub and changed it, you have to change areas.bbs manually to your new hub.

Bob Roberts

---
þ Synchronet þ Halls of Valhalla =San=Francisco= hovalbbs.com:2333
--- Synchronet 3.18c-Win32 NewsLink 1.113
* Vertrauen - Riverside County, California - telnet://vert.synchro.net
--- Synchronet 3.19c-Linux NewsLink 1.113

From Newsgroup: alt.bbs.synchronet

To: Digital Man
Re: Additional Detail
By: Digital Man to Dream Master on Mon Jan 11 2021 10:58 am

Yeah, but I'm guessing you have 1:15/1 configured in SBBSecho to route to 1:15/0. I'm not sure why, but that doesn't seem right.

I believe I found the problem and corrected it earlier today.

[domain:fidonet]
Zones = 1,2,3,4,5,6
DNSSuffix = binkp.net
NodeList = /sbbs/fido/_fidonet/NODELIST.008

I noticed that I either left the "NodeList" definition line blank, based upon the history of files in /sbbs/ctrl/sbbsecho.?.*, or that it was removed when I reconfigured SBBSECHO. Who knows? I turned on debugging and caught it in binkstats.ini with a callout failure.

You did turn me on to something and your suggestion made me re-look at the log files and the configuration of BinkIT--thank you!

Dream Master


---
þ Synchronet þ Caught in a Dream - Coming Soon!
--- Synchronet 3.18c-Win32 NewsLink 1.113
* Vertrauen - Riverside County, California - telnet://vert.synchro.net
--- Synchronet 3.19c-Linux NewsLink 1.113

From Newsgroup: alt.bbs.synchronet

To: Bob Roberts
Re: Additional Detail
By: Bob Roberts to Dream Master on Mon Jan 11 2021 03:41 pm

Also check your /sbbs/data/areas.bbs. The node number next to each echotag should be your hub. If you used init-fido door to setup fido, and then were assigned a different hub and changed it, you have to change areas.bbs manually to your new hub.

I caught it off of binkstats.ini (callout failure). I did check areas.bbs to make sure I didn't have anything missing earlier today.

Thank you!

Dream Master

---
þ Synchronet þ Caught in a Dream - Coming Soon!
--- Synchronet 3.18c-Win32 NewsLink 1.113
* Vertrauen - Riverside County, California - telnet://vert.synchro.net
--- Synchronet 3.19c-Linux NewsLink 1.113

From Newsgroup: alt.bbs.synchronet

To: Dream Master
Re: Additional Detail
By: Dream Master to Digital Man on Mon Jan 11 2021 10:01 pm

Re: Additional Detail
By: Digital Man to Dream Master on Mon Jan 11 2021 10:58 am

Yeah, but I'm guessing you have 1:15/1 configured in SBBSecho to route to 1:15/0. I'm not sure why, but that doesn't seem right.

I believe I found the problem and corrected it earlier today.

[domain:fidonet]
Zones = 1,2,3,4,5,6
DNSSuffix = binkp.net
NodeList = /sbbs/fido/_fidonet/NODELIST.008

I noticed that I either left the "NodeList" definition line blank, based upon the history of files in /sbbs/ctrl/sbbsecho.?.*, or that it was removed when I reconfigured SBBSECHO. Who knows? I turned on debugging and caught it in binkstats.ini with a callout failure.

You did turn me on to something and your suggestion made me re-look at the log files and the configuration of BinkIT--thank you!

None of that explains the "Routing" log message. Something else is wrong (too?).
--
digital man

Rush quote #38:
See how it sings like a sad heart, then joyously screams out its pain
Norco, CA WX: 57.5øF, 26.0% humidity, 0 mph SW wind, 0.00 inches rain/24hrs
--- Synchronet 3.18c-Win32 NewsLink 1.113
* Vertrauen - Riverside County, California - telnet://vert.synchro.net
--- Synchronet 3.19c-Linux NewsLink 1.113

From Newsgroup: alt.bbs.synchronet

To: Digital Man
Re: Additional Detail
By: Digital Man to Dream Master on Mon Jan 11 2021 11:52 pm

None of that explains the "Routing" log message. Something else is wrong (too?).

I think you might be right and now I am curious about this:

From sbbsecho.log:

2021-01-12 14:23:45 Unpacking bundle: /sbbs/fido/inbound/ffa7ff8c.tu5 (2.1KB) 2021-01-12 14:23:45 Importing /sbbs/fido/inbound/079c7bbe.pkt (Type 2e, 7.2KB) from 1:15/0 to 1:104/116
2021-01-12 14:23:45 Imported: 2 msgs fidonet_fido-req <- FIDO-REQ 2021-01-12 14:23:45 Imported: 1 msgs fidonet_syncdata <- SYNCDATA 2021-01-12 14:23:45 Imported: 3 msgs total
2021-01-12 14:23:45 Sending packet (/sbbs/temp/sbbsecho/5ffe1361.pkt, 7.3KB) from 1:104/116 to 1:15/1
2021-01-12 14:23:45 Routing packet (/sbbs/temp/sbbsecho/5ffe1361.pkt) to 1:15/0 2021-01-12 14:23:45 File (../fido/outbound/5ffe1361.pkt, 7.3KB) for 1:15/0 added to BSO/FLO file: ../fido/outbound/000f0000.clo
2021-01-12 14:23:45 SBBSecho (PID 5521) exiting with error level 0, Bundles(1 unpacked, 0 sent), Packets(1 imported, 1 sent), EchoMail(3 imported, 0 exported)

From binkstats.ini:

[callout success: 1:15/0@fidonet]
oper = Tj Barlow
AKAs = 1:15/0@fidonet,1:15/1@fidonet,10:6/1@league10,316:719/1@whispnet,719:550/3@cscnet,701:1/4@fishnet
vers = Mystic/1.12A47
host = region15.net
port = 24555
info.sys = Region 15 HQ
info.time = Tue, 12 Jan 2021 21:23:50 0000
info.build = 2020/09/27 13:46:00 Linux/64
info.qsize = 4 files 33,694 bytes
localtime = Jan 12 2021 14:23:52
sent_files = ../fido/outbound/5ffe1361.pkt
received_files = /sbbs/temp/event/ECH00715.tic,/sbbs/temp/event/ech01042.tic,/sbbs/temp/event/ECH00715.ZIP,/sbbs/temp/event/ech01042.zip

Now I feel like I need to find what the hell is wrong here. FidoNet messages are being received without issue while outbound is not. My configuration for SciNet is working fine, though. Weird.

Going to take a look and I'll let you know.

Dream Master

---
þ Synchronet þ Caught in a Dream - Coming Soon!
--- Synchronet 3.18c-Win32 NewsLink 1.113
* Vertrauen - Riverside County, California - telnet://vert.synchro.net
--- Synchronet 3.19c-Linux NewsLink 1.113

From Newsgroup: alt.bbs.synchronet

To: Dream Master
Re: Additional Detail
By: Dream Master to Digital Man on Tue Jan 12 2021 02:28 pm

Re: Additional Detail
By: Digital Man to Dream Master on Mon Jan 11 2021 11:52 pm

None of that explains the "Routing" log message. Something else is wrong (too?).

I think you might be right and now I am curious about this:

From sbbsecho.log:

2021-01-12 14:23:45 Unpacking bundle: /sbbs/fido/inbound/ffa7ff8c.tu5 (2.1KB) 2021-01-12 14:23:45 Importing /sbbs/fido/inbound/079c7bbe.pkt (Type 2e, 7.2KB) from 1:15/0 to 1:104/116
2021-01-12 14:23:45 Imported: 2 msgs fidonet_fido-req <- FIDO-REQ 2021-01-12 14:23:45 Imported: 1 msgs fidonet_syncdata <- SYNCDATA 2021-01-12 14:23:45 Imported: 3 msgs total
2021-01-12 14:23:45 Sending packet (/sbbs/temp/sbbsecho/5ffe1361.pkt, 7.3KB) from 1:104/116 to 1:15/1
2021-01-12 14:23:45 Routing packet (/sbbs/temp/sbbsecho/5ffe1361.pkt) to 1:15/0 2021-01-12 14:23:45 File (../fido/outbound/5ffe1361.pkt, 7.3KB) for 1:15/0 added to BSO/FLO file: ../fido/outbound/000f0000.clo
2021-01-12 14:23:45 SBBSecho (PID 5521) exiting with error level 0, Bundles(1 unpacked, 0 sent), Packets(1 imported, 1 sent), EchoMail(3 imported, 0 exported)

From binkstats.ini:

[callout success: 1:15/0@fidonet]
oper = Tj Barlow
AKAs = 1:15/0@fidonet,1:15/1@fidonet,10:6/1@league10,316:719/1@whispnet ,719:550/3@cscnet,701:1/4@fishnet
vers = Mystic/1.12A47
host = region15.net
port = 24555
info.sys = Region 15 HQ
info.time = Tue, 12 Jan 2021 21:23:50 0000
info.build = 2020/09/27 13:46:00 Linux/64
info.qsize = 4 files 33,694 bytes
localtime = Jan 12 2021 14:23:52
sent_files = ../fido/outbound/5ffe1361.pkt
received_files = /sbbs/temp/event/ECH00715.tic,/sbbs/temp/event/ech0104 2.tic,/sbbs/temp/event/ECH00715.ZIP,/sbbs/temp/event/ech01042.zip

Now I feel like I need to find what the hell is wrong here. FidoNet messages are being received without issue while outbound is not. My configuration for SciNet is working fine, though. Weird.

Going to take a look and I'll let you know.

From the sbbsecho.log output it appears you have 1:15/1 configured as your uplink (e.g. listed for FidoNet echoes in your area file), yet you also have 1:15/1 configured to route to 1:15/0 in your sbbsecho.ini file. This is not a logical configuration. Your uplink should be a direct connection and need no routing.
--
digital man

Rush quote #36:
Raging at unreachable glory, straining at invisible chains
Norco, CA WX: 65.2øF, 25.0% humidity, 5 mph ESE wind, 0.00 inches rain/24hrs --- Synchronet 3.18c-Win32 NewsLink 1.113
* Vertrauen - Riverside County, California - telnet://vert.synchro.net
--- Synchronet 3.19c-Linux NewsLink 1.113