Timeline for Routing IPs through another ASN
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 7, 2021 at 5:54 | comment | added | ditrapanij | @user73125, usually they will tell you how they wish for this to be done. If you wanted to do it the private ASN way (and you already have a eBGP session with them from a Private ASN) all you will need to now do is redistribute the range into BGP somehow. This can be done so via a nail down route (e.g. static route for x.x.x.x/24 pointing to Null0 with a high admin distance) or by using the network x.x.x.x/24 command under your BGP instance. | |
| Jan 7, 2021 at 5:51 | comment | added | user73125 | Yes they understood the purpose of us getting a circuit with them we just don't know how to establish the private asn situation that you are explaining. The ISP already accepted the range and loa documents and added the range to the prefix list on our circuit its just a matter of establishing everything. | |
| Jan 7, 2021 at 5:23 | comment | added | ditrapanij | @user73125, you will still need to speak with your ISP. Most companies won't have a problem with this however they may want to nail the prefix down within their network before routing it towards you or something similar. | |
| Jan 7, 2021 at 5:21 | comment | added | user73125 | Hi thanks for your reply, the prefix list was updated with the ranges and an RPKI and IRR exist. | |
| Jan 7, 2021 at 5:09 | history | answered | ditrapanij | CC BY-SA 4.0 |