| |
I0OJJ > SYSOP 05.03.25 16:33l 40 Lines 1314 Bytes #999 (0) @ WW
BID : 31706I0OJJ
Read: DJ6UX
Subj: Bug at amprgw RIPv2
Path: DB0FHN<DB0RKB<DK0WUE<PD0LPM<PI8ZTM<VK2IO<VK2RZ<ZL2BAU<GB7JD<GB7JED<
GB7CIP<I0OJJ
Sent: 250305/1440z @:I0OJJ.ITA.EU [Rome] $:31706I0OJJ
>From i0ojj@i0ojj.ita.eu Wed Mar 5 15:40:30 2025
Received: from [44.134.109.10] by i0ojj.ampr.org (JNOS2.0p.6) with SMTP
id AA17027320 ; Wed, 05 Mar 2025 15:40:30 +0100
Message-ID: <b3494d3a-b54d-4b4a-a4ef-caa3d810013f@i0ojj.ita.eu>
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
>From: Gustavo Ponza <i0ojj@i0ojj.ita.eu>
Content-Language: en-US
Organization: SICD Rome
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Hi all sysops concerned,
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.
--
73 and ciao, gustavo i0ojj/ir0aab/ir0eq
non multa, sed multum
Read previous mail | Read next mail
| |
