Ok, think I figured it out.
My core problem was that I was assigning prefixes manually in rad.conf,
then assigning each interface an address *in the same prefix*. This
created some kind of conflictâthe nature of which I still don't fully
understand.
This was the key line I missed in
> To reach the internet from ULA addresses you'll need NAT.
> Alternatively use *both* global and ULA prefixes in rad.conf (or I
> think you can use auto prefix). But I don't think you've got that far
> yet.
I was planning on using the ULAs for internal addressing only, and doing
port-forwarding
On 2024-03-25, Evan Sherwood wrote:
>>> interface igc1 {
>>> prefix fdbf:e79a:8e3e::/48
>>
>> lesser operating systems will refuse to form autoconf addresses if the
>> prefix length is not 64.
>
> Thanks, this was helpful. I got addresses allocated on client
> I can ping6 back to my router using the IPv6 address in the prefix
> delegation from my ISP, but I cannot seem to do the same for the
> addresses in my ULA prefix.
I can see neighbor solicitation requests from my clients for the ULA
gateway address, but I see no neighbor advertisements sent in
>> interface igc1 {
>> prefix fdbf:e79a:8e3e::/48
>
> lesser operating systems will refuse to form autoconf addresses if the
> prefix length is not 64.
Thanks, this was helpful. I got addresses allocated on client machines,
but they don't seem routable.
I can
On 2024-03-24 23:33 +01, Evan Sherwood wrote:
> I'm not sure how to configure rad (or if rad is the right program) to
> help have my devices autoconfigured ULA addresses in a given prefix
> (generated from https://www.unique-local-ipv6.com).
>
> I am debugging a new ISP and need to switch between
I'm not sure how to configure rad (or if rad is the right program) to
help have my devices autoconfigured ULA addresses in a given prefix
(generated from https://www.unique-local-ipv6.com).
I am debugging a new ISP and need to switch between two ISPs without
disrupting communication between my
7 matches
Mail list logo
