Text 27936, 85 rader
Skriven 2015-09-06 10:10:25 av Eric Renfro (224.fido-fidonews)
  Kommentar till text 27933 av Michiel van der Vlist (2:280/5555)
Ärende: I'd like to know where the news is....
==============================================
  Re: I'd like to know where the news is....
  By: Michiel van der Vlist to Eric Renfro on Sun Sep 06 2015 01:17 pm

 MV> Hello Eric,

 MV> On Sunday September 06 2015 02:39, you wrote to me:

 MV>>> answering on IPv6. If there is, I add the node to the list. That
 MV>>> is how you got in the list. If there is only an answer on IPv4, I
 MV>>> contact the sysop and try to get him to upgrade his system.
 MV>>> Sometimes that works and sometimes it does not. If it works I add
 MV>>> him to the list.

 ER>> Ahhh. Very cool.

 MV> Tnx.

 ER>>>> my current nodelisted entry doesn't have an IPv6 record because
 ER>>>> Synchronet doesn't support IPv6

 MV>>> I noticed. So in tomorrow's list you will be flagged as 6DWN.

 ER>> Hehe. It's only because the NC here hasn't been fixing things when
 ER>> requested, but soon that's going to be changing.

 MV> So if/when that change happens the list will be updated to reflect the new
 MV> situation. My POV on this is that lists like this should be as accurate
 MV> and up to date as possible. No matter what the reason. The actual
 MV> situation is that you have no AAAA record attached to the host name as
 MV> published in the nodelist. 

I totally agree, accuracy is a good thing. 

 MV> However... coming to think of it, I could list you as IPv6 Outgoing Only.
 MV> That would be a new category. Assuming that you can make outgoing IPv6
 MV> calls. Can you?

Yes, I do actually make outbound IPv6 just fine. I receive IPv6 as well, just
not via FidoNet currently due to nodelist being out of date from my specific
needs.

 ER>> So, once that's done and transitioned and updated, I'll be getting
 ER>> my node entry updated once again to include the proper binkp
 ER>> hostname in the nodelist, which /does/ link to the AAAA record
 ER>> because binkd supports IPv6. While the BBS entry only links to the A
 ER>> record. 

 MV> Understood.

 ER>>>>>> however my nodelist entry /currently/ in the nodelist is wrong
 ER>>>>>> (will be fixed in the next 1~2 weeks),

 MV> You seem to have a serious problem. There are only three nodes in net 135
 MV> that answer with a binkp connect. They are 366, 371 and 372. All the
 MV> others - including the host - seem to be MIA. Node 1313 has no listed
 MV> conact information at all, but does not carry the Pvt keyword either. Plus
 MV> that all nodes are listed with all zero telephone numbers which is
 MV> obsolete. The net 135 segment is full of dead wood and the NC does not
 MV> seem to be able to do his job. Even nore: he seems to have left Fidonet.
 MV> It is time for a new NC who can clean up. 

Precisely. Already in delegation for exactly that situation. :) I've already
tracked down 2 people in Net135, communicated with them. There's 2 more that
are on the nodelist that have running BBS's, but seem to be strictly on
auto-pilot and not responding to any communication.

 MV>>> As far as Zones 1, 2 and 3 is concerned that is outdated
 MV>>> information. All three zones distribute a daily updated nodelist
 MV>>> along with the weekly nodelist/nodediff.

 ER>> Hmmmm. This... I was not aware, and will look into this. Are the
 ER>> daily's distributed via file echos?

 MV> Here in zone 2, we have four file echos. First there are the classic
 MV> weekly NODELIST and NODEDIFF echos. Then there are the DAILYLST and
 MV> DAILYUTF echos that distribute a daily nodelist in ASCII and a daily
 MV> nodelist in UTF-8 format. 

Hmmm... Nodelists in UTF-8 format, eh? Nice. It's interesting to see BBS's
starting to support UTF-8, even Synchronet is working on that these days,
getting up to par with current standards.

)))[Psi-Jack -//- Decker]
--- SBBSecho 2.27-Linux
 * Origin: Decker's Heaven -//- bbs.deckersheaven.com (1:135/371)