Community discussions

MikroTik App
 
bestparth
just joined
Topic Author
Posts: 2
Joined: Wed May 11, 2016 7:52 pm

Google Peering Configuration

Wed May 11, 2016 8:12 pm

I have google peering P2P but how to configure in mikrotik ??
i dont know how to configure?

and how to load balance in bgp??
 
User avatar
mrz
MikroTik Support
MikroTik Support
Posts: 7056
Joined: Wed Feb 07, 2007 12:45 pm
Location: Latvia
Contact:

Re: Google Peering Configuration

Thu May 12, 2016 10:00 am

You can start by looking at this example setup
http://wiki.mikrotik.com/wiki/Manual:Si ... ultihoming
 
User avatar
ZeroByte
Forum Guru
Forum Guru
Posts: 4047
Joined: Wed May 11, 2011 6:08 pm

Re: Google Peering Configuration

Fri May 13, 2016 5:30 pm

High-level overview steps:

Make an output filter for the Google peering session, and make sure that it only allows YOUR prefixes to be advertised.

e.g.
10.12.96.0/22 prefix-length=22-24 --> accept
10.99.32.0/21 prefix-length=21-24 --> accept
discard
(obviously, these will be public IP ranges in your case, never advertise private IP addresses to peers in public BGP sessions)


I'm pretty sure that Google is going to only send their prefixes to you and could most likely be trusted to behave well (no input filter), but you may wish to create an input filter chain which only accepts as-paths which end in Google's ASN.

You may even want to use a higher local_pref on the routes you learn from Google so that you always send traffic to Google over this dedicated link, freeing up other circuits to carry everything else. If so, then make the first rule of the google-in filter be:
bgp-actions: set BGP local_pref = 150 (or some value above your other preferences)
actions = passthrough (unless you're accepting all routes from Google, in which case, just use action=accept)

Ensure that your output filters to other peers won't allow the Google prefixes to be sent upstream or to any other peers.

If you have BGP-enabled customers, then make sure Google doesn't mind receiving these prefixes from your peering session, so that Google's traffic for your customers can be routed across the private peering as well - but make sure that these prefixes are only sent to Google when your link to the customer is up. You can use a BGP community to mark routes learned from customers and then allow routes to Google which have this community on them.

That should basically be all you need to do.
 
bestparth
just joined
Topic Author
Posts: 2
Joined: Wed May 11, 2016 7:52 pm

Re: Google Peering Configuration

Mon Oct 17, 2016 7:00 am

Hi
this is my core router
I Have 1 Upstream And 1 Google Peering
both links bgp is working perfect
Google traffic is threw from google peering but issue when i ping in my core router to 8.8.8.8 than ping is break at peering gateway

what is issue behind this scene?
if i add source ip is upstream then ping is working perfect

i also attched screenshot of my traceroute
1-peering source ip
2-upstream source ip
You do not have the required permissions to view the files attached to this post.
 
patrick7
Member
Member
Posts: 343
Joined: Sat Jul 20, 2013 2:40 pm

Re: Google Peering Configuration

Mon Oct 17, 2016 1:20 pm

That's most probably because Google does not propagate the IXP LAN's in their network by OSPF. If you use your IXP LAN as source, google does not know where to reply to. You should always use one of your advertised IPs as source (example: Loopback)

For IPv4, you can fix that with a routing filter: "set-pref-src". For IPv6 that's not possible at the moment.

Who is online

Users browsing this forum: No registered users and 42 guests