Differences

This shows you the differences between two versions of the page.

--- wiki:bgp_ip_transit_info [2026/02/11 11:27] – add Updating path length and more screenshot antisa
+++ wiki:bgp_ip_transit_info [2026/06/10 09:41] (current) – add info about LOA antisa
@@ Line 6: / Line 6: @@
 The obtained subnet can be advertised from your server(s) via [[https://github.com/osrg/gobgp|goBGP]] or similar. There are 2 ways to do it **dynamic** or **static** BGP routing. You need to tell your server provider which one you want.
+Sometimes the provider might ask you for a Letter of authorization (LOA). This is a legal document which you need to fill out to prove you are the actual owner of the advertised IPs. You should ask the provider to send you a template if you don't have one. [[https://clients.hostslim.eu/knowledgebase/16/LOA-Letter-of-Authorization-ip-announcement-andoror-acceptance.html|Example here]].
 In dynamic setup you use your own AS# then you would setup BGP, and create a route object with ripe/arin for your ipv4 and ipv6 and specify the origin as your AS#. That would be dynamic routing as you could advertise or remove it from the provider on your own.
@@ Line 76: / Line 78: @@
 //as// is your assigned ASN number.
-//neighbor-address// is the IP of the peer, provider should give you this info.
+//neighbor-address// is the IP of the peer, provider should give you this info. There can be multiple peers for redundancy, so you just need to repeat this section for all the other IPs.
 //peer-as// is peer ASN, also given by provider.
@@ Line 97: / Line 99: @@
 :9000:600:24::1 11878    00:13:06 Establ      |        1         1
 </code>
+//Received// and //Accepted// columns can also be 0. Depends on provider routing.
-Check the routing table
+Check the routing table. You might see something like this
 <code>
@@ Line 118: / Line 121: @@
 *  2a03:c040::/48       ::                                        00:06:24   [{Origin: ?}]
+</code>
+or this
+<code | download>
+# gobgp global rib -a ipv4
+   Network              Next Hop             AS_PATH              Age        Attrs
+*  89.124.253.0/24      0.0.0.0                                   00:44:53   [{Origin: ?}]
+# gobgp global rib -a ipv6
+   Network              Next Hop             AS_PATH              Age        Attrs
+*  2a03:c040::/48       ::                                        00:44:54   [{Origin: ?}]
+</code>
+This should be ok. What you need to check is that you are advertising your IPs you should see something like:
+<code | download>
+# gobgp neighbor 198.44.157.1 adj-out
+   ID  Network              Next Hop             AS_PATH              AttrsFiltered
+   89.124.253.0/24      198.44.157.3         203619               [{Origin: ?}]not filtered
 </code>
@@ Line 217: / Line 239: @@
 On RIPE Looking glass this will be shown as
 {{:wiki:screenshots:2026:02:ripe_lg.png?direct&600|}}
+===== Withdrawing BGP announcements =====
+In case you need to take the server offline for maintenance and you have a dynamic setup i.e. you yourself is advertising the routes via the BGP daemon on your server, it is sufficient to simply stop the BGP session on your side before the maintenance begins. Once the session is down, the advertisements for will be withdrawn automatically.
+After the maintenance is completed, you can start the session again and the prefixes will be re-advertised as before.
 ====== Tested on ======
   * gobgp_version: 4.2.0
@@ Line 232: / Line 260: @@
   * https://datatracker.ietf.org/doc/html/rfc4271#autoid-1
   * https://www.noction.com/blog/as-path-and-as-path-prepending
+  * https://www.netactuate.com/docs/guides/mixed-provider-anycast