Hi all!

Up until Monday I was not having any issues with FE. However, I have
noticed that packets are being scanned out to a "zombie node" that I
do not have configured in my FE setup and was wondering how to go
about tracking down where that node might be set up if it is not set
up in the node book in FE at all?

--- EleBBS/OS2 v20120208.d
* Origin: Neptune's Lair/2 * Olive Branch, MS USA * os2bbs.org (1:116/18)

Hi! Robert,

On 08/04/2017 10:40 PM, you wrote:

Up until Monday I was not having any issues with FE. However, I have noticed that packets are being scanned out to a "zombie node" that I
do not have configured in my FE setup and was wondering how to go
about tracking down where that node might be set up if it is not set
up in the node book in FE at all?

Two possibilities that come immediately to mind: a now-erroneous entry in your 'pack' route file, or, a bad second entry for a node (just under their main address) in the node manager?

Since FE doesn't use the nodelist that may have changed a node's status, then that can't be the source of the error. What you have there is an operator-induced error. ;-)

Cheers,
Paul.

--- Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
* Origin: Quinn's Rock vBox - sunny side up on the bookcase (3:640/1384)

* In a message originally to Robert Wolfe, Paul Quinn said:

220/60
267/155
396/45
Hi! Robert,

On 08/04/2017 10:40 PM, you wrote:

Up until Monday I was not having any issues with FE. However, I have noticed that packets are being scanned out to a "zombie node" that I
do not have configured in my FE setup and was wondering how to go
about tracking down where that node might be set up if it is not set
up in the node book in FE at all?

Two possibilities that come immediately to mind: a now-erroneous entry in your 'pack' route file, or, a bad second entry for a node (just under
their main address) in the node manager?

Since FE doesn't use the nodelist that may have changed a node's status, then that can't be the source of the error. What you have there is an operator-induced error. ;-)

Cheers,
Paul.

--- Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
* Origin: Quinn's Rock vBox - sunny side up on the bookcase (3:640/1384)

Thanks for the info. The ony way I knew about it was because of an
ARChiverr (the archiver that was being called was literally SEA's
ARC). Once I put that in place it looks like the errors stopped and
operation has returned to normal.

--- EleBBS/OS2 v20120208.d
* Origin: Neptune's Lair/2 * Olive Branch, MS USA * os2bbs.org (1:116/18)

On 2017 Aug 04 22:40:00, you wrote to All:

Up until Monday I was not having any issues with FE. However, I have noticed that packets are being scanned out to a "zombie node" that I
do not have configured in my FE setup and was wondering how to go
about tracking down where that node might be set up if it is not set
up in the node book in FE at all?

i can't look at the moment but doesn't FE have a section where it can forward messages to a node number? or am i thinking of somoething in another program?

how are you seeing this manifest itself? in the logs or ???

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... Twits are to Moderators what mosquitoes are to campers..
---
* Origin: (1:3634/12.73)

* In a message originally to Robert Wolfe, mark lewis said:

i can't look at the moment but doesn't FE have a section where it can forward messages to a node number? or am i thinking of somoething in another program?

how are you seeing this manifest itself? in the logs or ???

You may be thinking about netmail forwarding/routing. I am seeing
this in the packing screen when it calls the archiver as well as in
the logs.

But, as I said in an earlier reply, since I installed ARC, the error
messages have gone away and my netmail folder has ceased to fill with error-related netmails. :)

--- EleBBS/OS2 v20120208.d
* Origin: Neptune's Lair/2 * Olive Branch, MS USA * os2bbs.org (1:116/18)