On Wed, 14 Sep 2016, Martin Winter wrote:
You’ll see my tester opening the BGP session first and giving in the
capabilities IPv6 Unicast. The OPEN in response from Quagga is missing
the IPv6/Unicast AFI/SAFI
Weird. You have it configured. So the 'activate' statement led to
peer_activate being called and:
peer->afc[afi][safi] = 1;
surely was called. And bgp_open_capability uses that to write out the
capability advertisement.
So how was it not in the OPEN?
Here is the relevant config from the Quagga Side:
Current configuration:
!
! [...]
!
interface eth2
ip address 192.168.1.101/24
ipv6 address fc00:192:168:1::101/64
!
! [...]
!
router bgp 500
bgp router-id 192.168.1.101
network 192.168.1.0/24
neighbor fc00:192:168:1::1 remote-as 501
neighbor fc00:192:168:1::1 ebgp-multihop 255
neighbor fc00:192:168:1::1 timers 60 180
!
address-family ipv6
network fc00:192:168:1::/64
neighbor fc00:192:168:1::1 activate
exit-address-family
exit
!
ip forwarding
ipv6 forwarding
!
line vty
!
end
Let me know if you need anything else. I’m working to fix my CI to correctly
detect issues like these.
Hmm. I can't reproduce this. It works for me between 2 Quaggas.
regards,
--
Paul Jakma | [email protected] | @pjakma | Key ID: 0xD86BF79464A2FF6A
Fortune:
Has anyone ever tasted an "end"? Are they really bitter?
_______________________________________________
Quagga-dev mailing list
[email protected]
https://lists.quagga.net/mailman/listinfo/quagga-dev
