GLL

Expanding BGP Data Horizons


GILL offers a fundamentally different approach compared to existing BGP collection platforms.
It stands out by providing an open peering policy and making all collected data publicly accessible to the entire community. This is achievable because GILL selectively stores only the most valuable data, thereby reducing costs. In contrast, other platforms either keep their data confidential or implement selective peering policies.

An overview of the BGP route collection platforms landscape. landscape over the different platforms that collect BGP routes and make them available to users

Why you should consider peering with GILL

✅ United we stand. By peering with GILL, you will share your RIB and every BGP route update that you observe with the entire community. In return, you can monitor how the BGP updates of your interest propagate across the Internet thanks to the other networks that peer with GILL.

✅ We need all of you. Whether you are a large Tier-1 AS, a small stub AS, or any other AS on the Internet, we welcome you to peer with GILL. Unlike other public BGP route collection platforms that selectively accept new peers, GILL takes a more inclusive approach and welcomes everyone.

✅ It is easy and fast. There is nothing easier than peering with GILL. Everything is automated. It should take less than ten minutes of your time and only requires a few lines of configuration on one of your BGP router.

✅ Clear data sharing policy. We believe in transparency regarding what happens with the data GILL collects. Our data sharing policy is straightforward, helping you make informed decisions about whether to peer with GILL. Our leitmotiv is that the data stored on our servers will always be publicly available.

What you should pay attention to with GILL

❗ Some data is discarded. To save resources, GILL selectively stores BGP route updates rather than retaining all collected data. The selection process employs peer-reviewed algorithms designed to eliminate redundant information, ensuring that only essential updates are preserved.

❗ Peering is only possible with BGP multihop. While this simplifies the architecture of GILL, it also means that your BGP session with GILL may pass through multiple ASes. We are actively working to enhance the security of these BGP multihop sessions to prevent vulnerabilities from third-party adversarial inputs. In any case, peering sessions with GILL are strictly for monitoring purposes and will not impact your other critical BGP sessions.

Start peering with GILL and contribute BGP data

Peering with GILL is quick and straightforward.

Step #1: Configure a BGP session.
Set up a BGP session with GILL that has AS65000 and IP address 185.216.75.11.
❗ Currently, we only support IPv4. IPv6 support will be added when we transition to production mode. However we support the IPv6 capability on IPv4 sessions.

We show how to configure a BGP session with GILL for three types of router software.
  1. ebgp-multihop 255: set the TTL of BGP packets to 255, allowing for remote connections between GILL and your router.
  2. update-source: specify the IP address to be used for the BGP session on your side, ensuring it matches the IP address you provide in the form below.
  3. route-map DENY-ALL-IN: This route map blocks all incoming BGP updates. While GILL does not send route updates, this additional security measure ensures no unintended updates are accepted. 
# FRRouting Configuration
router bgp YOUR_ASN
neighbor 185.216.75.11 remote-as 65000
neighbor 185.216.75.11 description Peering with GILL
neighbor 185.216.75.11 ebgp-multihop 255
neighbor 185.216.75.11 update-source YOUR_SOURCE_IP
neighbor 185.216.75.11 route-map DENY-ALL-IN in

route-map DENY-ALL-IN deny 1
                                
! Cisco IOS Configuration
router bgp YOUR_ASN
neighbor 185.216.75.11 remote-as 65000
neighbor 185.216.75.11 description Peering with GILL
neighbor 185.216.75.11 ebgp-multihop 255
neighbor 185.216.75.11 update-source YOUR_SOURCE_IP
neighbor 185.216.75.11 route-map DENY-ALL-IN in

route-map DENY-ALL-IN deny 10
match ip address prefix-list DENY-ALL

ip prefix-list DENY-ALL seq 5 deny 0.0.0.0/0 le 32
                                
# Juniper OS Configuration
set policy-options policy-statement DENY-ALL term 1 then reject
set protocols bgp group GILL neighbor 185.216.75.11 peer-as 65000
set protocols bgp group GILL neighbor 185.216.75.11 description "Peering with GILL"
set protocols bgp group GILL neighbor 185.216.75.11 local-address YOUR_SOURCE_IP
set protocols bgp group GILL neighbor 185.216.75.11 multihop 255
set protocols bgp group GILL neighbor 185.216.75.11 import DENY-ALL

Step 2: Submit your details.
Enter your ASN and the IPv4 address configured on your BGP session in the form below.


Step 3: Send us an email.
To authenticate the peering session, we ask you to send an email to peering@bgproutes.io from the email address listed in PeeringDB for your AS. Simply write "peering" in your email.

Once the form is submitted and the email received, GILL will automatically configure the BGP session, which should be active within a few seconds, and it will take about ten minutes for your routes to appear in our database. You can view the status of the peering session on the peers page.

❗ GILL is currently in prototype mode and operates on a small VM. In the short term, we may need to impose limitations on the number of peers and the volume of data we store. These limitations will be lifted once GILL transitions to production mode, and we are working hard to make that happen!