These are chat archives for Exa-Networks/exabgp

4th
Nov 2016
Ben Agricola
@benagricola
Nov 04 2016 09:50
@vincentbernat RE: Exa-Networks/exabgp@8cad7d5 - I'm pretty sure adding networks to loopback on linux works fine, the 127.0.0.1/8 address is after all a network and you can use any IP in that /8 to refer to localhost. I also have a /28 allocated on loopback using Exabgp (prior to that commit) and that is contactable as well
Thomas Mangin
@thomas-mangin
Nov 04 2016 11:09
@benagricola - happy to trust people who spend the time to check that it works - which won’t be me today :-( - I will let @vincentbernat comment on why he felt this change was necessary. healthcheck is his code and I am just the costedian of the repository :wink:
Ben Agricola
@benagricola
Nov 04 2016 11:10
haha, no worries @thomas-mangin, it's likely that I don't have a full picture or it's some behaviour that has changed at some point
Ben Agricola
@benagricola
Nov 04 2016 11:47
I also don't think it makes a big difference, the only thing I can think of is it'd be annoying if you were to add --ip=1.2.3.0/24 --deaggregate-networks
and then ip a would be somewhat... verbose :D
Ben Agricola
@benagricola
Nov 04 2016 14:31
hmm... having an issue passing cmd line arguments to healthcheck via exabgp... looks like the config tokeniser splits stuff up on spaces regardless of if they're in a quoted string or whatever... assuming the response here is 'do complex stuff like this in a script and pass the path to exabgp instead'?
Thomas Mangin
@thomas-mangin
Nov 04 2016 15:50
@benagricola I think I fixed this on master … did I forget to backport it (or was it the other way round !)
But yes - that would be the easy way round ..