This is exactly the clarification I was looking for. Now I completely got
it I think.
Thanks a lot guys.
Cheers,
2013/3/24 Payam Tarverdyan Chychi pchy...@gmail.com
On 13-03-24 2:08 PM, Payam Tarverdyan Chychi wrote:
Hey,
I'm not sure what the actual exact request from the user was since
Hey,
I suggest grabbing a book on routing and ip fundamentals but here is a basic
overview
You get routs, you install routes, you pass routes... So what does this mean?
Every protocol exchanges routes but before it makes them active it must run
its specific algorithm to ensure best path is
On Sun, Mar 24, 2013 at 8:21 AM, Zehef Poto mpdech...@gmail.com wrote:
I just inherited our backbone. We're a small LIR, we have an AS. The
backbone consists of four MX80 routers, all acting as eBGP edge ones (there
are various IP transit links up and running on all of them). I also use
OSPF
Hi All,
Am 24.03.2013 00:26, schrieb Jeff Wheeler:
Whoever that person is that said something about use next-hop-self
in this context, either you misunderstood them, or you shouldn't
listen to them anymore. That has nothing to do with looking to see if
your router knows about a route.
This
Hey guys,
Thank you all for the very valuable input. Actually yes, Tobias is right,
I'm having this question because of the (quoted by Tobias) e-mail we got
yesterday across several IXPs.
I just don't understand what is to carry a route in my backbone. Am I not
supposed to know all of (or most
Carry a route is the same as accepting a route and having it become active,
allowing traffic to traverse your network to the destination. In this case the
user is asking you to drop the route (attack traffic) at your edge if possible
and not to carry it through your network and deliver it to
Thank you Payam. I think I got what you mean.
In this particular case however, the X/22 route is not a customer or
anything. It is the IXP's peering LAN !
So... It means that the person requested all the IXP's members to
null-route the whole peering LAN ? How can you possibly ask for this ?
I
On 13-03-24 2:08 PM, Payam Tarverdyan Chychi wrote:
Hey,
I'm not sure what the actual exact request from the user was since i
don't really participate much in the AMS-IX anymore ...
maybe the attack was destined towards their actual nei ip on the
exchange (initially i assumed /22 was their
Hey,
I'm not sure what the actual exact request from the user was since i
don't really participate much in the AMS-IX anymore ...
maybe the attack was destined towards their actual nei ip on the
exchange (initially i assumed /22 was their network, sounds like maybe
they meant the /22 that
On 3/24/13 1:24 PM, Zehef Poto wrote:
Thank you Payam. I think I got what you mean.
In this particular case however, the X/22 route is not a customer or
anything. It is the IXP's peering LAN !
So... It means that the person requested all the IXP's members to
null-route the whole peering LAN ?
Hey guys,
The question may seem very noobish and I'm very sorry if that's the case
indeed. I'm kind of junior when it comes to enterprise routing...
I just inherited our backbone. We're a small LIR, we have an AS. The
backbone consists of four MX80 routers, all acting as eBGP edge ones (there
On Sat, Mar 23, 2013 at 5:21 PM, Zehef Poto mpdech...@gmail.com wrote:
I just inherited our backbone. We're a small LIR, we have an AS. The
backbone consists of four MX80 routers, all acting as eBGP edge ones (there
are various IP transit links up and running on all of them). I also use
OSPF
12 matches
Mail list logo
