These are chat archives for Exa-Networks/exabgp

29th
Feb 2016
Thomas Mangin
@thomas-mangin
Feb 29 2016 12:30
@nskalis Sorry I failed to understand your question about labelled routes but looking at the gobgp patch I think that answer is yes it is supported
convert = {
    'ipv4': {
        'unicast':   (AFI(AFI.ipv4),SAFI(SAFI.unicast)),
        'multicast': (AFI(AFI.ipv4),SAFI(SAFI.multicast)),
        'nlri-mpls': (AFI(AFI.ipv4),SAFI(SAFI.nlri_mpls)),
        'mpls-vpn':  (AFI(AFI.ipv4),SAFI(SAFI.mpls_vpn)),
        'flow':      (AFI(AFI.ipv4),SAFI(SAFI.flow_ip)),
        'flow-vpn':  (AFI(AFI.ipv4),SAFI(SAFI.flow_vpn)),
    },
    'ipv6': {
        'unicast':   (AFI(AFI.ipv6),SAFI(SAFI.unicast)),
        'mpls-vpn':  (AFI(AFI.ipv6),SAFI(SAFI.mpls_vpn)),
        'flow':      (AFI(AFI.ipv6),SAFI(SAFI.flow_ip)),
        'flow-vpn':  (AFI(AFI.ipv6),SAFI(SAFI.flow_vpn)),
    },
    'l2vpn': {
        'vpls':      (AFI(AFI.l2vpn),SAFI(SAFI.vpls)),
        'evpn':      (AFI(AFI.l2vpn),SAFI(SAFI.evpn)),
    }
}
Or if it is not, it should be easy
Hi @ishidawataru :-)
Wataru Ishida
@ishidawataru
Feb 29 2016 12:34
Hi @thomas-mangin
just fixed gobgp’s bug of ipv6-labeled nlri parser
Thomas Mangin
@thomas-mangin
Feb 29 2016 12:35
As I never had to really use it (just implemented things) I would appreciate if you could tell me what was required for you to implement ipv4|6-labelled routes.
Is it just a case of announcing the family in the capability and associating the right AFI/SAFI when announce MultiProtocol routes ?
I am trying to catch-up on user request after a few months when I could not code.
Wataru Ishida
@ishidawataru
Feb 29 2016 12:37
yes it won’t be hard for you to implement. it is just another address-family.
here is gobgp’s ipv4-labelled nlri parser/serializer
difference from ipv4-vpn is it lacks route-distinguisher
Thomas Mangin
@thomas-mangin
Feb 29 2016 12:39
This looks like RFC3107 ..
In that case, is it what I called nlri-mpls ?
Or is there a difference ?
Wataru Ishida
@ishidawataru
Feb 29 2016 12:40
yes it is RFC3107
Thomas Mangin
@thomas-mangin
Feb 29 2016 12:40
ah ! :-)
Wataru Ishida
@ishidawataru
Feb 29 2016 12:40
6PE is a name of the application using RFC3107
Thomas Mangin
@thomas-mangin
Feb 29 2016 12:40
Thank you @ishidawataru : I learn things everyday :-)
@nskalis : so here you are nlri-mpls is your friend :-)
just add a label to a route and the AFI/SAFI will change to what you need
4.0 will break down routes into their families ( so it will be clearer)
Thomas Mangin
@thomas-mangin
Feb 29 2016 13:30
patch Exa-Networks/exabgp@b83b545
let’s see if it does what @nskalis needs
Bryan Benson
@bmbenson
Feb 29 2016 18:29
@thomas-mangin To followup on the MD5 question. I was able to bring up a session w/ MD5 when we were NATd by attaching the public IP to the host and using iptables to SNAT from public->private. Thank you!
Thomas Mangin
@thomas-mangin
Feb 29 2016 21:31
have a new patch adding the md5-ip as an option