COVID-19 Update
BGP Policy banner

WebReach / SAIX BGP policy

WebReach / SAIX BGP policy

Tag with star icon
Basic requirements for ISP clients
  • Require a BGP ASN (autonomous system number) allocated by ARIN, RIPE, APNIC or Afrinic.
  • Router must be BGP capable.
  • Require IP blocks allocated by ARIN, RIPE, APNIC or Afrinic.
  • Must aggregate their IP blocks as much as possible.
  • Require a route object registered with an IRR to expose their prefixes.
Block with gear icon
WebReach / SAIX Default BGP configuration

The WebReach / SAIX default BGP configuration will be configured as follows:

  • BGP peer will be established to the client’s ASN.
  • Private ASNs will be removed when routes are advertised.
  • An IP address filter will be setup to only allow the client to send IP addresses belonging to the client. If a client obtains another range of IP addresses the client will have to inform WebReach / SAIX to update this IP address filter before they are accepted.
  • WebReach / SAIX will update its relevant peer filters to ensure that the client’s IP addresses are propagated to all local and international peers*. This process may take up to 72 working hours.
  • WebReach / SAIX will accept a block no smaller than a /24.
  • A client may request the BGP session to be password protected. If no such request is received the BGP session will not be password protected.

* This may differ in clients who have only purchased a national-only service.

Contact card icon
BGP MED (multi exit discriminator) / AS path prepend
  • WebReach / SAIX accept MED for path selection.
  • WebReach / SAIX accept AS path prepend for path selection.
Envelope icon
Input community (sent by client to WebReach / SAIX)
  • To use this feature a client must request that WebReach / SAIX implement this on the BGP session as by default this feature is not enabled.
  • WebReach / SAIX accepts multiple communities for IP blocks. Communities are categorized into 2 levels. Level 1 and Level 2 communities.
Newspaper icon
Level 1 community
  • The Level 1 community is used to determine how the IP Block is advertised to other WebReach / SAIX peers, like other clients, local peering and international peering.
  • This community is mandatory and should always be present on any IP block that is advertised to WebReach / SAIX. If the Level 1 community is not set, the default behaviour on the WebReach / SAIX router will be to advertise this IP block to every client and peer, i.e. is the same as setting community 5713:100*. Table 2 indicates which Level 1 communities can be sent by the client and what they are used for.

* This may differ in clients who have only purchased a national-only service.

Community
Purpose
5713:100
Advertise IP block to everyone (international peers, local peers and WebReach / SAIX clients).
5713:200
Advertise IP block to local peers and WebReach / SAIX clients.
5713:300
Not exported out of the WebReach / SAIX ASN.

Table 2: Level 1 communities

Info icon

NOTE: Only ONE Level 1 community should be set on an IP block however if TWO or MORE Level 1 communities are set, the top most community setting will be set. For example, if you set TWO Level 1 communities like 5713:100 and 5713:200 on an IP block, the 5713:100 setting will be applied on the WebReach / SAIX router.

Newspaper icon
Level 2 community
  • The Level 2 community is used to determine if an IP block should NOT be advertised to a certain WebReach / SAIX BGP peer. The setting of the Level 2 community is NOT MANDATORY. The table below indicates which Level 2 communities can be sent by the client and what they are used for.
Community
Purpose
5713:1001
Will not advertise IP block to WebReach / SAIX Google Cache (see table "5713:1001 Usage" below for explanation)

Table 3: Level 2 communities

Info icon

NOTE: A Level 2 community has no relevance with a Level 1 community set to 5713:300.

  • The following is required for users on the WebReach / SAIX network to be served by the WebReach / SAIX Google Cache segment:
    1. The Internet IP address of the end user must be advertised via BGP to the WebReach / SAIX Google Cache. By default WebReach / SAIX will advertise all clients routes to the WebReach / SAIX Google Cache.
    2. The Internet IP address of the DNS resolver that the client is using must be advertised via BGP to the WebReach / SAIX Google Cache. By default WebReach / SAIX will advertise all client’s routes to the WebReach / SAIX Google Cache.
  • If either of these Internet IP addresses is not advertised via BGP to the WebReach / SAIX Google Cache, the request will be served outside of the WebReach / SAIX Google Cache. The WebReach / SAIX Google Cache uses the routes it learns via the BGP session only as a mechanism to communicate the list of users that should be served from a node and not for routing purposes.
  • Clients that require not to be served by the WebReach / SAIX Google Cache need to set the 5713:1001 community on either their end-users IP addresses or the DNS resolver's IP address that the users are using, or both. Once the community is set, WebReach / SAIX will no longer advertise these IP addresses to the WebReach / SAIX Google Cache, which will result in the users not being served from the WebReach / SAIX Google Cache. Note that this process is not immediate and may take some time to take effect.
Clipboard icon
Output community (sent by WebReach / SAIX to client)
  • To use this feature, a client must request that WebReach / SAIX implement this on the BGP session, as by default this feature is not enabled. This feature is only supported on BGP sessions that take a full internet routing table feed from WebReach / SAIX.
  • WebReach / SAIX can mark IP blocks to help a client determine if a route is a local or international route. The table below indicates the communities that WebReach / SAIX will mark.

* This may differ in clients who have only purchased a national-only service.

Community
Purpose
5713:777
Routes received from an international peer.
IP blocks with no community set indicates a route was not received by an international peer.

Table 4: Output communities