-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The third RC build of the 12.0-RELEASE release cycle is now available.
Installation images are available for:
o 12.0-RC3 amd64 GENERIC
o 12.0-RC3 i386 GENERIC
o 12.0-RC3 powerpc GENERIC
o 12.0-RC3 powerpc64 GENERIC64
o 12.0-RC3 powerpcspe MPC85XXSP
As someone who controls both ends of the link (runs the ISP, has service
from the ISP), so far (a bit out of laziness) I have the following
solution...
Now... of note is that we statically assign addresses. This is not just
being nice, but being practical. We deal out IPv4 addresses vi IPCP, but
## Bjoern A. Zeeb (bzeeb-li...@lists.zabbadoz.net):
> No, IPV6CP, to my very best 15 year old memory only negotiates the
> interface identifiers, which are used to generate the link-local addresses.
Ah, you're right - it's IPV6CP-then-NDP, not "IPV6CP or NDP".
I got ahead of the protocol...
Rega
On 11/30/2018 7:12 AM, O. Hartmann wrote:
>
> For IPv6, I only see my local linklocal address, fe80::...
>
> Checking the log of ppp (/var/log/ppp.log), there is also a fe80::
> linklocal address
> assigned to the variable HISADDR. Somehow, the tun0 never obtains a
> IPv6 aprefix so far.
>
> Can so
On 30 Nov 2018, at 15:59, Christoph Moench-Tegeder wrote:
> ## O. Hartmann (ohartm...@walstatt.org):
>
>> As far as I know, with the IPv4 stack a IPv4 address is obtained
>> automatically, so I would expect the same for IPv6.
>
> The fun with "automatically" is that there's more than one way...
>
## O. Hartmann (ohartm...@walstatt.org):
> As far as I know, with the IPv4 stack a IPv4 address is obtained
> automatically, so I would expect the same for IPv6.
The fun with "automatically" is that there's more than one way...
DHCPv6 and NDP (IPV6 Neighbour Discovery Protocol/Router Solicitation
On Fri, Nov 30, 2018 at 01:12:32PM +0100, O. Hartmann wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> My ISP is offering IPv6 only "as an experimental feature", so I had to ask to
> enable the
> IPv6 stack on my connection. I'm using FreeBSD 12-STABLE as the basis for a
> router/fi
On Wed, 28 Nov 2018 19:39:21 +0100
"O. Hartmann" wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Am Wed, 28 Nov 2018 15:00:42 +0100
> Emmanuel Vadot schrieb:
>
> > Hi,
> >
> > On Wed, 28 Nov 2018 10:51:11 +0100
> > "O. Hartmann" wrote:
> >
> > > -BEGIN PGP SIGNED MESSAGE
Hi,
> On 30 Nov 2018, at 12:12, O. Hartmann wrote:
>
> Signed PGP part
> My ISP is offering IPv6 only "as an experimental feature", so I had to ask to
> enable the
> IPv6 stack on my connection. I'm using FreeBSD 12-STABLE as the basis for a
> router/firewall/PBX system, FreeBSD's onboard ppp c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
My ISP is offering IPv6 only "as an experimental feature", so I had to ask to
enable the
IPv6 stack on my connection. I'm using FreeBSD 12-STABLE as the basis for a
router/firewall/PBX system, FreeBSD's onboard ppp client is performing the
uplink a
10 matches
Mail list logo