Добро пожаловать, Гость. Пожалуйста авторизуйтесь здесь.
FGHIGate на GaNJa NeTWoRK ST@Ti0N - Просмотр сообщения в эхоконференции IPV6
Введите FGHI ссылку:


Присутствуют сообщения из эхоконференции IPV6 с датами от 31 Jul 11 14:37:00 до 03 Oct 24 21:46:09, всего сообщений: 7440
Ответить на сообщение К списку сообщений Предыдущее сообщение Следующее сообщение
= Сообщение: 2079 из 7440 ============================================= IPV6 =
От   : Roger Nelson                     1:3828/7           06 Feb 16 17:14:14
Кому : Michiel van der Vlist                               06 Feb 16 17:14:14
Тема : Nodelist
FGHI : area://IPV6?msgid=1:3828/7.0+6b66fa81
На   : area://IPV6?msgid=2:280/5555+56b6352c
= Кодировка сообщения определена как: CP866 ==================================
Ответ: area://IPV6?msgid=2:310/31+56b68f5a
==============================================================================
On Sat Feb-06-2016 19:00, Michiel van der Vlist (2:280/5555) wrote to Roger Nelson:

MvdV> On Saturday February 06 2016 07:20, you wrote to me:

RN> "It" is what I typed on the subject line.  The nodelist is correct.  I
RN> receive a nodediff every Friday.  D'Bridge copies the nodediff to its
RN> own folder and then applies the nodediff to the nodelist and compiles
RN> it.  I keep the nodediffs for the currect year only.  Because I also
RN> use Gerard van Essen's timEd/386 for replying, I use QNODE to create
RN> the NODEX.DAT, NODEX.NDX and SYSOP.NDX files so timEd/386 will be able
RN> to find everything it is looking for.  QNODE runs as a D'Bridge event
RN> every Sunday.

MvdV> Ok. so no problem so far. Didn't expect it really. Golded has
MvdV> itsown nodelist processor. No problem there eiter.

timEd/386 uses the V7 nodelist contained in D'Bridge.  No other is needed.    Thee three small files timEd/386 creates is for lookup.  Does Golded require a propriety nodelist?  It has been many years since I used it and I quit about the time its author was off to university, so I don't recall.

MvdV> The problem with binkp.net is also fixed. f303.n249.z1.binkp.net
MvdV> now has an AAAA record.

Didn't know there was one, but I do now.

MvdV> Ping f303.n249.z1.binkp.net
MvdV> [2607:f2c0:f00e:4200:f9e0:b9ff:6166:c8ef] mit 32 Bytes Daten:

MvdV> Antwort von 2607:f2c0:f00e:4200:f9e0:b9ff:6166:c8ef: Zeit=113ms
MvdV> Antwort von 2607:f2c0:f00e:4200:f9e0:b9ff:6166:c8ef: Zeit=119ms
MvdV> Antwort von 2607:f2c0:f00e:4200:f9e0:b9ff:6166:c8ef: Zeit=113ms
MvdV> Antwort von 2607:f2c0:f00e:4200:f9e0:b9ff:6166:c8ef: Zeit=109ms

MvdV> Ping-Statistik fБr 2607:f2c0:f00e:4200:f9e0:b9ff:6166:c8ef:
MvdV>     Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0 (0%
MvdV> Verlust), Ca. Zeitangaben in Millisek.:
MvdV>     Minimum = 109ms, Maximum = 119ms, Mittelwert = 113ms

Ping f303.n249.z1.binkp.net

Pinging f303.n249.z1.binkp.net [2607:f2c0:f00e:4200:f9e0:b9ff:6166:c8ef] with 32 bytes of data:
Reply from 2607:f2c0:f00e:4200:f9e0:b9ff:6166:c8ef: time=370ms
Reply from 2607:f2c0:f00e:4200:f9e0:b9ff:6166:c8ef: time=366ms
Reply from 2607:f2c0:f00e:4200:f9e0:b9ff:6166:c8ef: time=353ms
Reply from 2607:f2c0:f00e:4200:f9e0:b9ff:6166:c8ef: time=355ms

Ping statistics for 2607:f2c0:f00e:4200:f9e0:b9ff:6166:c8ef:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 353ms, Maximum = 370ms, Average = 361ms


Regards,

Roger
--- timEd/386 1.10.y2k+ Windows 10
* Origin: NCS BBS - Houma, LoUiSiAna - (1:3828/7)

К главной странице гейта
Powered by NoSFeRaTU`s FGHIGate
Открытие страницы: 0.046137 секунды