12 Nov
2020
12 Nov
'20
9:19 p.m.
Marius,
Bluntness is fine. Coming from the old days of packet, I find that my skin is still
pretty thick.
Understand that I've been out of this for a while. And I'm seeing that what you
say makes sense. I have a BGP provider that will advertise my route, but the standard for
advertising a subnet via BGP is no less than /24. I'm waiting to hear back from Chris
on expanding my allocation from /27 to /24.
Thanks,
73's
-Albert
WB7AWL
-----Original Message-----
From: 44Net [mailto:44net-bounces+wb7awl=lawsonpc.com@mailman.ampr.org] On Behalf Of
Marius Petrescu via 44Net
Sent: Thursday, November 12, 2020 11:13 AM
To: 44net(a)mailman.ampr.org
Cc: Marius Petrescu <marius(a)yo2loj.ro>
Subject: Re: [44net] Lost Packets
This may sound blunt, but why do you need to run DMR traffic from/to the internet via
44net if you don't have a BGP announced subnet?
Using your public IP for it (since you have a gateway, otherwise you would not need
ampr-gw) would actually circumvent all those problems related to the gateway.
Also, your partners would experience a round trip time cut in half by connecting directly
to you or you connecting to them via public IP instead of the
client<->ampr-gw<->client option.
And if they also use 44net, then again the gateway should not matter, since all tunnels
are full mesh.
The AMPR tunneling system is for interlinking isolated subnets and the gateway itself to
provide management and occasional internet access, not for providing high speed high
performance routing, like those needed for DV traffic.
Talking of sustainability, you use the gateway for something it was not meant to support,
not mentioning the contribution to clogging the ampr-gw router itself.
Marius, YO2LOJ
On 12.11.2020 07:15, Albert Lawson via 44Net wrote:
Dan,
Please keep us posted on USCD's response. I'm experiencing a 30% packet loss to
the gateway tonight and that's not acceptable. I don't want to make waves or
cause trouble....but this is not sustainable. The packet loss started again tonight
around 5PM (PST) and has so far made a complete mess of two of our DMR nets.
73's
-Albert
WB7AWL
-----Original Message-----
From: 44Net
[mailto:44net-bounces+wb7awl=lawsonpc.com@mailman.ampr.org] On Behalf
Of Daniel E Andersen via 44Net
Sent: Wednesday, November 11, 2020 9:06 PM
To: 44net(a)mailman.ampr.org
Cc: Daniel E Andersen <dea(a)caida.org>
Subject: Re: [44net] Lost Packets
On 11/11/20 8:00 AM, Paul Sladen via 44Net wrote:
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
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.
I can answer this part, at least. The make and model is a juniper ex3300-48t. It
is not running any customized firmware. Rather, the link drops down into a small vlan
grouping with the link from UCSD, a link to the ampr gw box, and a port replicator. For
whatever reason, when the ampr gw box reboots, there is a chance it takes the switch with
it. usually, the switch just reboots, but sometimes it full on crashes and needs a power
cycle.
It has been pretty stable recently, however.
Last flapped : 2019-10-18 01:34:48 PDT (55w5d 08:34 ago)
( on all three ports )
In other news, I'm still waiting to hear back from UCSD. Keep in mind it is a
holiday here, so it may be tomorrow.
Dan
_________________________________________
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