Hi
I am looking for example routing policies when any AS receiving BGP
advertisement changes Origin AS in BGP AS set attribute to remove the received
AS number and puts its own AS number.[legitimate cases]
1. customer AS advertises the prefix however provider AS announce the
aggregate(super pr
many legitimate cases when Origin AS in BGP announcement
changed by another AS?
To: "Akmal Shahbaz"
Cc: nanog@nanog.org
Date: Tuesday, January 4, 2011, 4:05 PM
On Tue, Jan 04, 2011 at 04:38:19AM -0800,
Akmal Shahbaz wrote
a message of 443 lines which said:
> I am looking for
HiSolutions like BGPmon.net,Cyclops,etc are doing a very good job of alerting
about the prefix hijack/configuration erros/experiments gonig on/etc.But i
would like to ask "Alerting the victim is the best we can do after detecting
such incidents" or what else we can do?What do you think about "B
Respected AllI would like to discuss some of the questions related to BGP
Security which might be quite helpful in my research.1.What are you using now
for BGP Security problems like Prefix hijacking,Path Spoofing,etc?2.What you
would be looking for in any BGP Security Solution?3.Are solutions l
4 matches
Mail list logo
