Adding default IPv6 route fails on 6.1

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
12 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Adding default IPv6 route fails on 6.1

Sterling Archer
Hello everyone.

After upgrading to 6.1 about an hour ago, I noticed that I didn't have an
IPv6 connection
anymore.

I use dhcpcd over a pppoe session, which worked fine in 6.0-stable. The
problem seems to
be a failure to add a default inet6 route on the pppoe device. I see this
error in the dmesg
console log:

"add net default: gateway fe80::: No route to host"

Did I miss something in the changelog, or is this a bug?


Here's the contents of my hostname.pppoe0:

[sven@puffy ~]$ cat /etc/hostname.pppoe0
description "pppoe session over vlan6"
inet 0.0.0.0 255.255.255.255 NONE mtu 1500 \
        pppoedev vlan6 authproto pap \
        authname 'kennyloggins' authkey 'dangerzone!'
dest 0.0.0.1
inet6 eui64
!/sbin/route add default -ifp pppoe 0.0.0.1
!/sbin/route add -inet6 default -ifp pppoe0 fe80::

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Adding default IPv6 route fails on 6.1

Stefan Sperling-5
On Wed, Apr 12, 2017 at 01:20:20AM +0200, Sterling Archer wrote:

> Hello everyone.
>
> After upgrading to 6.1 about an hour ago, I noticed that I didn't have an
> IPv6 connection
> anymore.
>
> I use dhcpcd over a pppoe session, which worked fine in 6.0-stable. The
> problem seems to
> be a failure to add a default inet6 route on the pppoe device. I see this
> error in the dmesg
> console log:
>
> "add net default: gateway fe80::: No route to host"
>
> Did I miss something in the changelog, or is this a bug?
>
>
> Here's the contents of my hostname.pppoe0:
>
> [sven@puffy ~]$ cat /etc/hostname.pppoe0
> description "pppoe session over vlan6"
> inet 0.0.0.0 255.255.255.255 NONE mtu 1500 \
>         pppoedev vlan6 authproto pap \
>         authname 'kennyloggins' authkey 'dangerzone!'
> dest 0.0.0.1
> inet6 eui64
> !/sbin/route add default -ifp pppoe 0.0.0.1
> !/sbin/route add -inet6 default -ifp pppoe0 fe80::
>

Can you add a default route manually once the pppoe session is up or
does that not work either?

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Adding default IPv6 route fails on 6.1

Dimitris Papastamos
In reply to this post by Sterling Archer
On Wed, Apr 12, 2017 at 01:20:20AM +0200, Sterling Archer wrote:

> Hello everyone.
>
> After upgrading to 6.1 about an hour ago, I noticed that I didn't have an
> IPv6 connection
> anymore.
>
> I use dhcpcd over a pppoe session, which worked fine in 6.0-stable. The
> problem seems to
> be a failure to add a default inet6 route on the pppoe device. I see this
> error in the dmesg
> console log:
>
> "add net default: gateway fe80::: No route to host"
>
> Did I miss something in the changelog, or is this a bug?
>
>
> Here's the contents of my hostname.pppoe0:
>
> [sven@puffy ~]$ cat /etc/hostname.pppoe0
> description "pppoe session over vlan6"
> inet 0.0.0.0 255.255.255.255 NONE mtu 1500 \
>         pppoedev vlan6 authproto pap \
>         authname 'kennyloggins' authkey 'dangerzone!'
> dest 0.0.0.1
> inet6 eui64
> !/sbin/route add default -ifp pppoe 0.0.0.1
> !/sbin/route add -inet6 default -ifp pppoe0 fe80::

Try this instead:

!/sbin/route add -inet6 default -ifp pppoe0 fe80::%pppoe0

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Adding default IPv6 route fails on 6.1

Sterling Archer
In reply to this post by Stefan Sperling-5
On Wed, Apr 12, 2017 at 8:50 AM, Stefan Sperling <[hidden email]> wrote:

> On Wed, Apr 12, 2017 at 01:20:20AM +0200, Sterling Archer wrote:
> > Hello everyone.
> >
> > After upgrading to 6.1 about an hour ago, I noticed that I didn't have an
> > IPv6 connection
> > anymore.
> >
> > I use dhcpcd over a pppoe session, which worked fine in 6.0-stable. The
> > problem seems to
> > be a failure to add a default inet6 route on the pppoe device. I see this
> > error in the dmesg
> > console log:
> >
> > "add net default: gateway fe80::: No route to host"
> >
> > Did I miss something in the changelog, or is this a bug?
> >
> >
> > Here's the contents of my hostname.pppoe0:
> >
> > [sven@puffy ~]$ cat /etc/hostname.pppoe0
> > description "pppoe session over vlan6"
> > inet 0.0.0.0 255.255.255.255 NONE mtu 1500 \
> >         pppoedev vlan6 authproto pap \
> >         authname 'kennyloggins' authkey 'dangerzone!'
> > dest 0.0.0.1
> > inet6 eui64
> > !/sbin/route add default -ifp pppoe 0.0.0.1
> > !/sbin/route add -inet6 default -ifp pppoe0 fe80::
> >
>
> Can you add a default route manually once the pppoe session is up or
> does that not work either?
>

Sorry, I should have mentioned that, it fails when you attempt to
manually add it too.

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Adding default IPv6 route fails on 6.1

Sterling Archer
In reply to this post by Dimitris Papastamos
On Wed, Apr 12, 2017 at 9:59 AM, Dimitris Papastamos <[hidden email]> wrote:

> Try this instead:
>
> !/sbin/route add -inet6 default -ifp pppoe0 fe80::%pppoe0
>

That did the trick, dhcpcd is receiving router advertisments from
my ISP now. Thanks, Dimitris.

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Adding default IPv6 route fails on 6.1

Stuart Henderson
In reply to this post by Sterling Archer
On 2017-04-12, Sterling Archer <[hidden email]> wrote:

> On Wed, Apr 12, 2017 at 8:50 AM, Stefan Sperling <[hidden email]> wrote:
>
>> On Wed, Apr 12, 2017 at 01:20:20AM +0200, Sterling Archer wrote:
>> > Hello everyone.
>> >
>> > After upgrading to 6.1 about an hour ago, I noticed that I didn't have an
>> > IPv6 connection
>> > anymore.
>> >
>> > I use dhcpcd over a pppoe session, which worked fine in 6.0-stable. The
>> > problem seems to
>> > be a failure to add a default inet6 route on the pppoe device. I see this
>> > error in the dmesg
>> > console log:
>> >
>> > "add net default: gateway fe80::: No route to host"
>> >
>> > Did I miss something in the changelog, or is this a bug?
>> >
>> >
>> > Here's the contents of my hostname.pppoe0:
>> >
>> > [sven@puffy ~]$ cat /etc/hostname.pppoe0
>> > description "pppoe session over vlan6"
>> > inet 0.0.0.0 255.255.255.255 NONE mtu 1500 \
>> >         pppoedev vlan6 authproto pap \
>> >         authname 'kennyloggins' authkey 'dangerzone!'
>> > dest 0.0.0.1
>> > inet6 eui64
>> > !/sbin/route add default -ifp pppoe 0.0.0.1
>> > !/sbin/route add -inet6 default -ifp pppoe0 fe80::
>> >
>>
>> Can you add a default route manually once the pppoe session is up or
>> does that not work either?
>>
>
> Sorry, I should have mentioned that, it fails when you attempt to
> manually add it too.

This was due to a change in how the routing table is handled, I'm hoping
it is temporary because it makes things awkward with dynamic addresses.
It's not so bad for v6 where you can use any address in thr correct scope;
v4 is worse as it means you either have to rely on the horrible 0.0.0.1
hack or look up the remote address when you're adding a route for pppoe.

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Adding default IPv6 route fails on 6.1

Alexander Bochmann
In reply to this post by Sterling Archer
...on Wed, Apr 12, 2017 at 11:12:28AM +0200, Sterling Archer wrote:
 > On Wed, Apr 12, 2017 at 9:59 AM, Dimitris Papastamos <[hidden email]> wrote:
 > > Try this instead:
 > > !/sbin/route add -inet6 default -ifp pppoe0 fe80::%pppoe0
 > That did the trick, dhcpcd is receiving router advertisments from
 > my ISP now. Thanks, Dimitris.

On that note - there's several cloud VM providers out there
who assign a IPv6 network to customer VMs and then expect that
fe80::1 is used as default gateway.

In those cases, an interface tag is required too, as the
system will usually have at least one other link-local
network on the lo0 interface (that's not new in 6.1)...

So, depending on the interface name, something like this works:

 > # fgrep fe80 /etc/mygate
 > fe80::1%vio0

Alex.

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Adding default IPv6 route fails on 6.1

Harald Dunkel-5
In reply to this post by Sterling Archer
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi Sterling,

On 04/12/17 01:20, Sterling Archer wrote:
> Hello everyone.
>
> After upgrading to 6.1 about an hour ago, I noticed that I didn't have an IPv6 connection anymore.
>
> I use dhcpcd over a pppoe session, which worked fine in 6.0-stable.


I'd love to see your dhcpcd.conf.


Regards
Harri

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEH2V614LbR/u1O+a1Cp4qnmbTgcsFAljv6pgACgkQCp4qnmbT
gctozwgAiYbeVffl4b5NM4HTfgNxHa/nivt/EZb6PS5wn7mlxQDDSkCJpXju+8W6
ZfXOCM8v9T3D8j7aDp+r+rbdriFZykysV84jH7Dkb5AA/BgP0YslOmsx7fdAUqO1
MyNLQk+WykKN+E0fjJbSp9eAOd7mGjIan6oMavJs+3SyRxSUyO5NYZT58NvQ/Glb
dQNJI8rV+JMfLEow9k3l44/S8hcPMwVCYibsFBAnV1vvqKvsAWdNdGPTxMC4qG6f
WjSpS9kKkmPXr4Y7O3Rb1du7emlv8nc6vXtn0Mvonegeq2wkXPMRUuyZO6vhWVwn
E36knEvL6FJ1Q8/IirW0Dde3TY8MTA==
=HUdz
-----END PGP SIGNATURE-----

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Adding default IPv6 route fails on 6.1

Stuart Henderson
On 2017-04-13, Harald Dunkel <[hidden email]> wrote:

>
> Hi Sterling,
>
> On 04/12/17 01:20, Sterling Archer wrote:
>> Hello everyone.
>>
>> After upgrading to 6.1 about an hour ago, I noticed that I didn't have an IPv6 connection anymore.
>>
>> I use dhcpcd over a pppoe session, which worked fine in 6.0-stable.
>
>
> I'd love to see your dhcpcd.conf.

Mine is in the pkg-readme.


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Adding default IPv6 route fails on 6.1

Harald Dunkel-5
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 04/18/17 17:05, Stuart Henderson wrote:
>
> Mine is in the pkg-readme.
>
>

A pkg-readme? Is this included in the binary package?

# find / -iname \*readme\* -print | grep -i dhcp
# echo $?
1


Regards
Harri

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEH2V614LbR/u1O+a1Cp4qnmbTgcsFAlj3CA8ACgkQCp4qnmbT
gcv65Qf/S7weEvhxdy7OTXdOd5Y+iDq1X1jkvQzW7j5d8DRriOjbTTR+3lNbc6vW
JNrgvH0LUGiUQzbc7g2rFB+ISHBgPpJfFyvhErOawZgDVvY5dhXeuXQ4nYYWAM7g
/MKBW6Rjy3WV+24YqEp0QxSCbC2KZfHpt5a6lkZDAhDsOaccLWiGU5VJQIzy76z2
O+wAC/xuXIcPBgCC53dXiRZzjUe8coxnl0Egi2DfCOGxyAbuziMC/hdFob1Hs+/h
tnjyHBq4+u5fnpl/AHAi3/qUEtqyKHk8dT7WpGQceypLYSDU/m5N30oERXpAVUfH
HvpjAexQgCE8A4aghOoX06Db1B1r4Q==
=JPo5
-----END PGP SIGNATURE-----

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Adding default IPv6 route fails on 6.1

Marc Peters-3
Am 04/19/17 um 08:47 schrieb Harald Dunkel:
> On 04/18/17 17:05, Stuart Henderson wrote:
>
>> Mine is in the pkg-readme.
>
>
>
> A pkg-readme? Is this included in the binary package?

Try

$ less /usr/local/share/doc/pkg-readmes/dhcpcd-6.11.5


signature.asc (817 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Adding default IPv6 route fails on 6.1

Stuart Henderson
In reply to this post by Harald Dunkel-5
On 2017-04-19, Harald Dunkel <[hidden email]> wrote:
>
> On 04/18/17 17:05, Stuart Henderson wrote:
>>
>> Mine is in the pkg-readme.
>>
>>
>
> A pkg-readme? Is this included in the binary package?

Yes - pkg_add should have drawn your attention to it:

# pkg_add dhcpcd
dhcpcd-6.11.5: ok
The following new rcscripts were installed: /etc/rc.d/dhcpcd
See rcctl(8) for details.
Look in /usr/local/share/doc/pkg-readmes for extra documentation.


Loading...