Hello Kim,

I am seeing odd seen by lines in zone 21. All of the nodes are (I believe) regional independant nodes in region 1, 2, 3 and 4. In the seen by lines I see 0/??? node numbers (I'll post an example below that I cut and pasted from the web interface).

I am unsure if this is a problem in my config and/or if others see it also. Comments from anyone welcome. :)

I'll import a cut and paste below..

---- import begin ----

Message #4569, fsx_gen (Chat, Testing + More..) From:
nristen
To:
Avon
Subject:
Re: Galactic Dynasty
Date:
30th March, 2019 at 13:05
Replies:
Original

@SEEN-BY: 1/1 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 @SEEN-BY: 0/116 117 118 119 120 121 122 123 124 125 127 128 129 130 131 133 134 @SEEN-BY: 0/135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 @SEEN-BY: 0/152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 @SEEN-BY: 0/169 171 172 173 174 175 176 177 178 179 181 182 183 184 185 186 187 @SEEN-BY: 0/188 189 190 191 192 193 195 197 199 200 999 2/100 3/100 101 102 103 @SEEN-BY: 0/104 4/10 100 101 102 104 105 106 107 108 109 110 112 113 114 116 @SEEN-BY: 4/117
@PATH: 1/161 100 3/100 4/100 106
@TID: Mystic BBS 1.12 A42
@MSGID: 21:1/161 2ea3e523
@REPLY: 21:1/101 5356aee7
@TZUTC: -0400
@MSGID: 21:4/100 2ea3e523

Currently, when I try to enter the game from the BBS, I get the follo error,

"Sorry, the game is currently in use. Please try again later."

Yep I had that also, look for inuse.flg in the dir, and remove it, then try, all should be good :)

Ah, thank you.

Nristen
aka karl harris
keybase.io/nristen

-+- Mystic BBS v1.12 A42 2018/12/27 (Raspberry Pi/32)
+ Origin: searchbbs.fsxnet.nz:34123 / SSH 2222 (21:1/161)

---- import end ----

I've been seeing this for some time. This is a post from fsxNet. The net seems to be working fine, I'm getting and sending mail just fine and there are no problems in the net that I have noticed.

I only noticed this when a node asked me for a feed for fsxNet and I saw these path and seen by lines in outgoing packets.

--- BBBS/Li6 v4.10 Toy-4
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

On 30 Mar 2019 at 01:59p, Alan Ianson pondered and said...

believe) regional independant nodes in region 1, 2, 3 and 4. In the seen by lines I see 0/??? node numbers (I'll post an example below that I cut

Hi Al.

For the post you quoted I took at look at how things were looking as it
passed via 21:3/100 and 21:4/100 HUBs. From my perspective it all looks fine. I'll quote each post so you can see how it was prior to be sent to your NET 4 fsxNet address.

At 21:3/100

[snip]

From: nristen
To: Avon
Subj: Re: Galactic Dynasty
Date: 03/30/19 13:05
Base: FSX_GEN

@TID: Mystic BBS 1.12 A42
@MSGID: 21:1/161 2ea3e523
@REPLY: 21:1/101 5356aee7
@TZUTC: -0400
@SEEN-BY: 1/1 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 @SEEN-BY: 116 117 118 119 120 121 122 123 124 125 127 128 129 130 131 133 134 @SEEN-BY: 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 @SEEN-BY: 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 @SEEN-BY: 169 171 172 173 174 175 176 177 178 179 181 182 183 184 185 186 187 @SEEN-BY: 188 189 190 191 192 193 195 197 199 200 999 2/100 3/100 4/100
@PATH: 1/161 100

Currently, when I try to enter the game from the BBS, I get the

follo

error,

"Sorry, the game is currently in use. Please try again later."

Yep I had that also, look for inuse.flg in the dir, and remove it, then try, all should be good :)

Ah, thank you.

Nristen
aka karl harris
keybase.io/nristen

--- Mystic BBS v1.12 A42 2018/12/27 (Raspberry Pi/32)
* Origin: searchbbs.fsxnet.nz:34123 / SSH 2222 (21:1/161)

[snip]

and at 21:4/100 it looked like this

[snip]

From: nristen
To: Avon
Subj: Re: Galactic Dynasty
Date: 03/30/19 13:05
Base: Chat, Testing + More...

@TID: Mystic BBS 1.12 A42
@MSGID: 21:1/161 2ea3e523
@REPLY: 21:1/101 5356aee7
@TZUTC: -0400
@SEEN-BY: 1/1 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 @SEEN-BY: 116 117 118 119 120 121 122 123 124 125 127 128 129 130 131 133 134 @SEEN-BY: 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 @SEEN-BY: 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 @SEEN-BY: 169 171 172 173 174 175 176 177 178 179 181 182 183 184 185 186 187 @SEEN-BY: 188 189 190 191 192 193 195 197 199 200 999 2/100 3/100 101 102 103 @SEEN-BY: 104 4/100
@PATH: 1/161 100 3/100

Currently, when I try to enter the game from the BBS, I get the error,

"Sorry

Everything checks out fine, so as far as I can tell there is nothing amiss with Mystic nor fsxNet.

I agree, I don't don't see anything amiss either.

I scooped an inbound packet and the seen by lines look right and when I view the seen bys on my BBS here they look like what I posted. I'm not sure why that
is happening.

Happy to look at anything you need.

Thanks, will be in touch.. :)

--- BBBS/Li6 v4.10 Toy-4
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

On 2019 Mar 31 14:25:18, you wrote to Alan Ianson:

@SEEN-BY: 1/1 100 101 102 103 104 105 106 107 108 109 110 111 112 113
114 115
@SEEN-BY: 116 117 118 119 120 121 122 123 124 125 127 128 129 130 131
133 134
@SEEN-BY: 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149
150 151
@SEEN-BY: 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166
167 168
@SEEN-BY: 169 171 172 173 174 175 176 177 178 179 181 182 183 184 185
186 187
@SEEN-BY: 188 189 190 191 192 193 195 197 199 200 999 2/100 3/100
4/100

well, there's the problem... there must be a net on the first address of each line... if they are all in net1, it should look like this:

@SEEN-BY: 1/1 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115
@SEEN-BY: 1/116 117 118 119 120 121 122 123 124 125 127 128 129 130 131 133 134
@SEEN-BY: 1/135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151
@SEEN-BY: 1/152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168
@SEEN-BY: 1/169 171 172 173 174 175 176 177 178 179 181 182 183 184 185 186 187
@SEEN-BY: 1/188 189 190 191 192 193 195 197 199 200 999 2/100 3/100 4/100

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... You can thaw a frozen turkey in a clothes dryer but I wouldn't.
---
* Origin: (1:3634/12.73)

well, there's the problem... there must be a net on the first address of each line... if they are all in net1, it should look like this:

@SEEN-BY: 1/1 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 @SEEN-BY: 1/116 117 118 119 120 121 122 123 124 125 127 128 129 130 131 133

Ahh! I never noticed that. Thanks for that, next time your in town the beer & pizza is on me. :)

--- BBBS/Li6 v4.10 Toy-4
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

On 31 Mar 2019 at 12:53p, mark lewis pondered and said...

well, there's the problem... there must be a net on the first address of each line... if they are all in net1, it should look like this:

Ah. Thanks, is there someone in the specs for this in FTN land that you can point me to the requirement? When Al or I flag this with James it would be helpful to be able to point him to it.

I took a look at another post from a node in fsxNet and indeed there are no
NET lines stated at the start of each SEEN-BY

It's the first time it seems to have been an issue for anyone/system though.

[snip]

@TID: Mystic BBS 1.12 A43
@MSGID: 21:4/137 98af6bc5
@REPLY: 19305.fsx-fsx_gen@21:1/109 2105d695
@TZUTC: -0600
@SEEN-BY: 1/1 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 @SEEN-BY: 116 117 118 119 120 121 122 123 124 125 127 128 129 130 131 133 134 @SEEN-BY: 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 @SEEN-BY: 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 @SEEN-BY: 169 171 172 173 174 175 176 177 178 179 181 182 183 184 185 186 187 @SEEN-BY: 188 189 190 191 192 193 195 197 199 200 999 2/100 3/100 4/10 100 101 @SEEN-BY: 102 104 105 106 107 108 109 11 110 112 114 116 117 118 119 121 122
12
@SEEN-BY: 124 125 128 129 131 133 134 135 136 137 138 139 140 141 143 144 145 @SEEN-BY: 146 147 148 150 151
@PATH: 4/137 100 1/100

[snip]

Best, Paul

--- E:avon@bbs.nz ------ W:bbs.nz ---
--- K:keybase.io/avon --------------

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)

On 31 Mar 2019 at 12:53p, mark lewis pondered and said...

well, there's the problem... there must be a net on the first address of each line... if they are all in net1, it should look like this:

Hi Mark.

This is not an area of expertise for me but I went looking for info on the fstc.org site and found this

[snip]

Seen-by Lines

There can be many seen-by lines at the end of Conference
Mail messages, and they are the real "meat" of the control
information. They are used to determine the systems to
receive the exported messages. The format of the line is:

SEEN-BY: 132/101 113 136/601 1014/1

The net/node numbers correspond to the net/node numbers of
the systems having already received the message. In this way
a message is never sent to a system twice. In a conference
with many participants the number of seen-by lines can be
very large. This line is added if it is not already a part
of the message, or added to if it already exists, each time
a message is exported to other systems. This is a REQUIRED
field, and Conference Mail will not function correctly if
this field is not put in place by other Echomail compatible
programs.

[snip]

There does not seem to be any reference to requiring that NET be displayed at the start of each SEEN-BY line - perhaps I should be looking at another reference doc?

Best, Paul

--- E:avon@bbs.nz ------ W:bbs.nz ---
--- K:keybase.io/avon --------------

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)

Ah. Thanks, is there someone in the specs for this in FTN land that you can point me to the requirement? When Al or I flag this with James it would be helpful to be able to point him to it.

I'll let you bring that up with JC, but if my input is needed you know where to
find me. :)

--- BBBS/Li6 v4.10 Toy-4
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

On 2019 Apr 01 09:28:32, you wrote to me:

well, there's the problem... there must be a net on the first address
of each line... if they are all in net1, it should look like this:

Ah. Thanks,

welcome...

is there someone in the specs for this in FTN land that you can point
me to the requirement? When Al or I flag this with James it would be helpful to be able to point him to it.

i gave a cursory look this morning because i wanted to point you to it but i wasn't able to find anything in a short 5 minute search... all i can say is that this is the way it has been being done ever since i joined fidonet... that
was shortly before P4 was presented and voted on...

I took a look at another post from a node in fsxNet and indeed there
are no NET lines stated at the start of each SEEN-BY

if they're all mystic posts, it is easy to see...

It's the first time it seems to have been an issue for anyone/system though.

well, it would maybe be noticible to some because of dupe checking since it uses the seenbys for that... in the case presented here, the software was filling in the missing net with 0 so that made it more noticible... the only thing i can suggest, right now, would be to query in FTSC_PUBLIC... my search-fu is pretty broken right now... i know i've seen the info but cannot remember where... granted, it was 20+ years ago when i saw it while working on a seenby related project...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... It's a sad, sad day when a proper chili gets beaned.
---
* Origin: (1:3634/12.73)

On 2019 Apr 01 09:40:54, you wrote to me:

This is not an area of expertise for me but I went looking for info on the fstc.org site and found this

that's the current base document, yes...

[snip]

There does not seem to be any reference to requiring that NET be displayed at the start of each SEEN-BY line

correct... there isn't in there... there's also no mention of the squashed format where additional nodes in the same net and one the same line drop the net/ part but we all know that it is done like that...

- perhaps I should be looking at another reference doc?

i'm not sure which one that would be...

the thing i don't understand is it was working properly before so why did james
""fix"" it?? ;) ;) ;)

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... We are watching, and we are always here.
---
* Origin: (1:3634/12.73)

Hello Paul.

[snip]
From: nristen
To: Avon
Subj: Re: Galactic Dynasty
Date: 03/30/19 13:05
Base: FSX_GEN
@TID: Mystic BBS 1.12 A42
@MSGID: 21:1/161 2ea3e523
@REPLY: 21:1/101 5356aee7
@TZUTC: -0400
@SEEN-BY: 1/1 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 @SEEN-BY: 116 117 118 119 120 121 122 123 124 125 127 128 129 130 131 133 134 @SEEN-BY: 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 @SEEN-BY: 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 @SEEN-BY: 169 171 172 173 174 175 176 177 178 179 181 182 183 184 185 186 187 @SEEN-BY: 188 189 190 191 192 193 195 197 199 200 999 2/100 3/100 4/100

The problem as I see it is that the net needs to be specified at the beginning of each line to indicate which net the following nodes belong in. Until a new or different net is specified. The same principle is true and used in the setup
of many pieces of FTN software.

I would surmise that the Seen-By lines are not looked at as one continuous line
but as separate sequential lines. And therefor the net specification would need
to be specified at the beginning of each line.


Jeff

--- BBBS/Li6 v4.10 Toy-4
* Origin: Fidoneet: The Ouija Board - Anoka, MN -bbs.ouijabrd.net (1:282/1031)

On 01 Apr 2019 at 12:09a, Jeff Smith pondered and said...

The problem as I see it is that the net needs to be specified at the beginning of each line to indicate which net the following nodes belong in. Until a new or different net is specified. The same principle is
true and used in the setup of many pieces of FTN software.

I would surmise that the Seen-By lines are not looked at as one
continuous line but as separate sequential lines. And therefor the net specification would need to be specified at the beginning of each line.

Hi Jeff

Yes Mark has basically said the same thing.

I have sought clarification in the FTSC echo in an attempt to find some documentation that confirms this. Perhaps it's a case of some FTN software looks for this whilst others do not?

Best, Paul

--- E:avon@bbs.nz ------ W:bbs.nz ---
--- K:keybase.io/avon --------------

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)

On 2019 Apr 01 20:11:38, you wrote to Jeff Smith:

I have sought clarification in the FTSC echo in an attempt to find some

you mean FTSC_PUBLIC, right? there is a FTSC echo but it is limited access to only FTSC members and invited guests...

documentation that confirms this. Perhaps it's a case of some FTN
software looks for this whilst others do not?

no, the seenby lines have been done like that ever since they were introduced...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... Biology grows on you.
---
* Origin: (1:3634/12.73)

On 01 Apr 2019 at 11:26a, mark lewis pondered and said...

you mean FTSC_PUBLIC, right? there is a FTSC echo but it is limited

Yep :)

no, the seenby lines have been done like that ever since they were introduced...

Coolio thanks Mark :)

Best, Paul

--- E:avon@bbs.nz ------ W:bbs.nz ---
--- K:keybase.io/avon --------------

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)