Login: GUEST @ JH4XSY.13.JNET1.JPN.AS [PM95VU SOK]
home | newest check | boards | help index | log | ps | userlogin | send sysop | slog | status forward | bcm news | users | version | remove cookieI0OJJ > SYSOP 21.04.24 22:27l 39 Lines 1155 Bytes #3 (0) @ WW BID : A48T0_I0OJJ Read: JH4XSY GUEST Subj: Re^2: Update: Use 44.1.1.44 Instead ... Path: JH4XSY<IW0QNL<VE2PKT<I0OJJ Sent: 240421/1321z @:I0OJJ.ITA.EU [Rome] $:A48T0_I0OJJ >From i0ojj@i0ojj.ampr.org Sun Apr 21 15:21:19 2024 Received: from [44.134.32.240] by i0ojj.ampr.org (JNOS2.0o.10dev) with SMTP id AA16994196 ; Sun, 21 Apr 2024 15:21:19 +0200 Message-ID: <78d351fb-55d8-409e-9371-75ce28b00405@i0ojj.ampr.org> MIME-Version: 1.0 User-Agent: Mozilla Thunderbird >From: Gustavo Ponza <i0ojj@i0ojj.ampr.org> Content-Language: en-US Organization: SICD Rome Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit hi all, > The IP 44.1.1.44 is not pingable at all from here :( > The 44.0.0.1 seemed always good from here... so, I can > change ONLY when the 44.1.1.44 will result workable. All is OK now, after routed the new IP towards the linux gateway. The new DNS response is 'one third' with respect the original gateway (i.e.: three times faster): PING 44.0.0.1 (44.0.0.1) 56(84) bytes of data. 64 bytes from 44.0.0.1: icmp_seq=1 ttl=47 time=214 ms PING 44.1.1.44 (44.1.1.44) 56(84) bytes of data. 64 bytes from 44.1.1.44: icmp_seq=1 ttl=48 time=76.0 ms Good catch! TNX to N2NOV for notice and to ARDC developers! -- 73 and ciao, gustavo i0ojj/ir0aab/ir0eq non multa, sed multum
前のメール | 次のメール