Thanks Robert, I don't think the setup you're describing fits my situation. In particular, if I understand things correctly, usage of the router advertisement mode isn't correct if the node in question (my intended DHCP server host) isn't a router. For my network, I have a separate router node (specifically a PFSense box) that's receiving the initial prefix delegation from the ISP and providing the LAN's RAs. While it technically *can* run a DHCPv6 server in addition to handling the RAs, I didn't want to do this for two reasons: 1) I already had a fairly detailed setup of DNS/IP assignments on my legacy IPv4 configured dnsmasq server and 2) the PFSense interface didn't make it seem very easy to setup and manage a similar configuration.
So my hope was to split the responsibility (which seems within spec, as far as I can tell from reading RFC documentation) between two nodes - one, a router, handling the RAs and one, a non-router, handling the DHCP assignments. That all said... I'd love to understand how your setup using dhcpcd differs from my setup within FreeBSD using rtsold to acquire the interface's ip. Does the usage of dhcpcd not mark the address as autoconfigured? Router advertisements aside, I feel like my big issue at the moment is getting an address, automatically, on the jail's interface that isn't considered "automatically configured", since that is the sticky point when it comes to dnsmasq's behavior regarding using a constructor in the dhcp-range command. Can you post the output of your interface's setup so I can compare it to the one I posted? As for the ISP issue.... yeah. That's becoming pretty annoying. It's "static enough" I suppose, in the sense that it's not changing every few hours... but it's changing often enough that I don't really want to reconfigure stuff each time. Particularly since I've been trying to do things like host software for my friends (notably a roleplaying virtual tabletop server). In theory, having the ISP provide globally routable IPs is great - get things configured, set the IP up with my external DNS provider and all is good... only then the prefix changes a few days later and everything breaks until I go around updating things. Getting my local network under control with a potentially changing prefix is step one in wrangling this - once I can consistently reference internal addresses by internal DNS for the local firewall, I can start looking into DynDNS for my external domain updates... -- Nathan On Fri, Jan 3, 2025 at 12:39 AM Robert Sharp <sysad...@osburn-sharp.uk> wrote: > > On 03/01/2025 04:32, Nathan Mitchell wrote: > > Is there a way I can accomplish this with dnsmasq? Or am I running > > into a fundamental design issue with the IPv6 architecture where I'm > > not supposed to do this? And if so, what is the replacement for the > > way things worked before in IPv4 land? Because this doesn't seem too > > crazy to want to do in my mind. > > > > Thanks! > > -- Nathan > > Hi Nathan, > > I think that I have this working fine with the following: > > # IPv6 stuff > enable-ra > > dhcp-range=::FF,::400,constructor:enp3s0,ra-names,24h > dhcp-range=vlan0@enp3s0,::2,::400,constructor:vlan0,ra-names,24h > > dhcp-host=fc:ab:13:c8:90:3e,server,[::5] > dhcp-host=... > > I use dhcpcd to obtain and delegate a prefix to each interface and > dnsmasq hands out addresses to the lan and vlan and resolves names for > my server(s). Everything has been working fine for a long time now but > it took quite a bit of fiddling to get it working. > > Interesting that your ISP only provides dynamic prefixes. I thought the > whole point of IPv6 was to provide an address space large enough to > avoid that. Perhaps they are charging more for static addresses? I have > a static /48 prefix from my ISP which is just great for the 6 trillion > devices on my network. But I have been careful not to hard-wire the > static address into anything so it could be dynamic for all I care. > > Robert > > > _______________________________________________ > Dnsmasq-discuss mailing list > Dnsmasq-discuss@lists.thekelleys.org.uk > https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss >
_______________________________________________ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
