I continue to have problems connecting from my system to the boss node using binkP.
The HobbyNet network resides on hobbylinebbs.com My Synchronet system is on hobby-bbs.com
When I try areafix to 954:895/1 from my system at 954:895/35 I get an error. It tries
to connect to:
f35.n895.z954.example.com:24554
Where is the word example defined? It should be hobbylinebbs.com
I tried going to binkp.net to enter and I get the error: Error: Node 954:895/35 missing
in the nodelist.318 and there is no way for me to add it.
I'm stumped.
Mike Dippel
I continue to have problems connecting from my system to the boss node using binkP.
The HobbyNet network resides on hobbylinebbs.com My Synchronet system is on hobby-bbs.com
When I try areafix to 954:895/1 from my system at 954:895/35 I get an error. It tries
to connect to:
f35.n895.z954.example.com:24554
Where is the word example defined?
It should be hobbylinebbs.com
I tried going to binkp.net to enter and I get the error: Error: Node 954:895/35 missing
in the nodelist.318 and there is no way for me to add it.
I'm stumped.
Re: Re: Error: Node missing in nodelist
By: Ragnarok to Mike Dippel on Sun Nov 14 2021 03:32 pm
The first thing listed in 'Linked Node' is the address. Is that MY node of 954:895/35
For BinkP settings I am listing the host as: hobbylinebbs.com with a port of 24554
This is obviously wrong since it is not working. Can you suggest what changes I have to make?
I continue to have problems connecting from my system to the boss node using
binkP.
I replied to previous requests for help 3 days ago with suggestions and follow-up questions. You never answered.
Isn't 954:895/35 *your* system's addrses? (I asked you this question previously
and you did not answer). If that is *your* system's address, and your system is
trying to connect to f35.n895.z954... do you see the problem? That domain name
is clearly 954:895/35. So, you did something wrong.
I tried going to binkp.net to enter and I get the error: Error: Node 954:895/35 missing
in the nodelist.318 and there is no way for me to add it.
I'm stumped.
binkp.net is for FidoNet zones. Zone 954 is not a FidoNet zone, so you can't use binkp.net based address lookups. The problem here appears to be the FidoNet
address anyway - you're trying to send or route to 954:895/35 instead of 954:895/1. Fix that problem first.
--
On 11/14/2021 3:46 PM, Digital Man wrote to Mike Dippel:
I continue to have problems connecting from my system to the boss node using
binkP.
I replied to previous requests for help 3 days ago with suggestions and follow-up questions. You never answered.
I have been working hard for days to figure out the configuration and cannot find
anything that will help me online. I started a network on my local machine and someone wanted to carry the feed but only had binkP protocol. I registered iRex to
accommodate them.
Would I be better off doing it QWK like the Dove-Net feed?
I wasn't looking for criticism for not knowing the first thing about how to set it up on the
receiver side. I was hoping for someone to help me fill in the blanks and make it work.
Re: Re: Error: Node missing in nodelist
By: Ragnarok to Mike Dippel on Sun Nov 14 2021 03:32 pm
The first thing listed in 'Linked Node' is the address. Is that MY node of
954:895/35
No. *your* node address should not be listed in echocfg->Linked Nodes. I already asked you about this and clarified this for you multiple times. Are you
not seeing my replies to your inquiries?
digital man
Synchronet "Real Fact" #46:
Synchronet External X/Y/ZMODEM protocol driver (SEXYZ) was introduced in 2005.
Norco, CA WX: 76.0ÿF, 32.0% humidity, 1 mph NE wind, 0.00 inches rain/24hrs --- SBBSecho 3.14-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
On 11/14/2021 7:07 PM, Digital Man wrote to Mike Dippel:
Re: Re: Error: Node missing in nodelist
By: Ragnarok to Mike Dippel on Sun Nov 14 2021 03:32 pm
The first thing listed in 'Linked Node' is the address. Is that MY node of
954:895/35
Deleted 'Linked Nodes' and am trying QWK nw.
No. *your* node address should not be listed in echocfg->Linked Nodes. I already asked you about this and clarified this for you multiple times. Are you
not seeing my replies to your inquiries?
OK. Trying QWK, I copied the info for Dove into a new Net I call HOBBYBBS' I have all of the HobbyNet conferences set to connect to the corresponding conferemces
on the hub.
I created a user on the hub named hobbybbs with a fast login to the QWK/REP area.
I created a security level on the hub that allows the user 'hobbybbs' to download a
packet specific to his security level.
My command line on the Synchronet BBS for the QWK Network Hub of hobbybbs is: *qnet-ftp %s hobbylinebbs.com Mypassword
When I try the QNET poll from Synchronet, it scans the conference areas and creates
the packet but gives the error:
Download of HOBBYBBS.qwk failed: Error: Unable to connect
Any suggestions? The security level I assigned for that user does accept FTP connections.
I read through the documentation of configuring a hub. Thanks for that.
The hub for HobbyNet is located at hobbylinebbs.com and the QWK packet is named HOBBY.QWK
Looks like I just need the command line to connect from hobby-bbs.com to the boss node at hobbylinebbs.com
The hub is a Winserver system. I looked in the c:\sbbs\exec directory for example scripts and couldn't find anything to suggest how to create a batch file for telnet. I don't have Telix, robocomm or Qmodem anyway.
I just need the command line to connect the 2 systems.
I would rather use FTN, but I thought you said the node for 954 (HobbyNet) is not Fido and couldn't be used.
Sorry to be such a pain. I just need to learn this.
I read through the documentation of configuring a hub. Thanks for that.
The hub for HobbyNet is located at hobbylinebbs.com and the QWK packet is named HOBBY.QWK
So HobbyNet is not *your* network, but someone else's? I can't keep your BBS names and hostnames straight here.
Your BBS appears to be "HOBBYBBS" and the HobbyNet hub BBS is a someone else's
BBS with a QWK-ID of "HOBBY"?
Looks like I just need the command line to connect from hobby-bbs.com to the
boss node at hobbylinebbs.com
Does hobbylinebbs.com support QWK packet transfers via FTP?
The hub is a Winserver system. I looked in the c:\sbbs\exec directory for
example scripts and couldn't find anything to suggest how to create a batch
file for telnet. I don't have Telix, robocomm or Qmodem anyway.
If the Winserver system doesn't support QWK packet transfer via FTP, then you'll have to come up with some other means of automated packet transfer. What
does the hub suggest you use?
I just need the command line to connect the 2 systems.
The hub sysop should be the expert on this matter... it is his network.
I would rather use FTN, but I thought you said the node for 954 (HobbyNet)
is not Fido and couldn't be used.
I did not say zone 954 could not be used. FidoNet consists of only zones 1-6.
Any other FTN zones are considered "othernets" are not part of FidoNet proper.
The same tools (e.g. mailers, tossers) may be used for "othernets", but binkp.net DNS-based lookup only works for FidoNet proper.
Have you read this?
https://wiki.synchro.net/ref:fidonet_glossary
On 11/16/2021 12:38 PM, Digital Man wrote to Mike Dippel:
I read through the documentation of configuring a hub. Thanks for that.
The hub for HobbyNet is located at hobbylinebbs.com and the QWK packet is named HOBBY.QWK
So HobbyNet is not *your* network, but someone else's? I can't keep your BBS names and hostnames straight here.
I run the hub for HobbyNet at my server located at hobbylinebbs.com I am the boss
node: 954:895/1
Your BBS appears to be "HOBBYBBS" and the HobbyNet hub BBS is a someone else's
BBS with a QWK-ID of "HOBBY"?
I am testing your software on a home machine, running the downlink node 954:895/35
So I am both the hub (/1) and the downlink (/35).
The hub's QWK name is HOBBY.QWK
But I would love to do it as an FTN connection, like 33 of my downlinks successfully do.
They use their Mystic, WWIV and Synchronet systems to connect to my iREX hub to send and receive their packets.
I just want to be able to do the same.
Looks like I just need the command line to connect from hobby-bbs.com to the
boss node at hobbylinebbs.com
Does hobbylinebbs.com support QWK packet transfers via FTP?
The hub is a Winserver system. I looked in the c:\sbbs\exec directory for
example scripts and couldn't find anything to suggest how to create a batch
file for telnet. I don't have Telix, robocomm or Qmodem anyway.
If the Winserver system doesn't support QWK packet transfer via FTP, then you'll have to come up with some other means of automated packet transfer. What
does the hub suggest you use?
I just need the command line to connect the 2 systems.
The hub sysop should be the expert on this matter... it is his network.
I know how to set iut up on my setup so others can connect. I just have to learn how to
do it as a downlink.
I would rather use FTN, but I thought you said the node for 954 (HobbyNet)
is not Fido and couldn't be used.
I did not say zone 954 could not be used. FidoNet consists of only zones 1-6.
Any other FTN zones are considered "othernets" are not part of FidoNet proper.
The same tools (e.g. mailers, tossers) may be used for "othernets", but binkp.net DNS-based lookup only works for FidoNet proper.
Again, it works for my downlinks.
I am able to connect but not send or
receive packets.
I get the error that it received M_EOB but there are files pending M_GOT
Maybe I need to define a path for them to get to?
I run the hub for HobbyNet at my server located at hobbylinebbs.com I am the boss
node: 954:895/1
That's good to know.
Your BBS appears to be "HOBBYBBS" and the HobbyNet hub BBS is a someone
else's
BBS with a QWK-ID of "HOBBY"?
I am testing your software on a home machine, running the downlink node 954:895/35
So I am both the hub (/1) and the downlink (/35).
The hub's QWK name is HOBBY.QWK
But I would love to do it as an FTN connection, like 33 of my downlinks successfully do.
They use their Mystic, WWIV and Synchronet systems to connect to my iREX hub
to send and receive their packets.
I just want to be able to do the same.
You should be able to.
The hub sysop should be the expert on this matter... it is his network.
I know how to set it up on my setup so others can connect. I just have to
learn how to
do it as a downlink.
We seem to be mixing up the discussion between QWK networking and FTN now.
I would rather use FTN, but I thought you said the node for 954 (HobbyNet)
is not Fido and couldn't be used.
I did not say zone 954 could not be used. FidoNet consists of only zones
1-6.
Any other FTN zones are considered "othernets" are not part of FidoNet proper.
The same tools (e.g. mailers, tossers) may be used for "othernets", but
binkp.net DNS-based lookup only works for FidoNet proper.
Again, it works for my downlinks.
If "it" is binkp.net DNS-based node address look-ups, no, it's not. Your downlinks have configured their systems correctly to connect to your hostname.
I am able to connect but not send or
receive packets.
I get the error that it received M_EOB but there are files pending M_GOT
You likely can ignore that error.
My big stumbling block now is that when I send a areafix from 954:895/35 to the hub,
areafix recognizes the system as 954:895/0 instead of 954:895/35 as I have it set up
as. I don't ever receive replies to the areafix, just a notice that /0 is not configured.
My big stumbling block now is that when I send a areafix from 954:895/35 to
the hub,
areafix recognizes the system as 954:895/0 instead of 954:895/35 as I have
it set up
as. I don't ever receive replies to the areafix, just a notice that /0 is
not configured.
I understand. I think the next step would be to answer the question I asked you
previously about those areafix message (i.e. how was it sent) and to check your
sbbsecho.log file for the originating address details.
Mike Dippel wrote to Digital Man <=-
My big stumbling block now is that when I send a areafix from
954:895/35 to the hub, areafix recognizes the system as 954:895/0
instead of 954:895/35 as I have it set up as. I don't ever
receive replies to the areafix, just a notice that /0 is not
configured.
On 11/16/2021 4:02 PM, Digital Man wrote to Mike Dippel:
My big stumbling block now is that when I send a areafix from 954:895/35 to
the hub,
areafix recognizes the system as 954:895/0 instead of 954:895/35 as I have
it set up
as. I don't ever receive replies to the areafix, just a notice that /0 is
not configured.
I understand. I think the next step would be to answer the question I asked you
previously about those areafix message (i.e. how was it sent) and to check your
sbbsecho.log file for the originating address details.
I think I am getting closer now. The log file showed that the areas.bbs file did not exist.
I created one (it's blank}. Once I did that I did another areafix and the echostats.ini file
now shows all of the conferences.
Unfortunately, The messages do not show
up on the
system in the conference areas.
My areafix format via option N (send netmail) is:
areafix@954:895/1
PW in the subject line.
and %+help in the message body. I also tried %+all and %rescan*
but got no response.
I assume the areas.bbs file has to contain some info.
Not sure how to generate it though.
I manually added all of the HNET conferences myself.
My big stumbling block now is that when I send a areafix from 954:895/35 to
the hub,
areafix recognizes the system as 954:895/0 instead of 954:895/35 as I have
it set up
as. I don't ever receive replies to the areafix, just a notice that /0 is
not configured.
I understand. I think the next step would be to answer the question I asked you
previously about those areafix message (i.e. how was it sent) and to check your
sbbsecho.log file for the originating address details.
Mike Dippel wrote to Digital Man <=-
My big stumbling block now is that when I send a areafix from 954:895/35 to the hub, areafix recognizes the system as 954:895/0 instead of 954:895/35 as I have it set up as. I don't ever
receive replies to the areafix, just a notice that /0 is not configured.
Do you have 954:895/35 defined in:
SCFG/Networks/FidoNet EchoMail and NetMail/System Addresses ?
... Don't cry for me I have vi.
--- MultiMail/Linux v0.52
ÿ Synchronet ÿ Palantir BBS * palantirbbs.ddns.net * Pensacola, FL
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
Mike Dippel wrote to Gamgee <=-
My big stumbling block now is that when I send a areafix from 954:895/35 to the hub, areafix recognizes the system as 954:895/0 instead of 954:895/35 as I have it set up as. I don't ever
receive replies to the areafix, just a notice that /0 is not configured.
Do you have 954:895/35 defined in:
SCFG/Networks/FidoNet EchoMail and NetMail/System Addresses ?
Yes on both counts. But it may be incorrect. For Fidonet,
Echomail and NetMail, I have both the fido address of 3:640/1116
and my address for this system of 954:895/35 and the Choose
Network Source Address set to YES
Is this correct? I am not carrying a Fido feed yet here, just on
my main system at hobbylinebbs.com
Mike Dippel wrote to Gamgee <=-
Does Synchronet have the ability to compile the nodelist? I see
that yours is way out of date.
Mike Dippel wrote to Gamgee <=-
Re: Re: Error: Node missing in nodelist
By: Gamgee to Mike Dippel on Wed Nov 17 2021 08:04 am
You don't know how much I appreciate your post. Thanks much.
Looks like I am finally connected. Now I can hopefully help
other sysOPs running Synchronet to connect.
| Sysop: | Nelgin |
|---|---|
| Location: | Plano, TX |
| Users: | 513 |
| Nodes: | 10 (1 / 9) |
| Uptime: | 05:08:55 |
| Calls: | 8,286 |
| Calls today: | 3 |
| Files: | 15,517 |
| Messages: | 928,319 |