2 Nov
2012
2 Nov
'12
9:56 a.m.
Hey All
Quick question: do you allow/run routing protocols between your (isp-)
network and your customer?
If so: which protocols?
If not: what reasons do you tell the customer?
In particular I am interested to know about setups when they want to
announce the prefix/subnet you assigned them from your PA-space back to
you because they want to run redundant routers.
The setup would probably look like this:
Customer Subnet 10.0.0.0/27
/ \
| |
[customer router a] - <routing protocol x> - [customer router b]
| |
<routing protocol y> <routing protocol y>
| |
[isp router a] - <routing protocol z> - [isp router b]
| |
\ /
ISP Network 10.0.0.0/8
--
Best regards,
Roman Hochuli
Operations Manager
nexellent ag
Saegereistrasse 33
CH-8152 Glattbrugg
Phone: +41 44 872 20 00
Fax: +41 44 872 20 01
URL: www.nexellent.ch
X-NCC-RegID: ch.nexellent
Imagination is the one weapon in the war
against reality.
-- Jules de Gaultier
2 Nov
2 Nov
10:21 a.m.
hi Roman,
I would propose BGP on CE-PE link, with some BGP community policy.
Then the customer would send you community strings which govern
local preference and announcements of those prefixes.
I made several such policy implementations based on Easynet BGP policy:
http://lg.easynet.net/bgppolicy.php
This is a very detailed document, and it covers all possible needs for an SP.
Typically you only need to implement a part of it.
cheers,
stan
----- Original Message -----
From: Roman Hochuli
<roman.hochuli(a)nexellent.ch>
To: "swinog(a)swinog.ch" <swinog(a)swinog.ch>
Cc:
Sent: Friday, November 2, 2012 9:56 AM
Subject: [swinog] routing protocols between isp and customer?
Hey All
Quick question: do you allow/run routing protocols between your (isp-)
network and your customer?
If so: which protocols?
If not: what reasons do you tell the customer?
In particular I am interested to know about setups when they want to
announce the prefix/subnet you assigned them from your PA-space back to
you because they want to run redundant routers.
The setup would probably look like this:
Customer Subnet 10.0.0.0/27
/ \
| |
[customer router a] - <routing protocol x> - [customer router b]
| |
<routing protocol y> <routing protocol y>
| |
[isp router a] - <routing protocol z> - [isp router b]
| |
\ /
ISP Network 10.0.0.0/8
--
Best regards,
Roman Hochuli
Operations Manager
nexellent ag
Saegereistrasse 33
CH-8152 Glattbrugg
Phone: +41 44 872 20 00
Fax: +41 44 872 20 01
URL: www.nexellent.ch
X-NCC-RegID: ch.nexellent
Imagination is the one weapon in the war
against reality.
-- Jules de Gaultier
_______________________________________________
swinog mailing list
swinog(a)lists.swinog.ch
http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
11:41 a.m.
Hello Stan
I would propose BGP on CE-PE link, with some BGP
community policy.
As far as I understand this document is talking about bgp-setups as a
whole. I would be more interested to hear if they would break out a
subnet out of their PA-allocation and accept that back over <insert
routing protocol of choice here> from their customer.
--
Best regards,
Roman Hochuli
Operations Manager
nexellent ag
Saegereistrasse 33
CH-8152 Glattbrugg
Phone: +41 44 872 20 00
Fax: +41 44 872 20 01
URL: www.nexellent.ch
X-NCC-RegID: ch.nexellent
Imagination is the one weapon in the war
against reality.
-- Jules de Gaultier
11:48 a.m.
On 2012-11-02 11:41, Roman Hochuli wrote:
Hello Stan
I've seen that kind of setup (give a chunk of PA to customer, let
customer announce it to the ISP in question so that customer can be
multihomed)) in various places. The choice of routing protocol just
depends on what devices are connected to either side. The preference for
it then typically is OSPF, BGP and last RIP and friends.
Greets,
Jeroen
I would propose BGP on CE-PE link, with some BGP
community policy.
As far as I understand this document is talking about bgp-setups as a
whole. I would be more interested to hear if they would break out a
subnet out of their PA-allocation and accept that back over <insert
routing protocol of choice here> from their customer.
1:31 p.m.
sure, they announce a part of your PA superblock, and you route it in internal BGP, and
just make sure you don't announce longer prefixes to the outside world. And this
community concept is actually helping to do this in an efficient manner.
Pretty much everyone is doing that.
----- Original Message -----
From: Roman Hochuli
<roman.hochuli(a)nexellent.ch>
To: swinog(a)lists.swinog.ch
Cc:
Sent: Friday, November 2, 2012 11:41 AM
Subject: Re: [swinog] routing protocols between isp and customer?
Hello Stan
I would propose BGP on CE-PE link, with some BGP
community policy.
As far as I understand this document is talking about bgp-setups as a
whole. I would be more interested to hear if they would break out a
subnet out of their PA-allocation and accept that back over <insert
routing protocol of choice here> from their customer.
--
Best regards,
Roman Hochuli
Operations Manager
nexellent ag
Saegereistrasse 33
CH-8152 Glattbrugg
Phone: +41 44 872 20 00
Fax: +41 44 872 20 01
URL: www.nexellent.ch
X-NCC-RegID: ch.nexellent
Imagination is the one weapon in the war
against reality.
-- Jules de Gaultier
_______________________________________________
swinog mailing list
swinog(a)lists.swinog.ch
http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
10:57 a.m.
Hi Roman,
Most ISPs would use BGP and typically it would look like this:
ISP-----iBGP_AS100-----ISP
| |
| |
eBGP eBGP
| |
| |
CSR--iBGP_AS65532--CSR
Regards,
Fadi
On Fri, Nov 2, 2012 at 9:56 AM, Roman Hochuli <roman.hochuli(a)nexellent.ch>wrote;wrote:
Hey All
Quick question: do you allow/run routing protocols between your (isp-)
network and your customer?
If so: which protocols?
If not: what reasons do you tell the customer?
In particular I am interested to know about setups when they want to
announce the prefix/subnet you assigned them from your PA-space back to
you because they want to run redundant routers.
The setup would probably look like this:
Customer Subnet 10.0.0.0/27
/ \
| |
[customer router a] - <routing protocol x> - [customer router b]
| |
<routing protocol y> <routing protocol y>
| |
[isp router a] - <routing protocol z> - [isp router b]
| |
\ /
ISP Network 10.0.0.0/8
--
Best regards,
Roman Hochuli
Operations Manager
nexellent ag
Saegereistrasse 33
CH-8152 Glattbrugg
Phone: +41 44 872 20 00
Fax: +41 44 872 20 01
URL: www.nexellent.ch
X-NCC-RegID: ch.nexellent
Imagination is the one weapon in the war
against reality.
-- Jules de Gaultier
_______________________________________________
swinog mailing list
swinog(a)lists.swinog.ch
http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
11:44 a.m.
Hello Fadi
Thank you for your reply.
Most ISPs would use BGP and typically it would look
like this:
That's basically the setup I described. Still remaining my question:
which ISPs run setups like that in CH?
--
Best regards,
Roman Hochuli
Operations Manager
nexellent ag
Saegereistrasse 33
CH-8152 Glattbrugg
Phone: +41 44 872 20 00
Fax: +41 44 872 20 01
URL: www.nexellent.ch
X-NCC-RegID: ch.nexellent
Imagination is the one weapon in the war
against reality.
-- Jules de Gaultier
12:41 p.m.
Hi Roman,
I cannot speak for others but I would imagine that any ISPs should be
willing to run such setups, at least I can confirm in the ISP where I work
we do this all the time, for both PA and PI.
Regards,
Fadi
On Fri, Nov 2, 2012 at 11:44 AM, Roman Hochuli
<roman.hochuli(a)nexellent.ch>wrote;wrote:
Hello Fadi
Thank you for your reply.
Most ISPs would use BGP and typically it would
look like this:
That's basically the setup I described. Still remaining my question:
which ISPs run setups like that in CH?
--
Best regards,
Roman Hochuli
Operations Manager
nexellent ag
Saegereistrasse 33
CH-8152 Glattbrugg
Phone: +41 44 872 20 00
Fax: +41 44 872 20 01
URL: www.nexellent.ch
X-NCC-RegID: ch.nexellent
Imagination is the one weapon in the war
against reality.
-- Jules de Gaultier
3979
days inactive
3979
days old
7 comments
4 participants
participants (4)
-
Fadi Bushnaq -
Jeroen Massar -
Roman Hochuli -
Stanislav Sinyagin