Hello Samuel, On 25/10/15(Sun) 18:20, Samuel Thibault wrote: > >Synopsis: bgp route issue on inet6 over gif > >Category: system > >Environment: > System : OpenBSD 5.8 > Details : OpenBSD 5.8 (GENERIC.MP) #1236: Sun Aug 16 02:31:04 MDT > 20 > 15 > > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compi > le/GENERIC.MP > > Architecture: OpenBSD.amd64 > Machine : amd64 > > >Description: > After an upgrade to 5.8, our v6 routes stopped working: > $ ping6 people.debian.org > ping6: sendmsg: No route to host > ping6: wrote 2001:41c8:1000:21::21:30 32 chars, ret=-1 > > >How-To-Repeat: > We first have a gif tunnel with HE.net, using this configuration > (as found in various websites): > > # cat /etc/hostname.gif0 > tunnel 1.1.1.1 216.66.84.50 > inet6 alias 2001:470:11:96::2 128 > inet6 dest 2001:470:11:96::1 > > Here is the result in ifconfig: > > # ifconfig gif0 > gif0: flags=8151<UP,POINTOPOINT,RUNNING,PROMISC,MULTICAST> mtu 1280 > priority: 0 > groups: gif egress > tunnel: inet 1.1.1.1 -> 216.66.84.50 > inet6 fe80::abcd:abff:fecd:abcd%gif0 -> prefixlen 64 scopeid > 0x15 > inet6 2001:470:11:96::2 -> 2001:470:11:96::1 prefixlen 128 > Could you also send me the output of "netstat -rnf inet6" at this point, before starting bgpd?
> >Fix: > I changed the gif0 configuration to this (which looks saner to > me, actually): > > # cat /etc/hostname.gif0 > tunnel 1.1.1.1 216.66.84.50 > inet6 2001:470:11:96::2/126 > > So that the ifconfig looks like that: > > # ifconfig gif0 > gif0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1280 > priority: 0 > groups: gif > tunnel: inet 1.1.1.1 -> 216.66.84.50 > inet6 fe80::abcd:abff:fecd:abcd%gif0 -> prefixlen 64 scopeid > 0x1b > inet6 2001:470:11:96::2 -> prefixlen 126 > > and thus we get "connected" as gateway in BGP: Same thing in this case. I'd like to know if the route created by the kernel are not confusing bgpd(8). Thanks, Martin
