---
title: "Internet peering on ANAPs"
canonical: "https://docs.aryaka.com/space/KNOW/1299742771/Internet%20peering%20on%20ANAPs"
format: markdown
---
An ANAP inserted in  dual port routed modes  like  edge routed mode  (ERM) or  inline routed mode  (IRM) can peer with their public-facing gateway using BGP. This feature allows customers who own their own IP blocks to advertise these subnets from each of their ISPs to the internet. Customers must choose whether the site uses MED or AS Path Prepends as the preferred path identification method. Customers can also opt for each internet-facing interface to have this feature enabled separately. For each of these interfaces, configuration is done by providing the following: Local ANAP—IP address of the internet facing interface used to source the BGP connection. Peer IP—IP address of the gateway device that is the destination of the BGP connection. Local AS—Unique AS number that identifies this BGP end point at the site. Remote AS—Unique AS number that identifies the BGP peer. MD5 password (optional) Advertising routes Each of the public subnets hosted at the site can be advertised to each of the internet-facing BGP peers with separate MED or AS Path Prepend values. Learning routes The routes advertised by internet-facing BGP peers are discarded by the ANAP unless it is a default route. This is because the ANAP is not a transit router and does not need to learn the internet's routing table. Related topics ANAPs ANAP insertion topology Configure routing