Recent posts

#1
German - Deutsch / Re: Wireguard Netz-zu-Netz Lan...
Last post by WallE - Today at 12:09:36 PM
Kurzer Nachtrag: Habe es hinbekommen...

Problem war anscheinend das ich da jedes mal den falschen Key kopiert hatte und es nicht gesehen habe.
Man kommt aber auch leicht durcheinander weil jeder Hersteller da seine Oberfläche und die Bezeichnungen etwas eigen hat.
#2
Maybe dnsmasq can do it. You can configure different RA pools on the same interface with different flags from what I can see.

But I never tested that.
#3
German - Deutsch / Re: Client IPv6 Adressen und D...
Last post by meyergru - Today at 11:48:51 AM
Genau. Man kann den bekannten EUI-64 Suffix angeben und das Interface, auf dem der Client hängt, für den Präfix.
#4
26.1, 26,4 Series / Re: With IPv6, how to get both...
Last post by dseven - Today at 11:46:15 AM
The OP stated why they don't want to disable privacy extensions too (for the GUAs, used for internet access).

I don't want to keep arguing about it, but I do think there's some merit in the OP's request. Whether there's enough demand for it to justify spending development effort on it, I'm not sure....
#5
If SLAAC is in play the addresses can be static too since they can be EUI-64 derived. SLAAC depends on the client configuration as well, like deactivating privacy extensions and other randomized SLAAC generation behavior, and only allow EUI-64 (or RFC 7217 stable addresses).

privacy/temporary addresses (RFC 4941 / RFC 8981) are entirely a host decision
#6
26.1, 26,4 Series / Re: With IPv6, how to get both...
Last post by dseven - Today at 11:19:39 AM
The OP's issue is that they want to use static ULAs in their firewall rules. If SLAAC is in play, the addresses are not static, and that model breaks. They want "managed" for the ULA prefix and "assisted" for the GUA prefix (on the same interface).
#7
The Router Advertisement config generation has some magic that has always been there and cannot be easily untangled anymore.

This means different settings for different prefixes on the same interface are indeed not possible.

But it's also not really needed most of the time, the most common setups can all be done:

A: GUAs + ULAs for all hosts
B: Only GUAs for all hosts
C: Only ULAs for all hosts

It also doesn't matter if hosts generate more than a single address for either GUA or ULA, it's common to have SLAAC and DHCPv6 addresses and privacy extensions. For me it doesn't make much sense trying to be smarter than necessary here.
#8
German - Deutsch / Re: Client IPv6 Adressen und D...
Last post by Maurice - Today at 10:46:03 AM
Das funktioniert auch mit SLAAC, da sich der Interface Identifier im Normalfall nicht ändert (Ausnahme: Stable Privacy / RFC 7217).

Das Präfix wird nicht vom WAN-Interface übernommen, sondern von dem LAN-Interface, an dem der Server hängt.

Und ja, das funktioniert mit dem normalen os-ddclient.
#9
26.7 Series / Re: IPS - unable to download r...
Last post by Karla - Today at 10:45:57 AM
I have run cleanup, connectivity, health and security.
No problems found.

When I try to do download the IPS rules, then it stops the download process immediately and not nothing happens then.

Should I reinstall and try to download the IPS rules ?
#10
26.1, 26,4 Series / Re: With IPv6, how to get both...
Last post by dseven - Today at 10:39:39 AM
Agreed that (at least arguably) the root issue is ISP policy, but very few of us here are in a position to be able to change that.

Looking at radvd, AdvAutonomous is set at the prefix level, so it should be possible to have a ULA VIP on an interface that does not get advertised for SLAAC (but can be used for DHCPv6), which is (I think) what the OP wants. I wonder if it could be done by adding a flag to the VIP (interface config) to say "[don't] use this for SLAAC", then have the radvd config generation set AdvAutonomous for the prefix accordingly. That seems less complicated than trying to handle all of it in the RA UI. Not sure how much appetite there'd be for something like this in the dev camp (Hi Cedrik!) though ;)