MAIL TOSSERS
BBS SOFTWARE
TIC PROCESSORS/FILEFIX/SRIF
BBS DOORS/UTILITIES
POINT SOFTWARE
SYSOP MAIL EDITORS
INTERNET UTILITIES
INFORMATIONAL WEBSITES/BBS LISTS
=================================================================
GENERAL ARTICLES =================================================================
PING robot survey, a follow up
By Michiel van der Vlist, 2:280/5555
Eight weeks ago I published a PING robot survey. This is a follow up.
I had hoped that my previous article would encourage sysops to add
PING funtionality to their systems, but so far the result is only
two new PING flags in the nodelist and one sysop who is working on
it.
I have added PING support to my node here thanks to Stas Mishchenkov's Ping Robot for HPT perl.
It replies to Ping and also supports trace. I have it enabled at
1:153/0 and 1:153/757. 1:153/757.2 also replies to Ping from SBBSecho.
It replies to Ping and also supports trace. I have it enabled at
1:153/0 and 1:153/757. 1:153/757.2 also replies to Ping from
SBBSecho.
Great!
Tests are on the way... ;-)
=================================================================
GENERAL ARTICLES
=================================================================
PING robot survey, a follow up
By Michiel van der Vlist, 2:280/5555
Eight weeks ago I published a PING robot survey. This is a follow up.
I had hoped that my previous article would encourage sysops to add
PING funtionality to their systems, but so far the result is only
two new PING flags in the nodelist and one sysop who is working on
it.
I have added PING support to my node here thanks to Stas Mishchenkov's Ping
Robot for HPT perl.
It replies to Ping and also supports trace. I have it enabled at 1:153/0 and 1:153/757. 1:153/757.2 also replies to Ping from SBBSecho.
It replies to Ping and also supports trace. I have it enabled at
1:153/0 and 1:153/757. 1:153/757.2 also replies to Ping from SBBSecho.
I've sent a routed netmail to PING@1:153/757, 2 hours ago. No response yet...
I've sent a routed netmail to PING@1:153/757, 2 hours ago. No
response yet...
I haven't seen anything from your node yet, maybe it took the scenic route?
It replies to Ping and also supports trace. I have it enabled at
1:153/0 and 1:153/757. 1:153/757.2 also replies to Ping from SBBSecho.
I've sent a routed netmail to PING@1:153/757, 2 hours ago. No response yet...
I haven't seen anything from your node yet, maybe it took the scenic route?
I've sent a routed netmail to PING@1:153/757, 2 hours ago. No
response yet...
I haven't seen anything from your node yet, maybe it took the scenic route?
It was routed via 1:229/101. After that I don't know where it will go. I haven't seen any Trace responses either.
I just received two pongs, from 1:153/757 and from 1:153/757.2. But we have a very short path. :)
However, no reply from a ping to 1:153/0 yet...
It was routed via 1:229/101. After that I don't know where it will
go.
I haven't seen any Trace responses either.
I just polled 1:229/101 and picked up a netmail from January!
But still nothing from your node.
Maybe try 1:153/7715, 2:221/6 or 3:770/1. I think you'll get a quick response via those nodes.
The point of the PING messages is to find routing problems, so I'm not going to route around the problems! ;)
I mostly use crash mails when I need to be sure a netmail is delivered, any way! ;)
However, no reply from a ping to 1:153/0 yet...
1:153/7715 used to fly 1:153/0. I wonder if that AKA is still in his config.
I will ask him to check what happens to mail for 153/0 there.
The point of the PING messages is to find routing problems, so I'm
not going to route around the problems! ;)
OK, I hope you will get a reply before too long.
The point of the PING messages is to find routing problems, so I'm
not going to route around the problems! ;)
OK, I hope you will get a reply before too long.
Maybe I'll try a crashmail to PING on your system, so we know how the route
back goes.
I had hoped that my previous article would encourage sysops to add
PING funtionality to their systems, but so far the result is only
two new PING flags in the nodelist and one sysop who is working on
it.
My BBS, Imzadi Box 2:240/5824, also supports PING mails and should respond correctly.
The thing with a nodelist update for my system is ... not so easy, I don't know if/when the change could be applied.
My BBS, Imzadi Box 2:240/5824, also supports PING mails and should
respond correctly.
The thing with a nodelist update for my system is ... not so easy, I
don't know if/when the change could be applied.
My BBS, Imzadi Box 2:240/5824, also supports PING mails and should
respond correctly.
Test is on it's way...
My BBS, Imzadi Box 2:240/5824, also supports PING mails and should
respond correctly.
Test is on it's way...
Which was 3 hours ago, but I haven't received a response. :-(
+ 16 Apr 16:40:07 [10791] sending /home/fido/outbound.001/079a1c40.pkt as 079a1c40.pkt (388)
+ 16 Apr 16:40:07 [10791] sent: /home/fido/outbound.001/079a1c40.pkt (388, 388.00 CPS, 1:153/757@fidonet)
A response hasn't arrrived yet...
A response hasn't arrrived yet...
I did get that message, Ping replied and packed that reply to
153/7715. I was thinking but I could be wrong that Dallas had a fairly direct route to net 280.
+ 16 Apr 16:40:07 [10791] sending
/home/fido/outbound.001/079a1c40.pkt
as 079a1c40.pkt (388) + 16 Apr 16:40:07 [10791] sent:
/home/fido/outbound.001/079a1c40.pkt (388, 388.00 CPS,
1:153/757@fidonet)
A response hasn't arrrived yet...
I did get that message, Ping replied and packed that reply to 153/7715. I was thinking but I could be wrong that Dallas had a fairly direct route to net 280.
I have changed the route for net 280 to go via 2:221/6 as most traffic
for zone 2 goes. Can you try again?
A response hasn't arrrived yet...
I did get that message, Ping replied and packed that reply to
153/7715. I was thinking but I could be wrong that Dallas had a fairly
direct route to net 280.
I have changed the route for net 280 to go via 2:221/6 as most
traffic for zone 2 goes. Can you try again?
I have a link with Tommy at 2:221/1, so that will probably work. I just sent another crashmail to your PING.
I've sent a routed netmail to PING@1:153/757, 2 hours ago. No response yet...
Maybe I'll try a crashmail to PING on your system, so we know how the route back goes. Do you have a direct connection with Nick BTW? If not it would be interesting if you ping'ed his system...
My BBS, Imzadi Box 2:240/5824, also supports PING mails and should respond correctly.
I guess most Synchronet BBSes do support it as I don't remember having to enable it somehow :)
The thing with a nodelist update for my system is ... not so easy, I don't know if/when the change could be applied.
He does, he has a direct link with me. I got your PINg responze via that link. So I wonder why he does not use that link to route all mail for net 280 to me...
A response to that one arrived here quite fast:
========================================================================== =====
From : Ping Robot 1:153/757 2021-04-16 15:40:52
To : Wilfred van Velzen 2:280/464
Subj : Pong ========================================================================== ===== @INTL 2:280/464 1:153/757
@MSGID: 1:153/757 607a1275
@TID: hpt/lnx 1.9.0-cur 2021-03-14
Hi Wilfred van Velzen.
Your ping-message was received by my system on Fri Apr 16 15:40:53 2021
Orignal message: ========================================================================== == From: Wilfred van Velzen 2:280/464 17 Apr 21 00:40:32
To : PING 1:153/757
Subj: Crashmail ping test to 1:153/757 ==========================================================================
@Via 1:153/757 @20210416.224053.UTC hpt/lnx 1.9.0-cur 2021-03-14
@Via 2:221/6 @20210416.224117.UTC hpt/lnx 1.9.0-cur 2021-04-15
@Via 2:280/5555 @20210416.224131.432.UTC FMail-W32(Toss) 2.1.3.7-B20170919 @Via 2:280/5555 @20210416.224131.495.UTC FMail-W32(Pack) 2.1.3.7-B20170919 @Via 2:280/464 @20210416.224219.082.UTC FMail-lnx64(Toss)
Where are the days that a reply within the week was considered OK.
I've sent a routed netmail to PING@1:153/757, 2 hours ago. No response
yet...
Where are the days that a reply within the week was considered OK.
I just sent a ping to your node. I have received a couple trace replies so it is heading your way. I'll let you know when I get a reply.
But I didn't?
So where did he route the netmail for me? And why didn't it arrive
here... Mysteries... :-(
That was pre-MXMXI. Welcome to MMXXI! Please adjust your PLayboy calendar.
That was pre-MXMXI. Welcome to MMXXI! Please adjust your PLayboy calendar.I think you need to freshen up on your Roman numerals.
Early Playboy calendars were way better, real tits ... not photoshopped. (sorry ladies for my language)
Maybe I'll try a crashmail to PING on your system, so we know how the
route back goes. Do you have a direct connection with Nick BTW? If
not it would be interesting if you ping'ed his system...
Yes, I am linked at 229/101 and 229/426 so either should work.
@Via 1:153/757 @20210416.224053.UTC hpt/lnx 1.9.0-cur 2021-03-14
@Via 2:221/6 @20210416.224117.UTC hpt/lnx 1.9.0-cur 2021-04-15
@Via 2:280/5555 @20210416.224131.432.UTC FMail-W32(Toss)
2.1.3.7-B20170919 @Via 2:280/5555 @20210416.224131.495.UTC
FMail-W32(Pack) 2.1.3.7-B20170919 @Via 2:280/464
@20210416.224219.082.UTC FMail-lnx64(Toss)
That looks much better.. :)
I routed to 229/101 for the PING test, so if you didn't get it from him, I think we found the problem... :-(
Yes, but now you are routing around the problem, instead of trying to get it fixed... :-/
I routed to 229/101 for the PING test, so if you didn't get it from
him, I think we found the problem... :-(
Yes, I think that is a problem. I'll netmail Frank and ask him to check our
link.
I just finished a ping robot that *should* be working with sbbsecho if
you want to test - ping@1:342/17
I had hoped that my previous article would encourage sysops to add
PING funtionality to their systems, but so far the result is only
two new PING flags in the nodelist and one sysop who is working on
it.
I just finished a ping robot that *should* be working with sbbsecho if you want to test - ping@1:342/17
Test on the way...
Cheers, Michiel--- SBBSecho 3.11-Linux
I think you need to freshen up on your Roman numerals.
Getting your attention was the aim.
It works nicely on a (Ubuntu) calculator.
Cool. I'll try to watch the logs for it.
That was pre-MXMXI. Welcome to MMXXI! Please adjust your PLayboy
calendar.
I think you need to freshen up on your Roman numerals.
Early Playboy calendars were way better, real tits ... not photoshopped. (sorry ladies for my language)
It works nicely on a (Ubuntu) calculator.
A good reason not to use it. It's wrong.
Do you have Dutch ancestry?
The thing with a nodelist update for my system is ... not so easy, I
don't know if/when the change could be applied.
Just write a netmail to Torsten Bamberg to the effect that you want the PING flag added to your listing. That is what NCs are for. ;-)
My BBS, Imzadi Box 2:240/5824, also supports PING mails and should ACN>>> respond correctly.
Test is on it's way...
Which was 3 hours ago, but I haven't received a response. :-(
Btw: I've now also tried crash, and got this:
+ 16 Apr 21:13:18 [26562] call to 2:240/5824@fidonet
16 Apr 21:13:18 [26562] trying box.imzadi.de [2001:470:540b:0:f1d0:2:240:5824]... ? 16 Apr 21:15:25 [26562] connection to 2:240/5824@fidonet failed: Connection timed out 16 Apr 21:15:25 [26562] trying box.imzadi.de [217.81.92.195]:24554... 16 Apr 21:15:25 [26562] connected + 16 Apr 21:15:25 [26562] outgoing session with box.imzadi.de:24554 [217.81.92.195] ...
So there is something wrong with your IPv6 inbound, so it seems...
Actually from the Province of Zeeland. Don't know if it really qualifies.
My BBS, Imzadi Box 2:240/5824, also supports PING mails and should
respond correctly.
Test is on it's way...
Which was 3 hours ago, but I haven't received a response. :-(
Did you get a response now?
Btw: I've now also tried crash, and got this:
+ 16 Apr 21:13:18 [26562] call to 2:240/5824@fidonet
16 Apr 21:13:18 [26562] trying box.imzadi.de
[2001:470:540b:0:f1d0:2:240:5824]... ? 16 Apr 21:15:25 [26562]
connection to 2:240/5824@fidonet failed: Connection timed out 16 Apr
21:15:25 [26562] trying box.imzadi.de [217.81.92.195]:24554... 16
Apr 21:15:25 [26562] connected + 16 Apr 21:15:25 [26562] outgoing
session with box.imzadi.de:24554 [217.81.92.195] ...
So there is something wrong with your IPv6 inbound, so it seems...
Thank you for the information!
It should now work again. But I don't really know what the problem was... After a reboot of the BBS, it is working again?!?
I did get that message, Ping replied and packed that reply to
153/7715. I was thinking but I could be wrong that Dallas had a
fairly direct route to net 280.
He does, he has a direct link with me. I got your PINg responze via
that link. So I wonder why he does not use that link to route all mail
for net 280 to me...
So there is something wrong with your IPv6 inbound, so it
seems...
Thank you for the information!
It should now work again. But I don't really know what the problem
was... After a reboot of the BBS, it is working again?!?
He does, he has a direct link with me. I got your PINg responze via
that link. So I wonder why he does not use that link to route all
mail for net 280 to me...
I did ask Dallas about that and he told me he routes mail for zone 2 via 261/38, Nick Andre.
I'm not sure if that means he is routing via Janis 1:261/38 or Nick 1:229/426. If he did route Wilfred's reply via 229/426 it may be on hold there for Wilfred, but I have no way to know.
It should now work again. But I don't really know what the problem
was... After a reboot of the BBS, it is working again?!?
It was working 2 minutes earlier... ;)
It was working 2 minutes earlier... ;)
Actually from the Province of Zeeland. Don't know if it really
qualifies.
Yes. You feel at home on the roiling deck of seagoing craft.
I did ask Dallas about that and he told me he routes mail for zone 2 via 261/38, Nick Andre.
I'm certain Nick Andre will be delighted to find that out.
I'm certain Nick Andre will be delighted to find that out.
I'm sure he is aware.
I'm not sure if that means he is routing via Janis 1:261/38 or Nick 1:229/4 If he did route Wilfred's reply via 229/426 it may be on hold there for Wilfred, but I have no way to know.
why anyone would use Janis's unreliable Linux BBBS bullshit is beyond explanation.
If she couldn't produce a nodelist on time or with the right segments, what makes anyone think she can route Netmail.
If she couldn't produce a nodelist on time or with the right segments, what makes anyone think she can route Netmail.
Janis has proved to be a reliable link year after year. Echomail netmail/files, no issues.
It should now work again. But I don't really know what the problem
was... After a reboot of the BBS, it is working again?!?
Nope.It was working 2 minutes earlier... ;)
[...]Did you get a response now?
No, and I tried it again with a crashmail to your system. Which also didn't get a response so far:
Did your system proces it? And where did it route the answer to?
Eh, that's weird. And now, after another reboot, it is working
again?!? There might be a problem in the IPv6 part of my BBS setup,
but I don't know what is happening there. A simple restart of the Synchronet services did not resolve it, but a reboot did.
I've looked in my Synchronet log file and found your call.
Also, just some seconds later, an outgoing call was initiated - and I guess, your answer was sent this way:
18:44:07 BINKP Remote addresses: 2:280/464@fidonet 39:39/0@amiganet 18:44:07 BINKP Receiving file: /sbbs/temp/07b0fd60.pkt (0.4KB)
18:44:07 BINKP Received file: /sbbs/temp/07b0fd60.pkt (0.4KB)
18:44:07 BINKP Non-secure session type: 'non-secure'
18:44:07 BINKP Moving '/sbbs/temp/07b0fd60.pkt' to '../fido/nonsecure/ 07b0fd60.pkt'.
18:44:11 DAILY Semaphore signaled for Timed Event: FIDOIN
18:44:11 FIDOIN Running native timed event: FIDOIN
18:44:11 FIDOIN Timed event: FIDOIN returned 0
18:44:15 DAILY Semaphore signaled for Timed Event: BINKOUT
18:44:15 BINKOUT Running timed event: BINKOUT
18:44:15 BINKOUT BinkIT/2.39 invoked with options:
18:44:15 BINKOUT Attempting callout for 2:240/5832@fidonet, file: /sbbs/ fido/outbound/00f016c8.out
18:44:15 BINKOUT JSBinkP/1.123 callout to 2:240/5832@fidonet started 18:44:15 BINKOUT Connecting to 2:240/5832@fidonet at bamberg-ot.de:24554
Please defend her some more, I smell zone 2 making popcorn.
Please defend her some more, I smell zone 2 making popcorn.
That wast spicy. Send more, over... Bacon, beans & eggs on the barbie her
If you're a Janis disciple you likely would get "reliable" service.
But she couldn't produce a reliable nodelist. Region 12 stuff would change almost weekly, randomly, for no reason. Date/time stamps of nodelists was sometimes not consistant. This is old news that can be verified by many here.
If she could not manage to produce a silly nodelist reliably and accurately, then routed Netmail at her system cannot be trusted. Period.
Please defend her some more, I smell zone 2 making popcorn.
Please defend her some more, I smell zone 2 making popcorn.
That wast spicy. Send more, over... Bacon, beans & eggs on thebarbie her
What if I want the food first?
why anyone would use Janis's unreliable Linux BBBS bullshit is beyond
explanation.
BBBS may not be for everyone, but it is reliable.
If she couldn't produce a nodelist on time or with the right segments,
what makes anyone think she can route Netmail.
Janis has proved to be a reliable link year after year. Echomail/netmail/files
no issues.
If she could not manage to produce a silly nodelist reliably and accurately, then routed Netmail at her system cannot be trusted. Perio
Producing a nodelist != routing mail.
Janis doesn't need my defense. She has a good track record of reliable service. I hope that zone 2 and all zones for that matter have all the popc they want/need. Hot and buttered.
The reason I did not send him my original script to create nodelist/nodedif was because I figured he was running windows or DOS, and nothing in my scri would have made sense to him. He'd be better off rewriting the entire thin from scratch.. I DID send him all the DOS batch files that I were sent to m by my predecessor. Nick never seems to mention that, oh well.
The reason I did not send him my original script to create nodelist/nodediffs was because I figured he was running windows or DOS,
and nothing in my script would have made sense to him.
BTW this is the script I used to generate nodelists for all the years I
was Z1C. Worked perfectly.
Eh, that's weird. And now, after another reboot, it is working
again?!? There might be a problem in the IPv6 part of my BBS setup,
but I don't know what is happening there. A simple restart of the
Synchronet services did not resolve it, but a reboot did.
He does, he has a direct link with me. I got your PINg responze
via that link. So I wonder why he does not use that link to route
all mail for net 280 to me...
I did ask Dallas about that and he told me he routes mail for zone 2
via 261/38, Nick Andre.
I'm not sure if that means he is routing via Janis 1:261/38 or Nick 1:229/426. If he did route Wilfred's reply via 229/426 it may be on
hold there for Wilfred, but I have no way to know.
I have more confidence in Tommi so I will route mail for net 280 (and
zone 2, for the most part) that way and since 153/7715 is working for
your node I'll keep routing 280/5555 to 153/7715.
I also asked Dallas about mail for 153/0 and he seemed to think mail
for 153/0 was on hold for my node. I poll 153/7715 several times a day
and I have not seen that message. I hope that Dallas has eyes on that
and will get mail I need to see to me.
think it had something to do with wildcards in MAKENL under Linux and how they are interpreted and resolved.
Today, it failed again. I did some reconfiguration in my router and
hope that this is helping a little longer now :)
It should work anyway. Wilfred has a direct link with Nick and I have direct links with both Janis and Nick. And even if Nick or Janis do not directly route to R28, their default route is via Ward and R28 has multiple direct links with Ward.
I would say, that if mail routed via Dallas does not reach R28, there is a problem at Dallas' end.
I have more confidence in Tommi so I will route mail for net 280
(and zone 2, for the most part) that way and since 153/7715 is
working for your node I'll keep routing 280/5555 to 153/7715.
That is fine with me, but doesn't solve the other problems at Dallas' end.
Dallas is your RC, so the two of you are responsible for that part of the smmooth operation of the network...
think it had something to do with wildcards in MAKENL under Linux
and how they are interpreted and resolved.
The way you use wildcards in Makenl, does not work on *nix system.
The quick solution is to remove all region updates from the master directory, ...
I tried to explain this to Janis, but I failed.
Nothing yet...
I saw two ping netmails from you come through here today, though they
both hit just before I had full logging back up. Looks like at least
one was destined for 2:280/something though? Did they get where you
wanted them, and how did you route them?
It should work anyway. Wilfred has a direct link with Nick and I have direc links with both Janis and Nick. And even if Nick or Janis do not directly
I sent several. One crash and some routed. I dod not see the VIAs in
the routed ones. They probably went via 1:153/7715. I send another one
via 1:320/219
If fries are not your thing, try the poutine!
I've had that. Once. By mistake. In Montreal.
Poutine is not for everyone. I don't care for it.
If my lady friends see's poutine on the menu she orders it if she is hungry
or not.
Sysop: | Eric Oulashin |
---|---|
Location: | Beaverton, Oregon, USA |
Users: | 91 |
Nodes: | 16 (1 / 15) |
Uptime: | 22:25:06 |
Calls: | 3,607 |
Calls today: | 7 |
Files: | 8,468 |
Messages: | 337,054 |