Hello all.
Pleased to inform you that registration for the SAFNOG-3 meeting, to be
held in Windhoek, Namibia, 8th - 10th August, 2016, is now open.
To register your participation for SAFNOG-3, please visit the link below:
http://www.safnog.org/
Please note that you will be able to view
Hello Tyler,
thanks for your reply.
> Am 28.04.2016 um 17:37 schrieb Tyler Haske :
>
> Martin,
>
>
> > Last but not least: I am also looking for anonymized statistical data about
> > DDoS attacks which I could use in the thesis. I am mainly interested in
> > data about the
> > type of attack
While following that Arista chat... That reminded me of that little
afternoon project years ago.
So I decided to find new hamsters, fire up that VM, refresh the DB's and
from the view point of a tiny 7206VXR/G1 with 2 T3 peers...
The amount of superfluous subnet advertisement drop to ~12
Alain Hebert wrote:
> PS: "Superfluous" is a nice way to say that the best path of a
> subnet is the same as his supernet.
... from the point of view of the paths that you see, which is to say
two egress paths. Someone else on the internet may have a different set
of bgp views which will giv
On 2016-04-29 12:48, Nick Hilliard wrote:
Alain Hebert wrote:
PS: "Superfluous" is a nice way to say that the best path of a
subnet is the same as his supernet.
... from the point of view of the paths that you see, which is to say
two egress paths. Someone else on the internet may have a
Hi
Amplification attacks and syn floods are just touching the surface of ddos
attack vectors. You should look into some industry reports:
Here are a couple examples to get you started.
https://www.radware.com/ert-report-2015/
http://www.verizonenterprise.com/verizon-insights-lab/dbir/2016/
Laszlo Hanyecz wrote:
> I'm curious about specific failure modes that can result from this, if
> anyone can share examples/experience with it.
The canonical pathological case is where the deaggregated prefixes are
affected by upstream topology changes and suddenly your optimisations
which saved yo
Just to be clear, this isn't (to my knowledge) something that Arista is
doing and so the risk described doesn't affect the products that were
discussed on that thread.
On Fri, Apr 29, 2016 at 9:30 AM, Nick Hilliard wrote:
> Laszlo Hanyecz wrote:
> > I'm curious about specific failure modes that
This is an automated weekly mailing describing the state of the Internet
Routing Table as seen from APNIC's router in Japan.
The posting is sent to APOPS, NANOG, AfNOG, AusNOG, SANOG, PacNOG,
SAFNOG, PaNOG, SdNOG, BJNOG, CaribNOG and the RIPE Routing WG.
Daily listings are sent to bgp-st...@lists
Den 29. apr. 2016 15.31 skrev "Nick Hilliard" :
>
> Laszlo Hanyecz wrote:
> > I'm curious about specific failure modes that can result from this, if
> > anyone can share examples/experience with it.
>
> The canonical pathological case is where the deaggregated prefixes are
> affected by upstream to
Baldur Norddahl wrote:
> With two uplinks that is highly unlikely to the point of being impossible.
> There is no topology change upstream that can cause a situation where it is
> not possible to do a high degree of aggregation of the full default free
> routing table before loading it in the FIB.
11 matches
Mail list logo