I'm having problems with SBBSECHO tossing messages.

In looking at the old HTML docs, it said that the AREAS.BBS file has
to be set up with the internal code, the echo tag, and the hub where it
is going. Yet, when I look at the file, I've got it set that way...but
the logs show the area as unrecognized, and is treating it as a passthru
echo. I've also put AREAS.BBS in the C:\SBBS\DATA directory.

It apparently is processing outbound echoes, but sending them to one
main directory, so I have no way to tell which packet was prepared for
which node, as it was when I ran InterEcho as a tosser.

Any assistance would be appreciated.

On another note, I got the autopost deal working with SMBUTIL, but I
have to create a "starting message" in the area for it to work.

Daryl

---
þ OLX 1.53 þ Out of my mind. Be back in five minutes.
þ Synchronet þ The Thunderbolt BBS - Little Rock, AR - wx1der.dyndns.org

Re: SBBSECHO ISSUES
By: Daryl Stout to ALL on Wed May 18 2016 07:17 pm

I'm having problems with SBBSECHO tossing messages.

In looking at the old HTML docs, it said that the AREAS.BBS file has
to be set up with the internal code, the echo tag, and the hub where it
is going. Yet, when I look at the file, I've got it set that way...but
the logs show the area as unrecognized, and is treating it as a passthru echo. I've also put AREAS.BBS in the C:\SBBS\DATA directory.

Double-check your internal codes. If you have an internal-code prefix set in SCFG->Message Areas->FidoNet, then you'll have to include that prefix in the areas.bbs file too.

It apparently is processing outbound echoes, but sending them to one
main directory, so I have no way to tell which packet was prepared for
which node, as it was when I ran InterEcho as a tosser.

You can use a packet viewer utility (like my pktdump.exe) to determine where the packets are destined. Or are you talking about bundles? In any case, assuming you're using a BSO/FLO style mailer, the FLO files will point to the bundles or packets and the FLO files are unique for each link. Once you figure out which FLO file is for which link, you'll then see which bundles or packets are pending for that link. The "key" to the filenaming is here: http://wiki.synchro.net/ref:fidonet_files

On another note, I got the autopost deal working with SMBUTIL, but I
have to create a "starting message" in the area for it to work.

Including the '-c' (create) option would resolve that.

digital man

Synchronet/BBS Terminology Definition #16:
DTE = Data Terminal Equipment
Norco, CA WX: 66.1øF, 71.0% humidity, 2 mph SE wind, 0.00 inches rain/24hrs

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ telnet://vert.synchro.net

Rob,

Double-check your internal codes. If you have an internal-code prefix set in DM>SCFG->Message Areas->FidoNet, then you'll have to include that prefix in the DM>areas.bbs file too.

OK, I'll have to recheck that. When I looked at them last night, I was
using the internal code first, the area tag second, and the destination
third, in the AREAS.BBS file.

You can use a packet viewer utility (like my pktdump.exe) to determine where DM>the packets are destined. Or are you talking about bundles? In any case, DM>assuming you're using a BSO/FLO style mailer, the FLO files will point to th DM>bundles or packets and the FLO files are unique for each link. Once you figu DM>out which FLO file is for which link, you'll then see which bundles or packe DM>are pending for that link. The "key" to the filenaming is here: DM>http://wiki.synchro.net/ref:fidonet_files

I'll look at that one later.

On another note, I got the autopost deal working with SMBUTIL, but I have to create a "starting message" in the area for it to work.

Including the '-c' (create) option would resolve that.

Got that noted.

Daryl

---
þ OLX 1.53 þ News Headline: Man shoots neighbor with machete.
þ Synchronet þ The Thunderbolt BBS - Little Rock, AR - wx1der.dyndns.org

19 May 16 08:57, you wrote to DIGITAL MAN:

Double-check your internal codes. If you have an internal-code prefix
set in SCFG->Message Areas->FidoNet, then you'll have to include that
prefix in the areas.bbs file too.

OK, I'll have to recheck that. When I looked at them last night, I was using the internal code first, the area tag second, and the
destination third, in the AREAS.BBS file.

eg:
ICP-AREACODE ECHOTAG ADDRESSESGOHERE ======================================================================== FIDO-SYNCDATA SYNCDATA 1:3634/12 FIDO-SYNCHRON SYNCHRONET 1:3634/12 FIDO-SYNCSYSO SYNC_SYSOPS 1:3634/12

in the above FIDO- is the internal-code prefix followed by the local code we've
given for the area to be stored in... the two are combined to form the actual filenames for the message areas... you can see them in sbbs/data/subs...

not sure how the areas.bbs file looks when areas are connected to more than one
system... the above snippet comes from the AREAS.BBS for 1:3634/50...

)\/(ark

Always Mount a Scratch Monkey

... Living near a forest doesn't make you a lumberjack.
---
* Origin: (1:3634/12.73)
þ Synchronet þ Vertrauen þ Home of Synchronet þ telnet://vert.synchro.net

Re: SBBSECHO ISSUES
By: Daryl Stout to DIGITAL MAN on Thu May 19 2016 08:57 am

Rob,

Double-check your internal codes. If you have an internal-code prefix set in DM>SCFG->Message Areas->FidoNet, then you'll have to include that prefix in the DM>areas.bbs file too.

OK, I'll have to recheck that. When I looked at them last night, I was using the internal code first, the area tag second, and the destination third, in the AREAS.BBS file.

That's the correct order, but the internal codes must be the *complete* internal code (including the prefix, if you have one specified in SCFG).

digital man

Synchronet/BBS Terminology Definition #14:
DOVE = Domain/Vertrauen
Norco, CA WX: 75.3øF, 57.0% humidity, 12 mph ESE wind, 0.00 inches rain/24hrs

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ telnet://vert.synchro.net

Re: SBBSECHO ISSUES
By: Digital Man to Daryl Stout on Wed May 18 2016 08:15 pm

You can use a packet viewer utility (like my pktdump.exe) to determine where the packets are destined. Or are you talking about bundles? In any case, assuming you're using a BSO/FLO style mailer, the FLO files will point to the bundles or packets and the FLO files are unique for each link. Once you figure out which FLO file is for which link, you'll then see which bundles or packets are pending for that link. The "key" to the filenaming is here: http://wiki.synchro.net/ref:fidonet_files

Rob,

I downloaded PKTDUMP.EXE, but I am confused with the command line structure. Is there a utility to determine what the destination is, by inputting the hexadecimal string as the header??

I understand the suffix as the first 2 letters of the day of the week, with a number from 0 through 9. But, I don't understand how to determine the prefix, and basically the destination.

Math was never my forte'. I can write a batchfile for the BBS, but my programming ENDS at setting the clock on the microwave oven. I guess if I forget to do that, I'll starve to death. I looked at the Synchronet Wiki on FIDONet file names, but that didn't really help me. It may be a simple process, but I'm confused.

Daryl

---
þ Synchronet þ The Thunderbolt BBS - Little Rock, AR - wx1der.dyndns.org

Re: SBBSECHO ISSUES
By: Daryl Stout to Digital Man on Thu May 26 2016 12:32 pm

Re: SBBSECHO ISSUES
By: Digital Man to Daryl Stout on Wed May 18 2016 08:15 pm

You can use a packet viewer utility (like my pktdump.exe) to determine where the packets are destined. Or are you talking about bundles? In any case, assuming you're using a BSO/FLO style mailer, the FLO files will point to the bundles or packets and the FLO files are unique for each link. Once you figure out which FLO file is for which link, you'll then see which bundles or packets are pending for that link. The "key" to the filenaming is here: http://wiki.synchro.net/ref:fidonet_files

Rob,

I downloaded PKTDUMP.EXE, but I am confused with the command line structure.

You type "pktdump" followed by a space and then the filenames of the packet you wish to view. (e.g. "pktdump *.pkt").

Is there a utility to determine what the destination is, by
inputting the hexadecimal string as the header??

Which hexadecimal string are you referring to? SBBSecho v3 uses the current time_t value (in hexadecimal) for the packet base filename (e.g. 574779f3.pkt). Or are you referring to bundle filenames (not packets)?

I understand the suffix as the first 2 letters of the day of the week, with a number from 0 through 9. But, I don't understand how to determine the prefix, and basically the destination.

You're talking about bundles, not packets. Here is a key to bundle filenaming: http://wiki.synchro.net/ref:fidonet_files#bundle

Math was never my forte'. I can write a batchfile for the BBS, but my programming ENDS at setting the clock on the microwave oven. I guess if I forget to do that, I'll starve to death. I looked at the Synchronet Wiki on FIDONet file names, but that didn't really help me. It may be a simple process, but I'm confused.

It's not simple. It requires math and probably a calculator that can perform calculations on hexadecimal numbers. Even Windows calc.exe can do this in "Programmer" mode.

The more simple values to decode are the FLO file names. Also in hex, but they require no math.

digital man

Synchronet "Real Fact" #32:
The second most prolific contributor to Synchronet is Stephen Hurd (Deuce). Norco, CA WX: 71.4øF, 55.0% humidity, 16 mph ESE wind, 0.00 inches rain/24hrs

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ telnet://vert.synchro.net

26 May 16 12:32, you wrote to Digital Man:

I downloaded PKTDUMP.EXE, but I am confused with the command line structure. Is there a utility to determine what the destination is, by inputting the hexadecimal string as the header??

pktdump should only be run on pkts with the .pkt extension... NOT .mo2 or .we1 or such... those are bundles... generally they are zipped...

)\/(ark

Always Mount a Scratch Monkey

... Mind... Mind... Let's see, I had one of those around here someplace.
---
* Origin: (1:3634/12.73)
þ Synchronet þ Vertrauen þ Home of Synchronet þ telnet://vert.synchro.net

Rob,

I downloaded PKTDUMP.EXE, but I am confused with the command line structure.

You type "pktdump" followed by a space and then the filenames of the packet DM>wish to view. (e.g. "pktdump *.pkt").

OK, the command line said something like PKTDUMP [-body] file.pkt --
the "body" was where i was confused.

Or are you referring to bundle filenames (not packets)?

Bundle filenames.

You're talking about bundles, not packets. Here is a key to bundle filenamin DM>http://wiki.synchro.net/ref:fidonet_files#bundle

I looked there, but was still confused.

It's not simple. It requires math and probably a calculator that can perform DM>calculations on hexadecimal numbers. Even Windows calc.exe can do this in DM>"Programmer" mode.

I tried that, but was even more confused.

While the SBBSECHO log tells of what packet was created, it doesn't
tell what packet is going to which node that I set up in ECHOCFG. If I
had that info, that'd make it whole lot easier. I've got a bunch of
outbound packets waiting to go, but I don't want them going to the wrong
node.

I did use the PKTDUMP, and was able to figure out where the waiting
bags should go.

Daryl

---
þ OLX 1.53 þ Don't drink and park -- accidents cause people.
þ Synchronet þ The Thunderbolt BBS - Little Rock, AR - wx1der.dyndns.org

Re: SBBSECHO ISSUES
By: Daryl Stout to DIGITAL MAN on Fri May 27 2016 02:09 pm

Rob,

I downloaded PKTDUMP.EXE, but I am confused with the command line structure.

You type "pktdump" followed by a space and then the filenames of the packet DM>wish to view. (e.g. "pktdump *.pkt").

OK, the command line said something like PKTDUMP [-body] file.pkt --
the "body" was where i was confused.

If you want to see the body text, use the -body option. If you don't, the don't.

Or are you referring to bundle filenames (not packets)?

Bundle filenames.

You can't pktdump.exe on bundles.

You're talking about bundles, not packets. Here is a key to bundle filenamin DM>http://wiki.synchro.net/ref:fidonet_files#bundle

I looked there, but was still confused.

It's not simple. It requires math and probably a calculator that can perform DM>calculations on hexadecimal numbers. Even Windows calc.exe can do this in DM>"Programmer" mode.

I tried that, but was even more confused.

About what? Can you be more specific?

While the SBBSECHO log tells of what packet was created, it doesn't
tell what packet is going to which node that I set up in ECHOCFG.

It does for me:

2016-05-27 14:44:29 Adding FIDONEWS message from Lee Lofaso (2:280/464) to packet for 1:218/700: s:\sbbs\temp\sbbsecho\5748bfbd.pkt

What version of SBBSecho are you running?

If I
had that info, that'd make it whole lot easier. I've got a bunch of
outbound packets waiting to go, but I don't want them going to the wrong node.

What makes you think they'll go to the wrong node?

I did use the PKTDUMP, and was able to figure out where the waiting
bags should go.

Bags?

digital man

Synchronet "Real Fact" #84:
The Electronic Frontier Foundation used to run Synchronet (circa 1993).
Norco, CA WX: 73.1øF, 54.0% humidity, 20 mph SSE wind, 0.00 inches rain/24hrs

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ telnet://vert.synchro.net

Rob,

OK, the command line said something like PKTDUMP [-body] file.pkt -- the "body" was where i was confused.

If you want to see the body text, use the -body option. If you don't, the DM>don't.

OK, that explains it. I thought you had to have something in the
[-body] string.

You can't pktdump.exe on bundles.

Yeah, I was able to unzip them, and then do pktdump on it.

It's not simple. It requires math and probably a calculator that can perform DM>calculations on hexadecimal numbers. Even Windows calc.exe can this in DM>"Programmer" mode.

I tried that, but was even more confused.

About what? Can you be more specific?

Windows Calculator in programming mode.

While the SBBSECHO log tells of what packet was created, it doesn't tell what packet is going to which node that I set up in ECHOCFG.

It does for me:

2016-05-27 14:44:29 Adding FIDONEWS message from Lee Lofaso (2:280/464) to DM>packet for 1:218/700: s:\sbbs\temp\sbbsecho\5748bfbd.pkt

What version of SBBSecho are you running?

That one that was bundled with SBBS 3.16 -- as I did a fresh install.

What makes you think they'll go to the wrong node?

SBBSECHO was putting everything in one common outbound. I use Internet
Rex with its BinkP option instead of the BinkD program.

I did use the PKTDUMP, and was able to figure out where the waiting bags should go.

Bags?

Should have said packets or bundles. When I ran GT Power, we used
"mailbags" in the terminology.

Daryl
---
þ OLX 1.53 þ Flood: A river that's too big for its bridges.
þ Synchronet þ The Thunderbolt BBS - Little Rock, AR - wx1der.dyndns.org

Daryl, where did you find PKTDUMP?

Thanks

--- Virtual Advanced Ver 2 for DOS
* Origin: *Square One BBS (1:3634/22)
þ Synchronet þ Vertrauen þ Home of Synchronet þ telnet://vert.synchro.net

Re: SBBSECHO ISSUES
By: Bill Gordon to Daryl Stout on Sat May 28 2016 07:24 am

Daryl, where did you find PKTDUMP?

ftp://vert.synchro.net/main/bbs/pktdump.exe

digital man

Synchronet "Real Fact" #21:
The first commericial sale of Synchronet was to Las Vegas Playground BBS (1992).
Norco, CA WX: 70.0øF, 66.0% humidity, 0 mph ESE wind, 0.00 inches rain/24hrs

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ telnet://vert.synchro.net

Re: SBBSECHO ISSUES
By: Daryl Stout to DIGITAL MAN on Fri May 27 2016 08:18 pm

Rob,

OK, the command line said something like PKTDUMP [-body] file.pkt -- the "body" was where i was confused.

If you want to see the body text, use the -body option. If you don't, the DM>don't.

OK, that explains it. I thought you had to have something in the
[-body] string.

You can't pktdump.exe on bundles.

Yeah, I was able to unzip them, and then do pktdump on it.

It's not simple. It requires math and probably a calculator that can perform DM>calculations on hexadecimal numbers. Even Windows calc.exe can this in DM>"Programmer" mode.

I tried that, but was even more confused.

About what? Can you be more specific?

Windows Calculator in programming mode.

While the SBBSECHO log tells of what packet was created, it doesn't tell what packet is going to which node that I set up in ECHOCFG.

It does for me:

2016-05-27 14:44:29 Adding FIDONEWS message from Lee Lofaso (2:280/464) to DM>packet for 1:218/700: s:\sbbs\temp\sbbsecho\5748bfbd.pkt

What version of SBBSecho are you running?

That one that was bundled with SBBS 3.16 -- as I did a fresh install.

You should upgrade to v2.33:
ftp://vert.synchro.net/Synchronet/sbe_233.zip

It has some fixes but also includes much more verbose logging.

What makes you think they'll go to the wrong node?

SBBSECHO was putting everything in one common outbound.

It's normal for everything for the same zone to go into the same outbound directory (points are an exception).

I use Internet
Rex with its BinkP option instead of the BinkD program.

And it should support the normal binkley-style-outbound where all bundles and FLOW files for a common zone go into a common outbound directory.

digital man

Synchronet/BBS Terminology Definition #32:
NUP = New User Password
Norco, CA WX: 70.5øF, 63.0% humidity, 4 mph ESE wind, 0.00 inches rain/24hrs

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ telnet://vert.synchro.net

Re: SBBSECHO ISSUES
By: Bill Gordon to Daryl Stout on Sat May 28 2016 07:24:34

Daryl, where did you find PKTDUMP?

Yeah, I couldnt find it either.
--- SBBSecho 3.00-Win32
* Origin: The Lions Den BBS, Trenton, On, CDN (1:249/303)
þ Synchronet þ Vertrauen þ Home of Synchronet þ telnet://vert.synchro.net

Rob,

You should upgrade to v2.33: DM>ftp://vert.synchro.net/Synchronet/sbe_233.zip

It has some fixes but also includes much more verbose logging.

Good deal. Just downloaded it, and will install it.

It's normal for everything for the same zone to go into the same outbound DM>directory (points are an exception).

I have no problem with the same zone, but I have more than one network (zone).

And it should support the normal binkley-style-outbound where all bundles an DM>FLOW files for a common zone go into a common outbound directory.

It does. In using PKTDUMP, I've been able to determine what goes
where, outbound wise.

Daryl

---
þ OLX 1.53 þ An Electrician gets into people's shorts!
þ Synchronet þ The Thunderbolt BBS - Little Rock, AR - wx1der.dyndns.org