Re: AIOE server timing out

Franz_aRTiglio <[email protected]> Mon, 30 Jan 2023 18:36:57 +0100
Newsgroups aioe.news.helpdesk
Organization A noiseless patient Spider
Message-ID <[email protected]>
Sembra che noel abbia detto :
> On Mon, 30 Jan 2023 09:32:16 +0000, Muttley wrote:
>
>> 
>> As for 2 servers:
>> 
>> fenris$ ping news.aioe.org PING news.aioe.org (46.165.242.91): 56 data
>> bytes 64 bytes from 46.165.242.91: icmp_seq=0 ttl=49 time=32.022 ms
>> 
>> fenris$ ping nntp.aioe.org PING nntp.aioe.org (46.165.242.75): 56 data
>> bytes Request timeout for icmp_seq 0
>> 
>> Oh wait, you think they're 2 seperate cards in a single machine, right?
>> 
>
>
> We like many service providers have for decades assigned multiple IP's to 
> clients, especially to those who have multiple nics, but only Paolo and 
> leaseweb know his setup, I am surprised it is taking so long to rebuild 
> his array given he doesn't have a huge retention period.

this ^^

also, a "machine" could be a single modem/router with two wan
interfaces that could handle above the "single wan interface"
maximum concurrent connections despite the maximum data
troughtput; as for many high level online database having
multiple wan connections the effective speed/max troughtput is
secondary to the capability to handle multiple concurrent
connections and limit connectivity problems (e.g. during a
DOS attack.