Differences

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

--- computing:bgproutes [2026/08/11 11:20] – created oemb1905
+++ computing:bgproutes [2026/08/11 11:34] (current) – oemb1905
@@ Line 1: / Line 1: @@
+-------------------------------------------
+  * **bgp-routes**
+  * **Jonathan Haack**
+  * **Haack's Networking**
+  * **webmaster@haacksnetworking.org**
+-------------------------------------------
+//BGP Routes//
-   telnet route-views.routeviews.org
+-------------------------------------------
-   show bgp ipv6 unicast 2604:fa40::/32
+I came up with this after a 96 hour outage. It avoids using proprietary websites and tools, i.e., looking glass sites, etc. To To confirm BGP routes from within a live routing table on the internet, one can use routeviews.org with telnet. Here is how I check routes for my Data Center's ipv6 /32:
+<code>
+telnet route-views.routeviews.org
+show bgp ipv6 unicast 2604:fa40::/32
+</code>
+Running that query now, provides the following output:
+<code>
+Trying 2001:468:d01:33::80df:3367...
+Connected to route-views.routeviews.org.
+Escape character is '^]'.
+**********************************************************************
+                    RouteViews BGP Route Viewer
+                    route-views.routeviews.org
+ RouteViews data is archived on https://archive.routeviews.org
+ This hardware is part of a grant by the NSF.
+ Please contact help@routeviews.org if you have questions, or
+ if you wish to contribute your view.
+ This router has views of full routing tables from several ASes.
+ The current list of all RouteViews peers is at
+   https://www.routeviews.org/peers/peering-status.html
+ NOTE: If you are using macOS and seeing the error message
+ "no default Kerberos realm" when logging in, you may want to
+ add "default unset autologin" to your ~/.telnetrc
+ To login, use the username "rviews".
+**********************************************************************
+User Access Verification
+Username: rviews
+route-views>show bgp ipv6 unicast 2604:fa40::/32
+BGP routing table entry for 2604:FA40::/32, version 1040563522
+Paths: (11 available, best #11, table default)
+  Not advertised to any peer
+  Refresh Epoch 1
+3356 17098
+:7800:100::16 from 2402:7800:100::16 (114.31.199.16)
+      Origin IGP, localpref 100, valid, external
+      Community: 3356:3 3356:22 3356:100 3356:123 3356:575 3356:601 3356:903 3356:2026 4826:5901 4826:6150 4826:59014
+      path 7F1611CA7ED8 RPKI State not found
+      rx pathid: 0, tx pathid: 0
+  Refresh Epoch 1
+27552 3356 17098
+:104:E000:1000::3 from 2620:104:E000:1000::3 (132.198.255.253)
+      Origin IGP, localpref 100, valid, external
+      path 7F1586CB1598 RPKI State not found
+      rx pathid: 0, tx pathid: 0
+  Refresh Epoch 2
+3356 17098
+:918:0:5::1 from 2001:918:0:5::1 (138.187.128.158)
+      Origin IGP, localpref 100, valid, external
+      Community: 3303:1004 3303:1007 3303:3066 3356:3 3356:22 3356:100 3356:123 3356:575 3356:601 3356:903 3356:2026
+      path 7F16EDC49068 RPKI State not found
+      rx pathid: 0, tx pathid: 0
+  Refresh Epoch 1
+3356 17098
+:1860::223 from 2001:1860::223 (209.124.176.224)
+      Origin IGP, localpref 100, valid, external
+      Community: 101:20100 101:20110 101:22100 101:24100 3356:3 3356:22 3356:100 3356:123 3356:575 3356:601 3356:903 3356:2026
+      Extended Community: RT:101:22100
+      path 7F15DF560098 RPKI State not found
+      rx pathid: 0, tx pathid: 0
+  Refresh Epoch 1
+3356 17098
+:1890:111D:1::63 from 2001:1890:111D:1::63 (12.0.1.63)
+      Origin IGP, localpref 100, valid, external
+      Community: 7018:5000 7018:37232
+      path 7F1597C68258 RPKI State not found
+      rx pathid: 0, tx pathid: 0
+  Refresh Epoch 1
+3356 17098
+A00:A7C0:E20A::17 from 2A00:A7C0:E20A::17 (37.139.139.17)
+      Origin IGP, metric 0, localpref 100, valid, external
+      Community: 3356:3 3356:22 3356:100 3356:123 3356:575 3356:601 3356:903 3356:2026 57866:100 65100:3356 65103:1 65104:31
+      unknown transitive attribute: flag 0xE0 type 0x20 length 0x30
+        value 0000 E20A 0000 0064 0000 0D1C 0000 E20A
+0065 0000 0064 0000 E20A 0000 0067
+0001 0000 E20A 0000 0068 0000 001F
+      path 7F1566DEBF90 RPKI State not found
+      rx pathid: 0, tx pathid: 0
+  Refresh Epoch 1
+1299 3356 17098
+A02:D140:1::60 from 2A02:D140:1::60 (91.218.184.60)
+      Origin IGP, localpref 100, valid, external
+      Community: 1299:4000 1299:20000 1299:52000
+      path 7F155FC96050 RPKI State not found
+      rx pathid: 0, tx pathid: 0
+  Refresh Epoch 1
+57866 3356 17098
+A02:898:0:300::3 from 2A02:898:0:300::3 (94.142.247.3)
+      Origin IGP, localpref 100, valid, external
+      Community: 3356:3 3356:22 3356:100 3356:123 3356:575 3356:601 3356:903 3356:2026 8283:15 57866:100 65100:3356 65103:1 65104:31
+      unknown transitive attribute: flag 0xE0 type 0x20 length 0x3C
+        value 0000 205B 0000 0006 0000 000F 0000 E20A
+0064 0000 0D1C 0000 E20A 0000 0065
+0064 0000 E20A 0000 0067 0000 0001
+E20A 0000 0068 0000 001F
+      path 7F16B9C69678 RPKI State not found
+      rx pathid: 0, tx pathid: 0
+  Refresh Epoch 1
+6939 3356 17098
+:40D0::1E from 2001:40D0::1E (77.39.192.1)
+      Origin IGP, localpref 100, valid, external
+      Community: 20912:65002 20912:65021
+      path 7F156339A928 RPKI State not found
+      rx pathid: 0, tx pathid: 0
+  Refresh Epoch 1
+6939 3356 17098
+:0:2250::FF0B from 2620:0:2250::FF0B (140.192.8.16)
+      Origin IGP, localpref 100, valid, external
+      path 7F157508F098 RPKI State not found
+      rx pathid: 0, tx pathid: 0
+  Refresh Epoch 1
+3356 17098
+:470:0:1A::1 from 2001:470:0:1A::1 (216.218.253.53)
+      Origin IGP, localpref 100, valid, external, best
+      path 7F16824DC778 RPKI State not found
+      rx pathid: 0, tx pathid: 0x0
+route-views> quit
+</code>
+In the output above, you can clearly see ''3356 17098'', which can be parsed by using ''whois'' against ''cymru.com'' data as follows:
+  whois -h whois.cymru.com "AS17098"
+  whois -h whois.cymru.com "AS3356"
+  whois -h whois.cymru.com "AS6461"
+The top command, for example, provides:
+<code>
+AS Name
+BROWNRICE-INTERNET-1 - Brownrice Internet, Inc., US
+</code>
+After that, look for priority in two ways. One the side by side ASN number will be the secondary route if no others are advertised. If there are two or more additional routes, look for which one has ''best'' in order to know which has priority, etc. If there is no secondary/additional route, then the ASN won't be in the output.
  --- //[[alerts@haacksnetworking.org|oemb1905]] 2026/08/11 11:20//

Haack's Wiki

User Tools

Site Tools

Differences

Page Tools