Difference between revisions of "Cisco: BGP Dua Link No Transit"
Jump to navigation
Jump to search
Onnowpurbo (talk | contribs) (Created page with "sumber: http://routerric.blogspot.com/2010/03/bgp-transit-ass-and-how-to-avoid.html How can you prevent your own BGP AS becoming a transit path? This can be achieved by makin...") |
Onnowpurbo (talk | contribs) |
||
(One intermediate revision by the same user not shown) | |||
Line 1: | Line 1: | ||
sumber: http://routerric.blogspot.com/2010/03/bgp-transit-ass-and-how-to-avoid.html | sumber: http://routerric.blogspot.com/2010/03/bgp-transit-ass-and-how-to-avoid.html | ||
− | + | Mungkinkah kita membuat supaya BGP AS yang kita gunakan tidak menjadi transit path? | |
BB1 ------ R1 (AS 101) ------- R2 (AS 101) ------- BB2 | BB1 ------ R1 (AS 101) ------- R2 (AS 101) ------- BB2 | ||
− | + | Hal ini dapat dengan mudah dilakukan dengan (1) distribute-list. Cara ini tidak scale dengan mudah jika ip address berubah dikemudian hari karena harus melihat access lists | |
− | OPTION 1 - | + | Atau dengan (2) prefix-list, cara ini lebih mudah untuk berkembang tanpa perlu melihat jika IP address berubah. |
+ | |||
+ | |||
+ | ==OPTION 1 - menggunakan no-export community== | ||
------------------------------------------------------------- | ------------------------------------------------------------- | ||
− | + | Disini community no-export di berlakukan ke semua ALL incoming bgp routes. | |
R1 | R1 | ||
Line 21: | Line 24: | ||
− | OPTION 2 – | + | ==OPTION 2 – menggunakan perintah filter-list== |
− | |||
− | + | Disini kita membuat as-path access list dan hanya mengijinkan bgp routes originated dari AS asal router (AS 101) yang di advertised out. | |
R2 | R2 | ||
Line 32: | Line 34: | ||
neigh {ip addrBB2} filter-list 1 out | neigh {ip addrBB2} filter-list 1 out | ||
+ | Dua perintah di atas digunakan | ||
+ | |||
+ | show ip bgp {ip address} advertise | ||
− | + | untuk memverifikasi advertised routes. | |
Line 45: | Line 50: | ||
==Pranala Menarik== | ==Pranala Menarik== | ||
+ | * [[TCP/IP: Advanced Routing]] | ||
* [[Quagga]] | * [[Quagga]] | ||
* [[Mikrotik]] | * [[Mikrotik]] | ||
* [[Cisco]] | * [[Cisco]] | ||
* [[Juniper]] | * [[Juniper]] | ||
+ | * [[BIRD: Routing]] | ||
+ | * [[IPv6]] |
Latest revision as of 09:30, 1 January 2019
sumber: http://routerric.blogspot.com/2010/03/bgp-transit-ass-and-how-to-avoid.html
Mungkinkah kita membuat supaya BGP AS yang kita gunakan tidak menjadi transit path?
BB1 ------ R1 (AS 101) ------- R2 (AS 101) ------- BB2
Hal ini dapat dengan mudah dilakukan dengan (1) distribute-list. Cara ini tidak scale dengan mudah jika ip address berubah dikemudian hari karena harus melihat access lists
Atau dengan (2) prefix-list, cara ini lebih mudah untuk berkembang tanpa perlu melihat jika IP address berubah.
OPTION 1 - menggunakan no-export community
Disini community no-export di berlakukan ke semua ALL incoming bgp routes.
R1 route-map NOEXPORT set community no-export router bgp 101 neigh {ip addr BB1} route-map NOEXPORT in neigh {ip addr r2} send-community
OPTION 2 – menggunakan perintah filter-list
Disini kita membuat as-path access list dan hanya mengijinkan bgp routes originated dari AS asal router (AS 101) yang di advertised out.
R2 ip as-path access-list 1 permit ^$ router bgp 101 neigh {ip addrBB2} filter-list 1 out
Dua perintah di atas digunakan
show ip bgp {ip address} advertise
untuk memverifikasi advertised routes.