BGP peering reset on unsupported RTC route

[Thomas Morin]

networking_bagpipe.bagpipe_bgp.engine.exabgp_peer_worker:

[-] Error: (=> aborting receive_loop and reinitializing): AssertionError
[-] : AssertionError
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/networking_bagpipe/bagpipe_bgp/engine/bgp_peer_worker.py", line 264, in _receive_loop
    loop_result = self._receive_loop_fun()
  File "/usr/lib/python2.7/site-packages/networking_bagpipe/bagpipe_bgp/engine/exabgp_peer_worker.py", line 333, in _receive_loop_fun
    message.attributes)
  File "/usr/lib/python2.7/site-packages/networking_bagpipe/bagpipe_bgp/engine/exabgp_peer_worker.py", line 361, in _process_received_route
    self._subscribe(afi, safi, nlri.rt)
  File "/usr/lib/python2.7/site-packages/networking_bagpipe/bagpipe_bgp/engine/worker.py", line 125, in _subscribe
    subobj = engine.Subscription(afi, safi, rt, self)
  File "/usr/lib/python2.7/site-packages/networking_bagpipe/bagpipe_bgp/engine/__init__.py", line 295, in __init__
    _SubUnsubCommon.__init__(self, afi, safi, route_target, worker)
  File "/usr/lib/python2.7/site-packages/networking_bagpipe/bagpipe_bgp/engine/__init__.py", line 264, in __init__
    exa.RouteTarget)
AssertionError

This happens when a BGP peer advertise a BGP RTC route (RFC4684, also sometimes called "route-target" family).

route_target: target:192.168.53.11:0 (<class 'exabgp.bgp.message.update.attribute.community.extended.rt.RouteTargetIPNumber'>)