Re: [Dnsmasq-discuss] Multiple Shared Networks?
Yes, we are using multiple shared-network statements with v2.87 and this is working as we expect. Thanks for your help. -Rich On Wed, Dec 14, 2022 at 11:44 AM Geert Stappers wrote: > On Mon, Oct 31, 2022 at 08:52:29PM +, Simon Kelley wrote: > > On 31/10/2022 14:15, Rich Otero via Dnsmasq-discuss wrote: > > > My dnsmasq server provides DHCP for more than one hundred subnets like > this: > > > > > > dhcp-range=set:172.18.14.0-24,172.18.14.0,static,255.255.255.0 > > > dhcp-option=tag:172.18.14.0-24,option:router,172.18.14.1 > > > > > > dhcp-range=set:172.18.15.0-24,172.18.15.0,static,255.255.255.0 > > > dhcp-option=tag:172.18.15.0-24,option:router,172.18.15.1 > > > > > > dhcp-range=set:172.18.16.0-24,172.18.16.0,static,255.255.255.0 > > > dhcp-option=tag:172.18.16.0-24,option:router,172.18.16.1 > > > > > > > > > I need to disconnect the dnsmasq server from each of those subnets > while > > > continuing to provide reserved leases for clients in them, so I > recently > > > upgraded from v2.75 to v2.87 to gain the shared-network option. I am > > > currently testing the change on one subnet and it is working as > > > expected: > > > > > > dhcp-range=set:172.18.15.0-24,172.18.15.0,static,255.255.255.0 > > > dhcp-option=tag:172.18.15.0-24,option:router,172.18.15.1 > > > shared-network=enp2s0,172.18.15.0 > > > > > > > > > Ultimately, I will need the shared-network behavior for every subnet. > Is > > > it allowed to have multiple shared-network directives in the config? > > > > Yes, there are no limits on the number of shared-network statements. > > > > Simon. > > > > > -Rich > > Hi Rich, > Hi Co-workers of Rich, > > > Please consider a "Yes, the multiple shared-network statements work fine" > or something like "Yeah, dnsmasq is doing what I expected from it!" > > > Groeten > Geert Stappers > -- > Silence is hard to parse > ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
Re: [Dnsmasq-discuss] Multiple Shared Networks?
On Mon, Oct 31, 2022 at 08:52:29PM +, Simon Kelley wrote: > On 31/10/2022 14:15, Rich Otero via Dnsmasq-discuss wrote: > > My dnsmasq server provides DHCP for more than one hundred subnets like this: > > > > dhcp-range=set:172.18.14.0-24,172.18.14.0,static,255.255.255.0 > > dhcp-option=tag:172.18.14.0-24,option:router,172.18.14.1 > > > > dhcp-range=set:172.18.15.0-24,172.18.15.0,static,255.255.255.0 > > dhcp-option=tag:172.18.15.0-24,option:router,172.18.15.1 > > > > dhcp-range=set:172.18.16.0-24,172.18.16.0,static,255.255.255.0 > > dhcp-option=tag:172.18.16.0-24,option:router,172.18.16.1 > > > > > > I need to disconnect the dnsmasq server from each of those subnets while > > continuing to provide reserved leases for clients in them, so I recently > > upgraded from v2.75 to v2.87 to gain the shared-network option. I am > > currently testing the change on one subnet and it is working as > > expected: > > > > dhcp-range=set:172.18.15.0-24,172.18.15.0,static,255.255.255.0 > > dhcp-option=tag:172.18.15.0-24,option:router,172.18.15.1 > > shared-network=enp2s0,172.18.15.0 > > > > > > Ultimately, I will need the shared-network behavior for every subnet. Is > > it allowed to have multiple shared-network directives in the config? > > Yes, there are no limits on the number of shared-network statements. > > Simon. > > > -Rich Hi Rich, Hi Co-workers of Rich, Please consider a "Yes, the multiple shared-network statements work fine" or something like "Yeah, dnsmasq is doing what I expected from it!" Groeten Geert Stappers -- Silence is hard to parse ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
[Dnsmasq-discuss] Error when using nftset
I receive the following error:
nftset inet filter filter google Error: Could not resolve service:
Servname not supported for ai_socktype
This happens, when dnsmasq tries to add an IP entry into nft map.
The set was created in this way:
nft add map inet filter google \{ type inet_service: ipv4_addr\; \}
OS: Debian 11, but picket dnsmasq, dnsmasq-base, dnsmasq-utils and
netbase manually from debian "bookworm" (upcoming version), to get the
v2.87 on my Raspberry Pi.
Updating netbase from bookworm (which contains /etc/services) didn't help.
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
Re: [Dnsmasq-discuss] Error when using nftset
I got it working, now. Accidentally, I used "map" instead of "set". A
better error message would be helpful.
Correct: nft add set inet filter google { type ipv4_addr; }
On Wed, 14 Dec 2022 at 14:31, Sebastian Loncar
wrote:
>
> I receive the following error:
>
> nftset inet filter filter google Error: Could not resolve service:
> Servname not supported for ai_socktype
>
> This happens, when dnsmasq tries to add an IP entry into nft map.
> The set was created in this way:
>
> nft add map inet filter google \{ type inet_service: ipv4_addr\; \}
>
> OS: Debian 11, but picket dnsmasq, dnsmasq-base, dnsmasq-utils and
> netbase manually from debian "bookworm" (upcoming version), to get the
> v2.87 on my Raspberry Pi.
>
> Updating netbase from bookworm (which contains /etc/services) didn't help.
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
