Long time I had the same opinion, however, if someone operates a network
with multiple upstream providers the operator should be able to afford a
proper out of band console access which solves this issue completely.
I would only accept a default route on Uplinks where I am only receiving
a par
On Tue, Nov 4, 2014 at 12:47 PM, Berry Mobley wrote:
> I'm wondering how many of you who are multihomed
> also add default routes pointing to your providers
> from whom you are receiving full feeds.
>
> If so, why? If not, why not?
Back when I worked for the DNC we ran into a problem with the TCA
> On Nov 4, 2014, at 10:49 PM, Andreas Larsen wrote:
>
> There is one setup where you would need default route from your provider.
That may be true, but this isn’t it…
> If you have no IBGP between two sites and your prefix is a large /16 on side
> and maybe a /18 from that /16 on another si
nanog@nanog.org
Subject: Re: Default routes on BGP routers with full feeds
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Nov 5, 2014, at 7:49 AM, Andreas Larsen wrote:
There is one setup where you would need default route from your provider.
If you have no IBGP between two sites and your pr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Nov 5, 2014, at 7:49 AM, Andreas Larsen wrote:
There is one setup where you would need default route from your provider.
If you have no IBGP between two sites and your prefix is a large /16 on side
and maybe a /18 from that /16 on another site.
There is one setup where you would need default route from your provider.
If you have no IBGP between two sites and your prefix is a large /16 on side
and maybe a /18 from that /16 on another site. These site would not be able to
talk to each other if you orginate from the same AS.
Other than t
On Tuesday, November 04, 2014 07:47:21 PM Berry Mobley
wrote:
> I'm wondering how many of you who are multihomed also add
> default routes pointing to your providers from whom you
> are receiving full feeds.
>
> If so, why? If not, why not?
We filter out default routes from our upstreams, but m
We don't accept a default from anyone, but will send one to a customer when
specifically requested.
We heavily filter all incoming routes (bogon, 1918, and many others). We
don't want data resorting to 0/0 and ::/0 when we specifically rejected the
matching route at the import policy.
Additionall
It seems in such a case, the traffic still doesn’t know where to go, but you
don’t realize it because you have a default.
Then you pass the traffic to one of the providers who doesn’t have a route for
it and they drop it instead of you.
If you see something different, then, by definition, said
Usually, when this is done, it is an adjunct to providing connectivity fast
while the table is loading on a connection reset.
Owen
> On Nov 4, 2014, at 9:47 AM, Berry Mobley wrote:
>
> I'm wondering how many of you who are multihomed also add default routes
> pointing to your providers from w
On Tue, Nov 4, 2014 at 12:47 PM, Berry Mobley wrote:
> I'm wondering how many of you who are
> multihomed also add default routes pointing
> to your providers from whom you are receiving full feeds.
Back when I was in the ISP world I installed a default route pointing to a
data capture machine. T
> On Nov 4, 2014, at 1:25 PM, Mike Walter wrote:
>
> I have 5 providers and we get the default from all of them and full routing
> tables.
>
> I have seen cases where if there is no default route, the traffic didn't know
> where to go, even with full routes from all my providers.
We put so
I can tell you that I do not do that. Typically if my BGP connectivity to a
carrier fails I would prefer we don't route anything their way until we get
that resolved because it might indicate a circuit that is up but unable to pass
traffic (very common with carrier Ethernet especially). It doe
I have 5 providers and we get the default from all of them and full routing
tables.
I have seen cases where if there is no default route, the traffic didn't know
where to go, even with full routes from all my providers.
-Mike
-Original Message-
From: NANOG [mailto:nanog-boun...@nanog
I often opt to leave one or more default routes configured with low
priority (lower than BGP). The thinking is that if there is a fault with
BGP, the router will still operate and the fault can be corrected
remotely (in-band). The downside is that I might pass traffic for
non-existing destinati
15 matches
Mail list logo
