Rogier Krieger wrote:
On Sun, Feb 8, 2009 at 02:09, Graeme Lee <gra...@omni.net.au> wrote:
The bgpd log shows this:
bgpd: send_rtmsg: action 1, prefix 2001:dc8:c000::/36: Network is
unreachable
bgpd: send_rtmsg: action 1, prefix 2a01:a8::/32: Network is unreachable
for every network received via my peer.
Are there intermediate hops that you receive from the peer but cannot
reach? If your nexthop is unreachable, that may explain the message.
If you go back far enough in the logs (before the first prefixes you
receive, the log may provide more insight as well as I don't know how
many peers you have/prefixes you get).
Nope. Here's the first few lines from bgpctl show ip bgp inet6
flags: * = Valid, > = Selected, I = via IBGP, A = Announced
origin: i = IGP, e = EGP, ? = Incomplete
flags destination gateway lpref med aspath origin
*> 2001::/32 2001:470:17:7f::1 100 0 6939 12859 i
*> 2001:200::/32 2001:470:17:7f::1 100 0 6939 2500 i
*> 2001:200:136::/48 2001:470:17:7f::1 100 0 6939 2516 7660
9367 i
*> 2001:200:600::/40 2001:470:17:7f::1 100 0 6939 2516 7667 i
*> 2001:200:900::/40 2001:470:17:7f::1 100 0 6939 2516 7660 i
*> 2001:200:a000::/35 2001:470:17:7f::1 100 0 6939 3257 2497
4690 i
*> 2001:200:c000::/35 2001:470:17:7f::1 100 0 6939 2500 23634 i
*> 2001:200:e000::/35 2001:470:17:7f::1 100 0 6939 4635 7660 i
*> 2001:208::/32 2001:470:17:7f::1 100 0 6939 23911 9800
38035 7610 i
*> 2001:218::/32 2001:470:17:7f::1 100 0 6939 2914 i
*> 2001:220::/35 2001:470:17:7f::1 100 0 6939 2516 7660
9270 i
*> 2001:220:2000::/35 2001:470:17:7f::1 100 0 6939 2516 7660
9270 38128 i
*> 2001:220:8000::/33 2001:470:17:7f::1 100 0 6939 2516 7660
9270 38128 i
2001:470:17:7f::1 is my bgp peer from hurricane. The bgp table looks
fine. It just doesn't translate to the kernel routing table. ergo, I
cannot see or be seen. my prefix is advertised fine (2400:6800::/32)
I can talk to and directly ping6 2001:470:17:7f::1
Adding static routes works (eg a default). It's just that bgpd isn't
translating what it knows into the kernel.
A clue to what I'm missing would be really appreciated.
Other than checking the nexthop above, it'll help to include your
network layout (what interfaces, uplink, addresses), bgpd
configuration and a non-chopped dmesg.
Dmesg was there to demonstrate I really was running -current and not
something from somewhere random.
Network layout is somewhat complicated. 1 x ebgp and 1 x ibgp session
receive ipv4 world tables. Gif tunnel to a hurricane router in Hong
Kong. I'm receiving ipv6 world bgp tables from this peer. Connectivity
to the peer is fine. Just can't get past it.
I can see that my prefix is announced via looking glasses. I'm
receiving about 1.6k prefixes from hurricane.
# bgpctl show ip bgp sum
Neighbor AS MsgRcvd MsgSent OutQ Up/Down
State/PrfRcvd
HurricaneHK 6939 3220 1428 0 11:52:11 1588
Optus Peer 10105 104321 43663 0 11:58:08 222487
NextGen 38809 78041 1439 0 11:58:08 274913
complete restart of bgpd shows this:
Feb 8 23:43:47 gw-nexgen bgpd[23344]: neighbor 2001:470:17:7f::1
(HurricaneHK): state change Connect -> OpenSent, reason: Connection opened
Feb 8 23:43:47 gw-nexgen bgpd[23344]: neighbor 2001:470:17:7f::1
(HurricaneHK): state change OpenSent -> OpenConfirm, reason: OPEN
message received
Feb 8 23:43:47 gw-nexgen bgpd[23344]: neighbor 2001:470:17:7f::1
(HurricaneHK): state change OpenConfirm -> Established, reason:
KEEPALIVE message received
Feb 8 23:44:13 gw-nexgen bgpd[4481]: nexthop 2001:470:17:7f::1 now
valid: directly connected
Feb 8 23:44:13 gw-nexgen bgpd[4481]: send_rtmsg: action 1, prefix
2a01:7b0::/32: Network is unreachable
Feb 8 23:44:13 gw-nexgen bgpd[4481]: send_rtmsg: action 1, prefix
2404:1b0::/32: Network is unreachable
Feb 8 23:44:13 gw-nexgen bgpd[4481]: send_rtmsg: action 1, prefix
2400:3000::/32: Network is unreachable
etc etc for all 1.6k prefixes
Hope it helps,
Rogier
