-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NLRI next hops are not formatted properly for ipv4 vpn #71
Milestone
Comments
louberger
added a commit
to LabNConsulting/frr
that referenced
this issue
Jan 15, 2017
Signed-off-by: Lou Berger <lberger@labn.net>
louberger
added a commit
to LabNConsulting/frr
that referenced
this issue
Jan 15, 2017
…FRRouting#71) Signed-off-by: Lou Berger <lberger@labn.net>
louberger
added a commit
to LabNConsulting/frr
that referenced
this issue
Jan 17, 2017
Signed-off-by: Lou Berger <lberger@labn.net>
louberger
added a commit
to LabNConsulting/frr
that referenced
this issue
Jan 17, 2017
…FRRouting#71) Signed-off-by: Lou Berger <lberger@labn.net>
louberger
added a commit
to LabNConsulting/frr
that referenced
this issue
Jan 18, 2017
On top of: bgpd: allow VPN next hop to be different AFI than NLRI next hop (Issue FRRouting#71) Signed-off-by: Lou Berger <lberger@labn.net>
louberger
added a commit
to LabNConsulting/frr
that referenced
this issue
Jan 18, 2017
Signed-off-by: Lou Berger <lberger@labn.net>
louberger
added a commit
to LabNConsulting/frr
that referenced
this issue
Jan 18, 2017
…FRRouting#71) Signed-off-by: Lou Berger <lberger@labn.net>
fixed in #83 |
#83 merged - closing. |
cfra
referenced
this issue
in opensourcerouting/frr
Nov 29, 2018
…Json bgp_l3vpn_to_bgp_vrf improvements
Closed
gpnaveen
pushed a commit
to gpnaveen/frr
that referenced
this issue
Oct 29, 2021
tests: adding mgmt automation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Seen in wireshark, Works fine in Quagga.
Format is correct when constructed.
Check in debugger @ bgp_updgrp_packet.c line 811 (stable/2.0)
The text was updated successfully, but these errors were encountered: