Hello All!

As I seem to be the only one posting here this is a test for linkage.

Anyone else getting MBSE ?


Vince

--- Linux/Mbse v1.1.02/GoldED+/LNX 1.1.5-b20120229
* Origin: Air Applewood, The Linux Gateway to the UK (2:250/1)

Hi,

On 2014-05-03 16:10:06, Vince Coen wrote to All:
about: "Test for links etc":

As I seem to be the only one posting here this is a test for linkage.

Anyone else getting MBSE ?

Yes, but I'm not too interested in MBSE... ;)

SEEN-BY: 12/0 19/33 34/999 90/1 116/18 120/331 123/500 1406 128/187 135/364
SEEN-BY: 140/1 154/10 203/0 218/700 221/1 226/0 160 230/0 150 240/1120 SEEN-BY: 249/0 134 300 303 250/1 255/28 261/38 100 266/185 404 1413 SEEN-BY: 267/155 280/464 5003 292/907 908 311/2 320/119 322/762
340/400
SEEN-BY: 393/68 396/45 633/260 640/384 712/848 801/161 189 5030/1256

So lot's of systems got it...

@PATH: 250/1 261/38 249/303 203/0 280/464

And also through:

@PATH: 250/1 261/38 712/848

But /848 strips seen-by's, so there wasn't anything there...

Bye, Wilfred.


--- FMail-W32-1.68.1.61-B20140411
* Origin: Native IPv6 connectable node (2:280/464)

Hi! Vince,

In a message to All you wrote:

As I seem to be the only one posting here this is a test for linkage. Anyone else getting MBSE ?

Yes, though I cannot understand why I still read most posts. I've been peeking
for years, thinking of trying MBSE... that's all: thinking about trying it.

Your note came here via...

@PATH: 250/1 261/38 712/848

It suffered the same treatment as noted by Wilfred. The out-of-zone SEEN-BYs having been stripped by the HPT mail processor at Scott Little's joint..

Cheers,
Paul.

... On the other hand, you have different fingers.
--- Paul's Win98SE VirtualBox
* Origin: Quinn's Post - Maryborough, Queensland, OZ (3:640/384)

Paul Quinn wrote to Vince Coen <=-

Hiya Paul...

In a message to All you wrote:

As I seem to be the only one posting here this is a test for linkage. Anyone else getting MBSE ?

Yes, though I cannot understand why I still read most posts. I've been peeking for years, thinking of trying MBSE... that's all: thinking
about trying it.

Your note came here via...

@PATH: 250/1 261/38 712/848

It suffered the same treatment as noted by Wilfred. The out-of-zone SEEN-BYs having been stripped by the HPT mail processor at Scott
Little's joint..

Is this the same thing Bjorn was screaming about?


Bill

Telnet: bbs.tequilamockingbirdonline.net
Web: bbs.tequilamockingbirdonline.net
IRC: irc.tequilamockingbirdonline.net Ports: 6661-6670 SSL: +6697
Radio: radio.tequilamockingbirdonline.net:8010/live


... Motorcycles are everywhere... Look twice, save a life!!
--- MultiMail/Win32 v0.50
--- SBBSecho 2.27-Win32
* Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)

Hi! Bill,

On Sat, 03 May 14, you wrote to me:

@PATH: 250/1 261/38 712/848

out-of-zone SEEN+BYs having been stripped by the HPT mail
processor at Scott Little's joint..

Is this the same thing Bjorn was screaming about?

Probably. It's a defect in HPT apparently. It's supposed to be being fixed, one way or t'other: complete compatibility with other FTN tossers or abled to be switched on/off with an option-line parameter.

Cheers,
Paul.

... I'm a modemer and I'm OK. I post all night and I sleep all day...
--- Paul's Win98SE VirtualBox
* Origin: Quinn's Post - Maryborough, Queensland, OZ (3:640/384)

Paul Quinn wrote to Bill Mcgarrity <=-

Hiya Paul...

On Sat, 03 May 14, you wrote to me:

@PATH: 250/1 261/38 712/848

out-of-zone SEEN+BYs having been stripped by the HPT mail
processor at Scott Little's joint..

Is this the same thing Bjorn was screaming about?

Probably. It's a defect in HPT apparently. It's supposed to be being fixed, one way or t'other: complete compatibility with other FTN
tossers or abled to be switched on/off with an option-line parameter.

OK.. good deal. There was so much being made of it back then and being sbbsecho was the "culprit du jour", I was scratching my head. :)

Have a good one!!


Bill

Telnet: bbs.tequilamockingbirdonline.net
Web: bbs.tequilamockingbirdonline.net
IRC: irc.tequilamockingbirdonline.net Ports: 6661-6670 SSL: +6697
Radio: radio.tequilamockingbirdonline.net:8010/live


... Motorcycles are everywhere... Look twice, save a life!!
--- MultiMail/Win32 v0.50
--- SBBSecho 2.27-Win32
* Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)

On Sat, 03 May 2014, Vince Coen wrote to All:

@MSGID: 2:250/1@fidonet 536506fd
@CHRS: UTF-8 2
@TZUTC: 0100
@TID: MBSE-FIDO 1.0.2 (GNU/Linux-x86_64)
Hello All!

As I seem to be the only one posting here this is a test for
linkage.

Anyone else getting MBSE ?

yes... here's your control lines so you can see all the other systems that are also seeing it...

Vince

___ Linux/Mbse v1.1.02/GoldED+/LNX 1.1.5-b20120229
- Origin: Air Applewood, The Linux Gateway to the UK (2:250/1)
@EEN-BY: 19/33 34/999 90/1 116/18 120/331 123/5 52 57 140 500 789 1406 @EEN-BY: 124/25 5013 128/187 135/364 140/1 154/10 218/700 226/0 160 600 @EEN-BY: 229/426 230/150 240/1120 249/303 250/1 261/38 100
266/185 404 1413
@EEN-BY: 267/155 292/907 908 311/2 320/119 322/759 762 340/400
342/11 393/68
@EEN-BY: 396/45 633/260 712/848 801/161 189 3634/12 22 50 5030/1256
@ATH: 250/1 261/38 123/500 3634/12

)\/(ark

One of the great tragedies of life is the murder of a beautiful theory by a gang of brutal facts. --Benjamin Franklin

--- FMail/Win32 1.60
* Origin: (1:3634/12.71)

Hello Vince!

03 May 14 16:10, you wrote to all:

As I seem to be the only one posting here this is a test for linkage. Anyone else getting MBSE ?

Gotcha here.

Andrew

--- GoldED+/LNX 1.1.5-b20130111
* Origin: Phoenix BBS * phoenix.bnbbbs.net:2323 (1:320/219)

Hello Andrew and all others who responded!

Sunday May 04 2014 21:42, you wrote to me:

Hello Vince!

03 May 14 16:10, you wrote to all:

As I seem to be the only one posting here this is a test for
linkage. Anyone else getting MBSE ?

Gotcha here.

I have been forwarding on problem from another budding mbse user who is using ubuntu and who states that the issue he is having also applies to Slackware which des not appear to be related to the gengoo/ubutu family.

I am struggling to see what library / headers he is missing that is causing the
problem with mbindex that is not previously reported with configure or make.

Ok, I am totally lost on this.

I was thinking is was related to the nodelist change that removed the PVT flag and added '-Unpublished-' for phone number but I am not seeing it for 1:1/1 or my own 2:250/1.

So, do not believe it relates to that. I still need an instance where it is wrong where node flags are not correctly defined in listings in someway as shown for the original post but wothout any details.

So far based on the number of replies I have had it does appear that the number
of sysops using mbse has shrunk or just have not responded.

Such is life.

Vince

--- Linux/Mbse v1.1.02/GoldED+/LNX 1.1.5-b20120229
* Origin: Air Applewood, The Linux Gateway to the UK (2:250/1)

Hello Vince.

03 May 14 16:10, you wrote to all:

Hello All!

As I seem to be the only one posting here this is a test for linkage.

Anyone else getting MBSE ?

Might not read it everyday, but I'm certianly receiving it...



Jame

--- GoldED+/LNX 1.1.5-b20110213
* Origin: ftn.rocasa.net (1:120/544)

Hello Vince!

05 May 14 15:26, you wrote to me:

I have been forwarding on problem from another budding mbse user who
is using ubuntu and who states that the issue he is having also
applies to Slackware which des not appear to be related to the gengoo/ubutu family.

Ubuntu is a derivative of Debian; Slackware's only relation to either is that they are both GNU/Linux distributions.

I am struggling to see what library / headers he is missing that is causing the problem with mbindex that is not previously reported with configure or make.

I would think if he was missing libraries, there would have been an error while building the BBS.

Ok, I am totally lost on this.

I was thinking is was related to the nodelist change that removed the
PVT flag and added '-Unpublished-' for phone number but I am not
seeing it for 1:1/1 or my own 2:250/1.

The issue I was having occurred with an othernet nodelist, but I noted that overriding the node's flags also results in the (null) url field.

So, do not believe it relates to that. I still need an instance where
it is wrong where node flags are not correctly defined in listings in someway as shown for the original post but wothout any details.

I am thinking the issue is the code in nodelist.c starting at line 921 which builds the connection URL. I need to trace it through processing a few nodelist entries to figure out where the problem is starting.

So far based on the number of replies I have had it does appear that
the number of sysops using mbse has shrunk or just have not responded. Such is life.

Yep.

Andrew


--- GoldED+/LNX 1.1.5-b20130111
* Origin: Phoenix BBS * phoenix.bnbbbs.net:2323 (1:320/219)

Hello Vince!

I only use MBcico for connection with a special downlink.

I did notivce the problem you describe, but I did not give it much notice as I could solve it with a direct entry for the node in question.

When MBSE reads the nodelist, it expects the dnsname to me in the nodename field, or the ip number in the phone filed, or as eb extent to the IBN flag.

MBSE does not know about the INA flag. With the change to -Unpublished- many systems and especially functional numbers returned to using function names in the bbs-name field and moved the dns name to the INA flag.

So a change is needed to include the INA flag as a possible source of the node name, or you have to use a preprocessor, that modifies the nodelist in such a way that the hostname is put in the bbs-namefield.

So the problem is nodelist related and not specific for Linux distribution.

My needs are so low, that it is not likely that I will take the challenge, but maybe Andrew will, if you are not up to it yourself.

05 May 14 15:26, you wrote to Andrew Leary:

Hello Andrew and all others who responded!

Sunday May 04 2014 21:42, you wrote to me:

Hello Vince!

03 May 14 16:10, you wrote to all:

As I seem to be the only one posting here this is a test for
linkage. Anyone else getting MBSE ?

Gotcha here.

I have been forwarding on problem from another budding mbse user who is using ubuntu and who states that the issue he is having also applies to Slackware which des not appear to be related to the gengoo/ubutu family.

I am struggling to see what library / headers he is missing that is causing
the problem with mbindex that is not previously reported with configure or make.

Ok, I am totally lost on this.

I was thinking is was related to the nodelist change that removed the PVT flag and added '-Unpublished-' for phone number but I am not seeing it for 1:1/1 or my own 2:250/1.

So, do not believe it relates to that. I still need an instance where it is wrong where node flags are not correctly defined in listings in someway as shown for the original post but wothout any details.

So far based on the number of replies I have had it does appear that the number
of sysops using mbse has shrunk or just have not responded.

Such is life.

Vince

--- Linux/Mbse v1.1.02/GoldED+/LNX 1.1.5-b20120229
* Origin: Air Applewood, The Linux Gateway to the UK (2:250/1)

Kees


--- FPD v2.9.040207 GoldED+/LNX 1.1.5--b20130910
* Origin: As for me, all I know is that, I know nothing. (2:280/5006.4)

Hello Kees!

Wednesday May 07 2014 15:14, you wrote to me:

When MBSE reads the nodelist, it expects the dnsname to me in the
nodename field, or the ip number in the phone filed, or as eb extent
to the IBN flag.

MBSE does not know about the INA flag. With the change to
-Unpublished- many systems and especially functional numbers returned
to using function names in the bbs-name field and moved the dns name
to the INA flag.

So a change is needed to include the INA flag as a possible source of
the node name, or you have to use a preprocessor, that modifies the
nodelist in such a way that the hostname is put in the bbs-namefield.

So the problem is nodelist related and not specific for Linux
distribution.

My needs are so low, that it is not likely that I will take the
challenge, but maybe Andrew will, if you are not up to it yourself.

The flag INA is the primary source for an IP address. In fact according to my reading of the nodelist summary near the bottom of it INA is the only flag that
relates to such.

If you know of another method please let me know.



Vince

--- Linux/Mbse v1.1.02/GoldED+/LNX 1.1.5-b20120229
* Origin: Air Applewood, The Linux Gateway to the UK (2:250/1)

Hello Vince!

07 Mai 14 17:25, you wrote to me:

Hello Kees!

Wednesday May 07 2014 15:14, you wrote to me:

When MBSE reads the nodelist, it expects the dnsname to me in the
nodename field, or the ip number in the phone filed, or as eb extent
to the IBN flag.

MBSE does not know about the INA flag. With the change to
-Unpublished- many systems and especially functional numbers returned
to using function names in the bbs-name field and moved the dns name
to the INA flag.

So a change is needed to include the INA flag as a possible source of
the node name, or you have to use a preprocessor, that modifies the
nodelist in such a way that the hostname is put in the bbs-namefield.

So the problem is nodelist related and not specific for Linux
distribution.

My needs are so low, that it is not likely that I will take the
challenge, but maybe Andrew will, if you are not up to it yourself.

The flag INA is the primary source for an IP address. In fact according to my reading of the nodelist summary near the bottom of it INA is the only flag that relates to such.

If you know of another method please let me know.

I only connect to one node. I did a session setup for that node.
I beleive you have to do that anyway for all nodes where you use a
session password. In that same menu you can enter a "Inet Hostname".

It is not a convenient as getting from the nodelist, but it works.

Another solution is to make a script where you rebuild the nodelist.
With that script you copy the dns from the INA flag to the system namefield.
Another option that may work is to use sed, the streaming editor, to remove
all bare IBN flags and then again to rename all INA flags to IBN.

It would add up to someting like sed -e 's/IBN,//' -e 's/INA:/IBN:/' nodelist.xxx > nodelist.yyy

I did not try the above.

If mbse is picky about the checksum, process the resulting file with makenl.

There is a section in ../etc/nodelist.conf that documents where
mbse expects to find a dns name or ip address.

The code that parses the nodelist is in lib/nodelist.c

I did not study the code, so I cannot say more.

Kees


--- FPD v2.9.040207 GoldED+/LNX 1.1.5--b20130910
* Origin: As for me, all I know is that, I know nothing. (2:280/5006.4)

Hello Kees!

Wednesday May 07 2014 21:32, you wrote to me:

When MBSE reads the nodelist, it expects the dnsname to me in the
nodename field, or the ip number in the phone filed, or as eb
extent to the IBN flag.

MBSE does not know about the INA flag. With the change to
-Unpublished- many systems and especially functional numbers
returned to using function names in the bbs-name field and moved
the dns name to the INA flag.

So a change is needed to include the INA flag as a possible source
of the node name, or you have to use a preprocessor, that modifies
the nodelist in such a way that the hostname is put in the
bbs-namefield.

So the problem is nodelist related and not specific for Linux
distribution.

My needs are so low, that it is not likely that I will take the
challenge, but maybe Andrew will, if you are not up to it
yourself.

The flag INA is the primary source for an IP address. In fact
according to my reading of the nodelist summary near the bottom
of it INA is the only flag that relates to such.

If you know of another method please let me know.

I meant other method of storing the IP address within the NODELIST other than after INA:



Vince

--- Linux/Mbse v1.1.02/GoldED+/LNX 1.1.5-b20120229
* Origin: Air Applewood, The Linux Gateway to the UK (2:250/1)

Hello Vince!

07 Mai 14 23:49, you wrote to me:

The flag INA is the primary source for an IP address. In fact
according to my reading of the nodelist summary near the bottom
of it INA is the only flag that relates to such.

If you know of another method please let me know.

I meant other method of storing the IP address within the NODELIST other than after INA:

Yes, but that is defying the purpose of the INA flag.

Then there is what is acceptable to makenl and not at least to your ZC.

Makenl accepts an IP address in the phonefield. That is a no-no in Z2 and
only a few remain in Z1, where they are redundant, as a hostname is also
presented in the system namefield or as an attribute of one of the flags.

Makenl accepts an IP address or hostname as an attribute to IBN: this is
used in Z1, but not accepted in Z2.

Makenl has no concern with the systen name field. For historical reasons,
this field has been overloaded, by holding the DNS hostname of the system.
With the wider use of the INA: flag, many are returning to the folklore
of reusing the system namefield for a personal touch to the node, or
adding info about the administrative function of the node.

I do not expect the net to return to putting the DNS hostname in the
system name field, because MBSE does not support the INA: flag.

On the other hand MBSE is one of the reasons to have the INA: as it
supports three IP protocols.

Kees


--- FPD v2.9.040207 GoldED+/LNX 1.1.5--b20130910
* Origin: As for me, all I know is that, I know nothing. (2:280/5006.4)

* Originally in MBSE

Hello Kees!

Thursday May 08 2014 14:08, you wrote to me:

The flag INA is the primary source for an IP address. In fact
according to my reading of the nodelist summary near the bottom
of it INA is the only flag that relates to such.
If you know of another method please let me know.

I meant other method of storing the IP address within the
NODELIST other than after INA:

Yes, but that is defying the purpose of the INA flag.

Then there is what is acceptable to makenl and not at least to your
ZC.

Makenl accepts an IP address in the phonefield. That is a no-no in Z2
and only a few remain in Z1, where they are redundant, as a hostname
is also presented in the system namefield or as an attribute of one of
the flags.

Makenl accepts an IP address or hostname as an attribute to IBN:
this is used in Z1, but not accepted in Z2.

Is is NOT in the spec here as taken from the nodelist:

;S | IBN[:24554] ......... BinkP protocol

and for INA:

;S | INA[:IP-addres] ..... Flag sets the default Internet address used for ;S | any non-email based IP-flag that does not specify ;S | its own.

Makenl has no concern with the systen name field. For historical
reasons, this field has been overloaded, by holding the DNS hostname
of the system. With the wider use of the INA: flag, many are returning
to the folklore of reusing the system namefield for a personal touch
to the node, or adding info about the administrative function of the
node.

Just as well we ignore that data other than as a name ' ish.

I do not expect the net to return to putting the DNS hostname in the
system name field, because MBSE does not support the INA: flag.

In the 20 odd years I have been in fido I have never seen this mode not that I have been looking mind you and as far as I can see if there is a defined location for a ip address/url eg, INA that is good enough for me.

It would be interesting to see what Ward's options are on this?

On the other hand MBSE is one of the reasons to have the INA: as it
supports three IP protocols.

Well I assume you mean all three variations e.g., URL, IP4 & IP6 when it is needed and no I have not tested it for IP6 and coming to think about it have not noticed IP4 as well.

Mbse is not the only one that looks for the URL/Ip address from the INA flag. It is what the INA flags is for.

Vince

--- Linux/Mbse v1.1.02/GoldED+/LNX 1.1.5-b20120229
* Origin: Air Applewood, The Linux Gateway to the UK (2:250/1)

Hello Vince!

I returned to teh original problem, and tried the the example.
I appears that all I have been saying about the INA: flag and MBSE is not true.

MBSE does gets the DNS hostname from any flag in the Flags section.

08 Mai 14 17:37, you wrote to me:

Makenl accepts an IP address or hostname as an attribute to IBN:
this is used in Z1, but not accepted in Z2.

Is is NOT in the spec here as taken from the nodelist:

;S | IBN[:24554] ......... BinkP protocol

and for INA:

;S | INA[:IP-addres] ..... Flag sets the default Internet address used for
;S | any non-email based IP-flag that does not specify ;S | its own.

Those are the specs that ZC2 accepts.

Below is what MBSE can handle (See /opt/mbse/etc/nodelist.conf)

# field8 - Search in the flags for a FQDN. Valid flags are like: # IBN:domain.com Standard
# IFC:domain.com:port Standard
# IBN:1.2.3.5 Standard
# ITN:1.2.3.4:port Standard
# IBN:* Proposed, use default domain
# IBN:*:port Not yet proposed

In the 20 odd years I have been in fido I have never seen this mode
not
that I have been looking mind you and as far as I can see if there is a defined location for a ip address/url eg, INA that is good enough for me.

I think we were talking about this type of notation:

Hub,1,Rosario_Hub_1,Rosario_SF,Damian_Kleiman,-Unpublished-,300,ICM,IBN:osionli
ne.com.ar,IMI:osiservicios@fibertel.com.ar

It would be interesting to see what Ward's options are on this?

Apparently he has decided against it, as it is not accepted by hist Errorflags
filter.

On the other hand MBSE is one of the reasons to have the INA: as it
supports three IP protocols.

Well I assume you mean all three variations e.g., URL, IP4 & IP6 when it is needed and no I have not tested it for IP6 and coming to think about it have not noticed IP4 as well.

No I meant the three Fidonet transports ITN, IFC and IBN

Incoming IPv6 is handled by inetd or xinetd and needs no modifications
to the programme. For outgoing IPv6 a few system calls have been replaced,
that can handle both IPv4 and IPv6.

When I started supporting IPv6 I was surprized that I got IPv6 connections
wen connecting to the system of Michiel Broek.

Currently Andrew Leary supports IPv6 on his MBSE system.

Mbse is not the only one that looks for the URL/Ip address from the
INA flag. It is what the INA flags is for.

Indeed, it even looks for mailbox type adresses and strips the xxxx@.
I am not shure if MBSE is choosy behind which flag it finds a hostname.

So I think this thread comes to an end, I tried to solve a problem that
is not there, and the original problem is system specific for the one who
posted it.

Kees


--- FPD v2.9.040207 GoldED+/LNX 1.1.5--b20130910
* Origin: As for me, all I know is that, I know nothing. (2:280/5006.4)