• Nodelist/diff status

    From Fred Riccio@1:132/174 to All on Friday, October 09, 2020 10:13:58
    Hello All!

    Back in July I posted a list of nodes that could not be directly connected to using the information in the NodeList. That list had 41 entries. Now we are up to 48. Does anyone care?


    ----- Failed.Txt begins -----
    1:218/410 Server Lookup Failed strontium90.servebbs.com
    1:229/275 Server Lookup Failed id-bbs.ddns.net
    1:229/1014 Server Lookup Failed t311net.ddns.net
    1:13/2 Server Lookup Failed wc4.winserver.org
    1:109/201 Server Lookup Failed bbs.cyberchatnet.com
    1:261/20 Server Lookup Failed wc4.winserver.org
    1:261/220 Server Lookup Failed blues.zapto.org
    1:266/32 Server Lookup Failed eldritch.darktech.org
    1:266/404 Server Lookup Failed ftn.tequilamockingbirdonline.net
    1:267/1 Server Lookup Failed yurykalinin.servemp3.com
    1:267/69 Server Lookup Failed bbs.doilidov.com
    1:267/151 Server Lookup Failed oceanbbs.dyndns.org
    1:267/585 Server Lookup Failed rbbbs.mtonework.com
    1:275/101 Server Lookup Failed cubedwellerbbs.ddns.net
    1:275/103 Server Lookup Failed readyplayertwo.ddns.net
    1:275/201 Server Lookup Failed bbs.cyberchatnet.com
    1:282/1050 Server Lookup Failed dkbbs.shensey.com
    1:282/1055 Server Lookup Failed melon.rlaprise.net
    1:282/1058 Server Lookup Failed oldhabitsbbs.com
    1:282/1059 Server Lookup Failed templeofsyrinx.info
    1:290/10 Server Lookup Failed bbs.homelabber.net
    1:299/5 Server Lookup Failed alorynavalon.ddns.net
    1:300/6 Server Lookup Failed drac.synchro.net
    1:114/224 Server Lookup Failed bbs.jumpgate.us
    1:114/271 Server Lookup Failed bbs.dbackbbs.com
    1:114/365 Server Lookup Failed kellys.synchro.net
    1:114/464 Server Lookup Failed torchwood-3.dyndns.org
    1:114/501 Server Lookup Failed acme-anvil.darktech.org
    1:114/625 Server Lookup Failed therealmbbs.com
    1:128/3 Server Lookup Failed asgard-bbs.net
    1:310/2 Server Lookup Failed cheyenne.tkware.us
    1:317/2 Server Lookup Failed tbbs.homeip.net
    1:3005/2 Server Lookup Failed f2.n3005.z1.binkp.net
    1:138/389 Server Lookup Failed f389.n138.z1.binkp.net
    1:340/800 Server Lookup Failed catch22bbs.com
    1:340/900 Server Lookup Failed bbs.realms-online.org
    1:340/1100 Server Lookup Failed bbs.neuroflux.online
    1:342/16 Server Lookup Failed jandro1000.no-ip.biz
    1:116/18 Server Lookup Failed os2bbs.org
    1:116/28 Server Lookup Failed magnum.synchro.net
    1:116/60 Server Lookup Failed opendoor.synchro.net
    1:116/102 Server Lookup Failed cartelbbs.keene.co
    1:116/739 Server Lookup Failed am1620.servebbs.net
    1:123/525 Server Lookup Failed alco.bbs.io
    1:123/1970 Server Lookup Failed bbs.midsouth.com
    1:106/324 Server Lookup Failed cyberiabbs.zapto.org
    1:124/5009 Server Lookup Failed FMLYNET.DYNDNS.ORG
    1:130/1015 Server Lookup Failed klonezonebbs.zapto.org

    48 Nodes
    ----- Failed.Txt ends -----

    --- Msged/NT 6.0.1
    * Origin: Somewhere in New Hampshire's White Mountains (1:132/174)
  • From Nick Andre@1:229/426 to Fred Riccio on Friday, October 09, 2020 13:14:14
    On 09 Oct 20 10:13:58, Fred Riccio said the following to All:

    Back in July I posted a list of nodes that could not be directly connected using the information in the NodeList. That list had 41 entries. Now we a up to 48. Does anyone care?

    To be fair, I haven't chased after really any of these things as people go through Covid and job loss and other stuff.

    Nick

    --- Renegade vY2Ka2
    * Origin: Joey, do you like movies about gladiators? (1:229/426)
  • From Andrew Leary@1:320/219 to Fred Riccio on Friday, October 09, 2020 15:04:23
    Hello Fred!

    09 Oct 20 10:13, you wrote to all:

    Back in July I posted a list of nodes that could not be directly
    connected to using the information in the NodeList. That list had 41 entries. Now we are up to 48. Does anyone care?


    ----- Failed.Txt begins -----
    48 Nodes
    ----- Failed.Txt ends -----

    I've noted a similar problem with the few dialup nodes remaining in the nodelist. Even worse, some of the dialup failures are actually answered by a voicemail service, or in 1 case, a human being.

    Andrew

    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: Phoenix BBS * phoenix.bnbbbs.net (1:320/219)
  • From Sean Dennis@1:18/200 to Fred Riccio on Sunday, October 11, 2020 00:21:06
    Fred Riccio wrote to All <=-

    Back in July I posted a list of nodes that could not be
    directly connected to using the information in the
    NodeList. That list had 41 entries. Now we are up to 48.
    Does anyone care?

    It looks like NCs aren't doing their job surprise, surprise. Net 116, the Tennessee Net, is full of deadwood (and that is why I am not part of Net 116 and am a RIN). Heck, I have never seen a message in Fidonet from Danny,
    NC116, in the entire 20+ years I've been in Fidonet.

    I recognize some of those nodes and they have been dead since I was RC11 in
    the early 2000s.

    20+ years of deadwood in the nodelist.

    Welcome to Fidonet, home of the automated BBS.

    Sarcasm--one of the many services I provide to the BBS world ...

    Later,
    Sean
    (tongue planted firmly in cheek)

    ___ MultiMail/Linux v0.52

    --- Maximus/2 3.01
    * Origin: Outpost BBS * bbs.outpostbbs.net:10123 (1:18/200)
  • From Danny Walters@1:116/116 to Sean Dennis on Friday, October 23, 2020 20:29:10
    Sean Dennis said to Fred Riccio:

    Net 116, the Tennessee Net, is full of deadwood (and that is why I
    am not part of Net 116 and am a RIN).

    You were offered a spot but didn't want to change your configs.

    Heck, I have never seen a message in Fidonet from Danny, NC116, in
    the entire 20+ years I've been in Fidonet.

    Doesn't mean I'm not here.

    And I've got some old netmails from when you moved back to your parents' house and were looking for work, so you've seen a message or three.

    And yes, I need to clean up my room.

    -dw

    --- timEd/2 1.10.y2k+
    * Origin: Infinite Rider on the Big Dogma - Nashville, TN (1:116/116)
  • From Sean Dennis@1:18/200 to Danny Walters on Saturday, October 24, 2020 12:09:42
    Hi Danny,

    You were offered a spot but didn't want to change your configs.

    That wasn't the only reason I declined. At the time, there was a possibility of my moving back to Georgia and I wanted not to have to change everything over.

    And I've got some old netmails from when you moved back
    to your parents' house and were looking for work, so
    you've seen a message or three.

    I was wrong. Sorry about that. My memory, as you can tell, is crap.

    And yes, I need to clean up my room.

    You're not the only one and at least you come out and admit it. It's been a while but I checked RC11's segment and there was still deadwood in there from when I was RC11 back in the early 2000s (I had to step down because personal issues at the time). It's the zone nodelist that is full of crap.

    What gets me is people expecting Nick to magically fix all of the problems. It's not his job to deal with the nodelist police; if someone wants to complain to the NCs and RCs to fix their segments (nothing aimed at you; just saying in general), maybe something might get done.

    Later,
    Sean




    --- Maximus/2 3.01
    * Origin: Outpost BBS * bbs.outpostbbs.net:10123 (1:18/200)
  • From Danny Walters@1:116/116 to Sean Dennis on Tuesday, October 27, 2020 12:08:59
    Sean Dennis said to Danny Walters:

    That wasn't the only reason I declined. At the time, there was a possibility of my moving back to Georgia and I wanted not to have
    to change everything over.

    And that's fine, and a good example of good use of regional independents. You were always invited and welcome, but never required.

    I was wrong. Sorry about that. My memory, as you can tell, is
    crap.

    Indeed. I don't post often. There was a brief discussion about BeOS this summer, I posted because I actually had something vaguely relevant to add. You must not have seen that, easy enough to miss. No worries.

    You're not the only one and at least you come out and admit it.

    The part that you nor anyone else is in a position to know is that I have some nodes that tend to drift in and out. I've just left them alone.

    I completely agree that it is administratively untidy to carry around missing nodes. I don't mean this to sound cavalier, but in the big picture a flaky local node isn't hurting anything really. If it were a 1:1/?? node that went mia, that might be a different thing.

    I'll work on it over the weekend.

    if someone wants to complain to the NCs and RCs to fix their
    segments (nothing aimed at you; just saying in general), maybe
    something might get done.

    Well but it was kinda aimed at me.

    -dw


    --- timEd/2 1.10.y2k+
    * Origin: Infinite Rider on the Big Dogma - Nashville, TN (1:116/116)
  • From Carol Shenkenberger@1:275/100 to Nick Andre on Saturday, October 31, 2020 12:02:43
    Re: Re: Nodelist/diff status
    By: Nick Andre to Fred Riccio on Fri Oct 09 2020 01:14 pm

    On 09 Oct 20 10:13:58, Fred Riccio said the following to All:

    Back in July I posted a list of nodes that could not be directly connect using the information in the NodeList. That list had 41 entries. Now w up to 48. Does anyone care?

    To be fair, I haven't chased after really any of these things as people go through Covid and job loss and other stuff.

    Nick


    Same here. A few of mine on that list explictly are NOT CM. 2 are using the computers for telework right now vs BBS.

    xxcarol
    --- SBBSecho 2.11-Win32
    * Origin: SHENK'S EXPRESS TELNET://SHENKS.SYNCHRO.NET (1:275/100)
  • From Carol Shenkenberger@1:275/100 to Sean Dennis on Saturday, October 31, 2020 12:10:32
    Re: Nodelist/diff status
    By: Sean Dennis to Danny Walters on Sat Oct 24 2020 12:09 pm

    Hi Danny,

    You were offered a spot but didn't want to change your configs.

    That wasn't the only reason I declined. At the time, there was a possibilit of my moving back to Georgia and I wanted not to have to change everything over.

    And I've got some old netmails from when you moved back
    to your parents' house and were looking for work, so
    you've seen a message or three.

    I was wrong. Sorry about that. My memory, as you can tell, is crap.

    And yes, I need to clean up my room.

    You're not the only one and at least you come out and admit it. It's been a while but I checked RC11's segment and there was still deadwood in there fro when I was RC11 back in the early 2000s (I had to step down because personal issues at the time). It's the zone nodelist that is full of crap.

    What gets me is people expecting Nick to magically fix all of the problems. It's not his job to deal with the nodelist police; if someone wants to compl to the NCs and RCs to fix their segments (nothing aimed at you; just saying general), maybe something might get done.

    Later,
    Sean





    I think more of us are 'on top of it' than you might think. I do need to fix one CM flag though. He's not CM right now.

    xxcarol
    --- SBBSecho 2.11-Win32
    * Origin: SHENK'S EXPRESS TELNET://SHENKS.SYNCHRO.NET (1:275/100)
  • From Carol Shenkenberger@1:275/100 to Danny Walters on Saturday, October 31, 2020 12:18:15
    Re: Nodelist/diff status
    By: Danny Walters to Sean Dennis on Tue Oct 27 2020 12:08 pm

    Sean Dennis said to Danny Walters:

    That wasn't the only reason I declined. At the time, there was a possibility of my moving back to Georgia and I wanted not to have
    to change everything over.

    And that's fine, and a good example of good use of regional independents. Y were always invited and welcome, but never required.

    I was wrong. Sorry about that. My memory, as you can tell, is
    crap.

    Indeed. I don't post often. There was a brief discussion about BeOS this summer, I posted because I actually had something vaguely relevant to add. Y must not have seen that, easy enough to miss. No worries.

    You're not the only one and at least you come out and admit it.

    The part that you nor anyone else is in a position to know is that I have so nodes that tend to drift in and out. I've just left them alone.

    I completely agree that it is administratively untidy to carry around missin nodes. I don't mean this to sound cavalier, but in the big picture a flaky local node isn't hurting anything really. If it were a 1:1/?? node that wen mia, that might be a different thing.

    I'll work on it over the weekend.

    if someone wants to complain to the NCs and RCs to fix their
    segments (nothing aimed at you; just saying in general), maybe something might get done.

    Well but it was kinda aimed at me.

    -dw


    It's ok Danny.

    2 of my 3 on the list are using the computer for telework (COVID related). The other has been down about 2 weeks but was never CM to start with.

    I'm not about to chop someone off at the knees because their workplace doesn't provide laptops and to telework, they have to provide their own gear.

    xxcarol
    --- SBBSecho 2.11-Win32
    * Origin: SHENK'S EXPRESS TELNET://SHENKS.SYNCHRO.NET (1:275/100)
  • From Fred Riccio@1:132/174 to Carol Shenkenberger on Saturday, October 31, 2020 13:03:58

    31 Oct 20 12:02, Carol Shenkenberger wrote to Nick Andre:


    A few of mine on that list explictly are NOT CM. 2 are
    using the computers for telework right now vs BBS.

    The CM flag has nothing to do with it! The nodes on my list can't be contacted at ANY time, including ZMH. The host name in the NodeList does not return an IP address, making them uncontactable 24 x 7.


    Regards,
    Fred

    --- Msged/NT 6.0.1
    * Origin: Somewhere in New Hampshire's White Mountains (1:132/174)
  • From Dale Shipp@1:261/1466 to Carol Shenkenberger on Sunday, November 01, 2020 01:24:04
    On 10-31-20 12:02, Carol Shenkenberger <=-
    spoke to Nick Andre about Re: Nodelist/diff status <=-

    To be fair, I haven't chased after really any of these things as people go through Covid and job loss and other stuff.

    Nick


    Same here. A few of mine on that list explictly are NOT CM. 2 are
    using the computers for telework right now vs BBS.

    My computer (using windows 10) has a user who manages the BBS and
    another that I use for every thing else. I am retired, not working, but
    even if not my computer could not do zoom type connections -- no video.

    Dale Shipp
    fido_261_1466 (at) verizon (dot) net
    (1:261/1466)



    ... Shipwrecked in Silver Spring, Maryland. 01:27:00, 01 Nov 2020
    ___ Blue Wave/DOS v2.30

    --- Maximus/NT 3.01
    * Origin: Owl's Anchor (1:261/1466)
  • From Carol Shenkenberger@1:275/100 to Fred Riccio on Sunday, November 01, 2020 21:07:53
    Re: Re: Nodelist/diff status
    By: Fred Riccio to Carol Shenkenberger on Sat Oct 31 2020 01:03 pm


    31 Oct 20 12:02, Carol Shenkenberger wrote to Nick Andre:


    A few of mine on that list explictly are NOT CM. 2 are
    using the computers for telework right now vs BBS.

    The CM flag has nothing to do with it! The nodes on my list can't be contac at ANY time, including ZMH. The host name in the NodeList does not return a IP address, making them uncontactable 24 x 7.


    Regards,
    Fred


    Fred, they are offline. rebooted to alternative OS in 2 cases.

    xxarol
    --- SBBSecho 2.11-Win32
    * Origin: SHENK'S EXPRESS TELNET://SHENKS.SYNCHRO.NET (1:275/100)