- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
IPv6 BGP over IPv4 IPSEC
I have two sites, A(FGT60E) and B (FGT60D).
They are connected via IPSEC Tunnel.
The IPv4 LAN subnets for both sites are advertised via BGP and working.
I recently introduced IPv6 on both sites.
IPv6 is activated on BGP. "network6" is also configured to advertise under BGP configuration.
I am able to see the IPv6 subnets being advertise on both Fortigates bgp table. However, the IPv6 received route is not in the routing table...
Site A:
BGP table version is 12, local router ID is 10.10.22.1 Status codes: s suppressed, d damped, h history, * valid, > best, i - internal, S Stale Origin codes: i - IGP, e - EGP, ? - incomplete Network Next Hop Metric LocPrf Weight RouteTag Path [style="background-color: #ffff00;"]*> fd01:101:101:13::/64[/style] ::ffff:a0d:2 0 0 0 64013 i *> fd01:101:101:ab00::/64 100 32768 0 i Total number of prefixes 2
ROUTING TABLE:
IPv6 Routing Table Codes: K - kernel route, C - connected, S - static, R - RIP, O - OSPF, IA - OSPF inter area N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2 E1 - OSPF external type 1, E2 - OSPF external type 2 i - IS-IS, B - BGP * - candidate default
Timers: Uptime
C ::1/128 via ::, root, 19:10:28 C fd01:101:101:ab00::/64 via ::, internal, 17:18:37 C fe80::/64 via ::, internal, 17:52:44 K ff00::/8 via ::, tun_fgfm, 19:10:12
Site B:
BGP table version is 14, local router ID is 10.13.0.2 Status codes: s suppressed, d damped, h history, * valid, > best, i - internal, S Stale Origin codes: i - IGP, e - EGP, ? - incomplete Network Next Hop Metric LocPrf Weight RouteTag Path [style="background-color: #ffff00;"]*> fd01:101:101:13::/64[/style] 100 32768 0 i *> fd01:101:101:ab00::/64 ::ffff:a0d:1 0 0 0 64001 i Total number of prefixes 2
ROUTING TABLE:
IPv6 Routing Table Codes: K - kernel route, C - connected, S - static, R - RIP, O - OSPF, IA - OSPF inter area N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2 E1 - OSPF external type 1, E2 - OSPF external type 2 i - IS-IS, B - BGP * - candidate default
Timers: Uptime
C ::1/128 via ::, root, 19:25:35 C fd01:101:101:13::/64 via ::, internal, 14:55:10 C fe80::/10 via ::, internal, 14:55:10
What seems to be the issue??
- Labels:
-
6.0
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
did you get any further with this?
im doing some ipv6 configuration over a BGP IPv4 neighbourship relation
did you check your routing database? for me the advertised route is there but it is inactive, also the via doesn't make sense there
FG-60E-01 # get router info6 routing-table database IPv6 Routing Table Codes: K - kernel route, C - connected, S - static, R - RIP, O - OSPF, IA - OSPF inter area N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2 E1 - OSPF external type 1, E2 - OSPF external type 2 i - IS-IS, B - BGP > - selected route, * - FIB route, p - stale info Timers: Uptime
C *> ::1/128 via ::, root, 14:07:07 B fde4:8dba:82e1:193::/64 [20/0] via ::ffff:2424:d6b2 inactive, 00:02:55 C *> fde4:8dba:82e1:1111::/64 via ::, wan1, 01:13:14 C *> fe80::/10 via ::, wan1, 01:13:14
what do you mean with "IPv6 is activated on BGP."
i tried with IPv6 neighbourship in parallel, but that seems to get less far. need to try that again with IPv6 only.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
tried with only IPv6 neighbours and it works fine, both for IPv4 and IPv6.
then found this knowledge base article, that is probably the way to go:
https://kb.fortinet.com/kb/microsites/search.do?cmd=displayKC&docType=kc&externalId=FD37481
