| |
N2NOV > SYSOP 08.07.22 16:36l 21 Lines 804 Bytes #999 (0) @ WW
BID : 6DNP_N2NOV
Read: GAST
Subj: Clearing Erroneous N1URO Aliases From Netrom
Path: DB0FFL<OE2XZR<DB0PM<DB0FHN<DB0BLO<DB0ERF<DB0RES<PI8CDR<GB7YEW<W9GM<
N2NOV
Sent: 220609/1250z @:N2NOV.#RICH.NY.USA.NOAM $:6DNP_N2NOV
>From n2nov@n2nov.ampr.org Thu Jun 9 08:50:14 2022
Received: from n2nov.ampr.org by n2nov.ampr.org (JNOS2.0n.dev) with SMTP
id AA297637 ; Thu, 09 Jun 2022 08:50:14 EDT
Message-Id: <297635@n2nov.ampr.org>
>From: n2nov@n2nov.ampr.org
X-JNOS-User-Port: Telnet (n2nov @ 44.68.41.2) -> Sending message
It has been 5 months since N1URO went SK. There are Netrom aliases for
N1URO showing up in the tables and being broadcast around the network.
Stations like VE2PKT and VE1JOT are reporting that N1URO is connecting
to their systems from 44.88.0.1 and passing along Netrom entries. That
IP address has been reassigned to gw.hamgatect.ampr.org back in April.
If you had/have N1URO in your Netrom routes, please hard code it to zero.
--
73 de N2NOV
n2nov@n2nov.ampr.org
n2nov@n2nov.#rich.ny.usa.noam
Lese vorherige Mail | Lese naechste Mail
| |
