| |
KQ6UP > 44NET 08.03.25 10:33l 33 Lines 908 Bytes #999 (0) @ WW
BID : 5470_KM6JTD
Subj: Re: Bug at amprgw RIPv2
Path: DB0FHN<DB0RKB<DK0WUE<DK0WUE<K7EK<W0ARP<WW4BSA<VE3CGR<VE6NAS<VE2PKT<
VK3AT<N6CTA<KN6YLK<AB6MV<KQ6UP<KM6JTD
Sent: 250307/1845Z @:KM6JTD.#SCA.CA.USA.NOAM #:5470 [Grand Terrace, CA]
From: KQ6UP@KM6JTD.#SCA.CA.USA.NOAM
To : 44NET@WW
>
> Hi all,
>
> this is to inform you that the server amprgw.ampr.org
> at ucsd.edu, as also nowadays, is not able to dispatch
> the ampr routes via RIPv2 broadcasts, in particular
> situations.
>
> That failure is NOT recognizable by ampr nodes having
> a static IP address, instead:
>
> - when occur that nodes having a dynamic IP address
> (as my situation) change their IPs, after that
> portal.ampr.org, recognizes and update the IP change
> (say one hour) the amprgw reacts and synchronize the
> RIP broadcasts again, and all become OK.
>
> - when occur that IP changes for two or more times,
> it happens that, the portal.ampr.org, in some ways
> (say hours) re-synchronize the last (stable) IP
> but the amprgw server definitively stop to send
> the RIP2 broadcasts... until (I think) its reboot.
>
Thanks for the heads up.
-73 de Chris KQ6UP
Read previous mail | Read next mail
| |
