Skip to content
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

Closed
louberger opened this issue Jan 13, 2017 · 2 comments
Closed

NLRI next hops are not formatted properly for ipv4 vpn #71

louberger opened this issue Jan 13, 2017 · 2 comments
Milestone

Comments

@louberger
Copy link
Member

Seen in wireshark, Works fine in Quagga.
Format is correct when constructed.
Check in debugger @ bgp_updgrp_packet.c line 811 (stable/2.0)

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
@donaldsharp donaldsharp added this to the 2.0-rc1 milestone Jan 17, 2017
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
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
@louberger
Copy link
Member Author

fixed in #83

@eqvinox
Copy link
Contributor

eqvinox commented Jan 19, 2017

#83 merged - closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants