Re: [44net] Lost Packets

You are too kind I block for three years Paul On 11/11/2020 17:59, Marius Petrescu via 44Net wrote: > Just FYI: > > I have have some 550 distinct IP addresses trying to connect from the > internet via tunnel to unavailable ports via my gateway every hour. > > What I do is to place them in a list and blacklist them for 1 hour :-) > > Marius, YO2LOJ > > On 11.11.2020 18:00, Paul Sladen via 44Net wrote: >> On Wed, 11 Nov 2020, G1FEF via 44Net wrote: >>>  From what I have seen logged into the GW machine itself, ... >>> >>> Hopefully the net ops guys at UCSD can ... >> Fundemental problem here (for debugging network issues) is that >> neither ARDC/Amprnet/44Net (...nor CAIDA), have full direct control, >> or access, to their own network instructure. >> >> CAIDA/UCSD is beholden to random upstream filtering as much in 2001[1] >> and 2009[2] as it is now.  And in-turn, AmprGW is/was beholden (2019) >> to an ethernet switch with customised firmware[3]... a blackbox. >> >> Graphs used to show the packet flow for Network Telescope (44net): >> >> https://www.caida.org/data/realtime/telescope/?monitor=telescope_attack&… >> >> >> but those broke (~2019-12-11), giving less insight for debugging. >> >> --------- >> >> ARDC now has the resources to put independently hosted redundancy >> in place for 44net.  Perhaps it would make sense to prioritise AmprGW >> infrastructure over distributions of funds to other organisations? [4] >> >>     -Paul >> >> >> [1] Shannon (2001) >> https://www.caida.org/research/security/code-red/coderedv2_analysis.xml#bac… >> >> "filter was put into place upstream of the monitor, we were unable to >> capture IP packet headers after 16:30 UTC" >> >> [2] Polterock (2012) >> https://blog.caida.org/best_available_data/2012/04/04/targeted-serendipity-… >> >> "increase in the amount of data stored after April 2009 due to the >> removal of an upstream rate limit filter on incoming packets" >> >> [3] Kantor (October 2019) >> "I don't know the make and model of the switch that is crashing. >> I believe it may be running locally-modified firmware." >> >> [4] ie. put a moratorium on the fun "grant giving" side of the >> business, until the primary/core mission of bringing AmprGW >> services under full control has been solved. >> >> >> >> _________________________________________ >> 44Net mailing list >> 44Net(a)mailman.ampr.org >> https://mailman.ampr.org/mailman/listinfo/44net > _________________________________________ > 44Net mailing list > 44Net(a)mailman.ampr.org > https://mailman.ampr.org/mailman/listinfo/44net > > ______________________________________________        This email has > been scanned by Netintelligence http://www.netintelligence.com/email >