19 messages in net.nether.puck.cisco-nsp[c-nsp] Source address on BGP peering...
FromSent OnAttachments
PiltrafillaJan 14, 2005 8:13 am 
Mark TinkaJan 14, 2005 8:46 am 
McCallum, RobertJan 14, 2005 9:00 am 
Daniel GinsburgJan 14, 2005 9:04 am 
Erdem SenerJan 14, 2005 9:09 am 
Marko MilivojevicJan 14, 2005 9:17 am 
Mark TinkaJan 14, 2005 9:19 am 
Rick CosseyJan 14, 2005 9:52 am 
Jared MauchJan 14, 2005 10:02 am 
Stephen J. WilcoxJan 14, 2005 10:34 am 
PiltrafillaJan 17, 2005 11:27 am 
Brian FeenyJan 17, 2005 11:37 am 
PiltrafillaJan 17, 2005 6:59 pm 
Brian FeenyJan 17, 2005 7:18 pm 
Michael K. SmithJan 17, 2005 10:30 pm 
PiltrafillaJan 18, 2005 3:33 am 
PiltrafillaJan 18, 2005 4:49 am 
Michael K. SmithJan 18, 2005 11:52 am 
PiltrafillaJan 24, 2005 8:01 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:[c-nsp] Source address on BGP peering set upActions...
From:Piltrafilla (pilt@gmail.com)
Date:Jan 14, 2005 8:13:59 am
List:net.nether.puck.cisco-nsp

Hi people,

Anyone knows how BGP on a Cisco router choose source IP address for peering establishment if no "update-source" command is applied to neighbor? Is it only the primary IP address on the closest interface to neighbor?

For instance, let's say that you would like to set up a peering using a secondary IP address to between two directly-connected neighbors. Is it setting up loopbacks, static /32 routes and update-source on the neighbors' config the only way to do it?

On bgpd of OpenBSD you could set up a "local-address" parameter per neighbor or group that sets up source IP address used for that peering. I haven't found any similar parameter on cisco bgp neighbors' config.

Thanks in advance,

-- Piltrafilla