Hi,

I am having a strange issue in Fidonet.

I am sending my echomail to a one 2.250/1 from my point: 2:250/1.2 which is sent correctly:

----
17-06-2018 16:04:13 Exporting fido-uk_fidotest message #65 from Rmh to Vince Coen in area: FIDOTEST
17-06-2018 16:04:13 Creating outbound packet from 2:250/1.2 to 2:250/1: /home/bbs/sbbs/temp/sbbsecho/5b26867d.pkt
17-06-2018 16:04:13 Adding FIDOTEST message from Rmh (2:250/1.2) to packet for 2:250/1: /home/bbs/sbbs/temp/sbbsecho/5b26867d.pkt
17-06-2018 16:04:13 Exported: 1 msgs fido-uk_fidotest -> FIDOTEST 17-06-2018 16:04:13 Exported: 1 msgs total
17-06-2018 16:04:13 Finalizing outbound packet from 2:250/1.2 to 2:250/1: /home/bbs/sbbs/temp/sbbsecho/5b26867d.pkt
17-06-2018 16:04:13 Node (2:250/1) successfully locked via: ../fido/outbound/00fa0001.bsy
17-06-2018 16:04:13 Sending packet (/home/bbs/sbbs/temp/sbbsecho/5b26867d.pkt, 0.5KB) from 2:250/1.2 to 2:250/1
17-06-2018 16:04:13 Routing packet (/home/bbs/sbbs/temp/sbbsecho/5b26867d.pkt) to 2:250/1
17-06-2018 16:04:13 Moving packet for 2:250/1: /home/bbs/sbbs/temp/sbbsecho/5b26867d.pkt to ../fido/outbound/5b26867d.pkt 17-06-2018 16:04:13 File (../fido/outbound/5b26867d.pkt, 0.5KB) for 2:250/1 added to BSO/FLO file: ../fido/outbound/00fa0001.flo
17-06-2018 16:04:13 Touching outgoing semfile: ../data/binkout.now
17-06-2018 16:04:13 Writing 1 areas to ../data/badareas.lst


---

But the Hub gets a completely different address: "2:65535/1.2"

---
16-Jun-2018 21:01:48 mbfido[30473] MBFIDO v1.0.7.6
16-Jun-2018 21:01:48 mbfido[30473] Cmd: mbfido tic toss web -quiet
+ 16-Jun-2018 21:01:48 mbfido[30473] Pass: hatch files
+ 16-Jun-2018 21:01:48 mbfido[30473] Pass: process ticfiles (/home/mbse/var/inbound)
+ 16-Jun-2018 21:01:48 mbfido[30473] Pass: toss netmail (/home/mbse/var/inbound)
+ 16-Jun-2018 21:01:48 mbfido[30473] Packet : 5b256ca0.pkt type 2+
+ 16-Jun-2018 21:01:48 mbfido[30473] From : 2:65535/1.2 to 2:250/1
+ 16-Jun-2018 21:01:48 mbfido[30473] Dated : 16-06-2018 20:01:36
+ 16-Jun-2018 21:01:48 mbfido[30473] Program : SBBSecho 3.5
+ 16-Jun-2018 21:01:48 mbfido[30473] Node 2:65535/1.2 not connected to area FIDOTEST
+ 16-Jun-2018 21:01:48 mbfido[30473] Tossing in bad board
+ 16-Jun-2018 21:01:48 mbfido[30473] Messages : 1
---

I cannot find anywhere that AKA configuredin my system so: "2:65535/1.2".

Not making much sense to me right now .
I have double checked the configurations for the Areas and all of them g

Re: Strange Issue Fidonet SBBSecho
By: Rmh to All on Sun Jun 17 2018 09:38 pm

Hi,

I am having a strange issue in Fidonet.

I am sending my echomail to a one 2.250/1 from my point: 2:250/1.2 which is sent correctly:

----
17-06-2018 16:04:13 Exporting fido-uk_fidotest message #65 from Rmh to Vince Coen in area: FIDOTEST
17-06-2018 16:04:13 Creating outbound packet from 2:250/1.2 to 2:250/1: /home/bbs/sbbs/temp/sbbsecho/5b26867d.pkt
17-06-2018 16:04:13 Adding FIDOTEST message from Rmh (2:250/1.2) to packet for 2:250/1: /home/bbs/sbbs/temp/sbbsecho/5b26867d.pkt
17-06-2018 16:04:13 Exported: 1 msgs fido-uk_fidotest -> FIDOTEST 17-06-2018 16:04:13 Exported: 1 msgs total
17-06-2018 16:04:13 Finalizing outbound packet from 2:250/1.2 to 2:250/1: /home/bbs/sbbs/temp/sbbsecho/5b26867d.pkt
17-06-2018 16:04:13 Node (2:250/1) successfully locked via: ../fido/outbound/00fa0001.bsy
17-06-2018 16:04:13 Sending packet (/home/bbs/sbbs/temp/sbbsecho/5b26867d.pkt, 0.5KB) from 2:250/1.2 to 2:250/1 17-06-2018 16:04:13 Routing packet (/home/bbs/sbbs/temp/sbbsecho/5b26867d.pkt) to 2:250/1
17-06-2018 16:04:13 Moving packet for 2:250/1: /home/bbs/sbbs/temp/sbbsecho/5b26867d.pkt to ../fido/outbound/5b26867d.pkt 17-06-2018 16:04:13 File (../fido/outbound/5b26867d.pkt, 0.5KB) for 2:250/1 added to BSO/FLO file: ../fido/outbound/00fa0001.flo
17-06-2018 16:04:13 Touching outgoing semfile: ../data/binkout.now 17-06-2018 16:04:13 Writing 1 areas to ../data/badareas.lst

---

But the Hub gets a completely different address: "2:65535/1.2"

Looks like the software your hub is using doesn't support type Type-2+ packet format defined in FSC-39. For details, see here: http://wiki.synchro.net/ref:fidonet_packets

A work-around would be to configure your hub in EchoCfg->Linked Nodes to use packet type "2e" instead.

digital man

This Is Spinal Tap quote #30:
Big bottom, big bottom / Talk about mud flaps, my girl's got 'em!
Norco, CA WX: 67.8oF, 57.0% humidity, 10 mph ENE wind, 0.00 inches rain/24hrs --- SBBSecho 3.05-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Strange Issue Fidonet SBBSecho
By: Digital Man to Rmh on Sun Jun 17 2018 05:33 pm

Looks like the software your hub is using doesn't support type Type-2+ packet format defined in FSC-39. For details, see here: http://wiki.synchro.net/ref:fidonet_packets

A work-around would be to configure your hub in EchoCfg->Linked Nodes to use packet type "2e" instead.

Thanks Digital Man.

That was exactly the reason for the issue and it's now working without problems.

Thanks again.

RainManHood<---

---
* Synchronet * UNICYBER BBS -- bbs.unicyber.co.uk:2323::ssh bbs.unicyber.co.uk 2424
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

On 2018 Jun 17 17:33:18, you wrote to Rmh:

A work-around would be to configure your hub in EchoCfg->Linked Nodes
to use packet type "2e" instead.

2e?? is that 2.2 as described in FSC-00045? or is it maybe the first 2+ as described in FSC-0039 without the FSC-0048 additions?

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... Northerners don't plan vacations around a gun-n-knife show.
---
* Origin: (1:3634/12.73)

Re: Strange Issue Fidonet SBBSecho
By: mark lewis to Digital Man on Mon Jun 18 2018 11:03 am

On 2018 Jun 17 17:33:18, you wrote to Rmh:

A work-around would be to configure your hub in EchoCfg->Linked Nodes to use packet type "2e" instead.

2e?? is that 2.2 as described in FSC-00045? or is it maybe the first 2+ as described in FSC-0039 without the FSC-0048 additions?

What I call "2e" is the packet fomrat defined in FSC-39 (there's no mention of "2+" in that document). I detailed this here: http://wiki.synchro.net/ref:fidonet_packets

digital man

Synchronet/BBS Terminology Definition #37:
NNTP = Network News Transfer Protocol
Norco, CA WX: 63.9oF, 72.0% humidity, 5 mph ESE wind, 0.00 inches rain/24hrs --- SBBSecho 3.05-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

On 2018 Jun 18 21:12:40, you wrote to me:

A work-around would be to configure your hub in EchoCfg->Linked
Nodes to use packet type "2e" instead.

2e?? is that 2.2 as described in FSC-00045? or is it maybe the first 2+
as described in FSC-0039 without the FSC-0048 additions?

What I call "2e" is the packet fomrat defined in FSC-39 (there's no mention of "2+" in that document).

yeah, i forget where the "+" came from but it has been around ""forever""... i haven't read the documents in a while... i generally refer to my ancient and pretty simple READPKT tool which was written as a PKT diagnostic tool...

I detailed this here: http://wiki.synchro.net/ref:fidonet_packets

looks good, man!

FWIW: since FSC-0048 builds on FSC-0039, perhaps it would be a good idea to alter this line a little bit??

2. Type-2+ (A Proposed Type-2 Packet Extension, defined in FSC-48)

maybe something like this?

2. Type-2+ (A Proposed Type-2 Packet Extension of FSC-0039, defined in FSC-48)

i suggest this because FSC-0048 won't/can't stand on its own... it has to start
with FSC-0039...


FWIW2: it might also be a good idea to reference FTSC document numbers with all
their leading zeros, too... i'm undecided about it but do generally write all the leading zeros... not that it makes any real difference other than consistency across the board...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... I read your post. It's plodding, pedantic. Much like yourself.
---
* Origin: (1:3634/12.73)

Re: Strange Issue Fidonet SBBSecho
By: mark lewis to Digital Man on Tue Jun 19 2018 08:21 am

On 2018 Jun 18 21:12:40, you wrote to me:

A work-around would be to configure your hub in EchoCfg->Linked
Nodes to use packet type "2e" instead.

2e?? is that 2.2 as described in FSC-00045? or is it maybe the first 2+
as described in FSC-0039 without the FSC-0048 additions?

What I call "2e" is the packet fomrat defined in FSC-39 (there's no mention of "2+" in that document).

yeah, i forget where the "+" came from but it has been around ""forever""...

It came from FSC-48.

i haven't read the documents in a while... i generally refer to my ancient and pretty simple READPKT tool which was written as a PKT diagnostic tool...

I detailed this here: http://wiki.synchro.net/ref:fidonet_packets

looks good, man!

FWIW: since FSC-0048 builds on FSC-0039, perhaps it would be a good idea to alter this line a little bit??

2. Type-2+ (A Proposed Type-2 Packet Extension, defined in FSC-48)

maybe something like this?

2. Type-2+ (A Proposed Type-2 Packet Extension of FSC-0039, defined in FSC-48)

i suggest this because FSC-0048 won't/can't stand on its own... it has to start
with FSC-0039...

How's that? I could write a 2+ packet generator/parser using nothing but http://ftsc.org/docs/fsc-0048.002 (plus FTS-1 for Packed Message header parsing). You don't need FSC-39. It seems to be everything useful in FSC-39 is restated (better) in FSC-48.

FWIW2: it might also be a good idea to reference FTSC document numbers with all
their leading zeros, too...

I generally do so when I first refer to a document (e.g. FTS-0001.016) in another document and then later shorten that to just FTS-1.

i'm undecided about it but do generally write
all the leading zeros... not that it makes any real difference other than consistency across the board...

I think always including the leading zeroes is dumb. <shrug>

digital man

Synchronet/BBS Terminology Definition #42:
R0DENT = Derogatory reference to a young BBS user of the 1990's
Norco, CA WX: 72.7oF, 57.0% humidity, 0 mph S wind, 0.00 inches rain/24hrs
--- SBBSecho 3.05-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)