Add cpe-id option in DHCP-DNS section

Mile-Lile · October 24, 2024, 6:11pm

I explained everything here

brada4 · October 24, 2024, 6:16pm

And what action you want to be performed here? Add option editing init script while waiting for your pull request to dnsmasq to roll around.
Pait providers provide sasl/mtls on encrypted connections configured someplace else.

Mile-Lile · October 24, 2024, 6:34pm

not sure that I undestand you... I need something like config dnsmasq option add-cpe-id 'ls2458' from uci, or in the GUI field in DHCP and DNS / Forwards where I can enter some value that will be forwarded upstream to my DNS ISP (e.g. NextDNS)...

brada4 · October 24, 2024, 6:39pm

You have to characterize option you need, or at least provide guide from provider where they say it. No crystal ball here.

brada4 · October 24, 2024, 6:45pm

Mile-Lile · October 24, 2024, 6:51pm

this is link from nextdns github wiki

but real config examples they have for every individual on setup page... it is different for e.g. me and you... my looks like this:

and I know about luci-app-nextdns sasl/mtls app... I use it... but after lastnight snapshot update it is not working... I suspect this commit broke something... I get

and if I had this add-cpe-id option I could fix it easy while I am looking for solution...

and thank you for helping me... I know you don't have crystall ball... no need to be cocky

dave14305 · October 24, 2024, 7:04pm

What’s the value from this command:

uci get dhcp.@dnsmasq[0].confdir

Nextdns assumes it’s the default /tmp/dnsmasq.d and hardcodes that, but some people change it.

github.com

nextdns/nextdns/blob/e7c9730f445e17f5f876f5b3fceec77dfa4f19b6/router/openwrt/setup.go#L29


      
          	SetPort0        bool
          
          	savedForwarders string
          }
          
          func New() (*Router, bool) {
          	if r, err := internal.ReadOsRelease(); err != nil || r["ID"] != "openwrt" {
          		return nil, false
          	}
          	return &Router{
          		DNSMasqPath: "/tmp/dnsmasq.d/nextdns.conf",
          		ListenPort:  "5342",
          	}, true
          }
          
          func (r *Router) String() string {
          	return "openwrt"
          }
          
          func (r *Router) Configure(c *config.Config) error {
          	c.Listens = []string{"127.0.0.1:" + r.ListenPort}

Mile-Lile · October 25, 2024, 3:30am

root@192.168.1.1's password:


BusyBox v1.36.1 (2024-10-22 11:15:54 UTC) built-in shell (ash)

  _______                     ________        __
 |       |.-----.-----.-----.|  |  |  |.----.|  |_
 |   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
 |_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
 -----------------------------------------------------
 OpenWrt SNAPSHOT, r27893-b6bbc76c0b
 -----------------------------------------------------
root@AX3000T:~# uci get dhcp.@dnsmasq[0].confdir
uci: Entry not found
root@AX3000T:~#

I don't recall changing it, at least not from cli... I usually use GUI...

Linux-DADDY · October 25, 2024, 3:45am

Thank you for making the topic again as it had not been added yet.

Can verify even from the stable branch nextdns app is broken, But i can't remember the error massage as i was not noticing that. But the NextDNS app broke my network configs that's why i had to remove that immediately.

Indeed it is. As i am using different DNS on different Interfaces so i have to use the dnsmasq option for it, i can not use the nextnds app until it gives me the option to select the interfaces and fixes the bugs.

Linux-DADDY · October 25, 2024, 3:57am

Even if this fix the nextdns configdir issues, which is good for @Mile-Lile. but it will still not fix the issue for me, as the nextdns app does not support the interfaces options to select and i do have 4 Interfaces with access point on one router.

lleachii · October 25, 2024, 7:28am

Did did you follow up with @systemcrash's comment?

Mile-Lile · October 25, 2024, 7:59am

maybe I missunderstood him? He said that GUI option is pointless unless there is no directive "under the hood"... so, when I tried to open ticket with FR in openwrt repo it redirected me here... any suggestion? I am owrt noob and not sure how things works here... for me it is just simple feature requeest that has to be reviwed by devs and if they thing this option is usefull for more than 5% of owrt users they will accpet it...

lleachii · October 25, 2024, 8:01am

Reviewed?

So you already submitted your code then?

Or you're asking the devs to write code?

Mile-Lile · October 25, 2024, 8:05am

ah, ok... now I get it I am a little bit slow...

Mile-Lile · October 25, 2024, 8:07am

but then again, it is contributing... so no FR...

Linux-DADDY · October 25, 2024, 8:33am

Maybe He is asking for the dev to write the code as i would. Now TBH The dev should have write the code for that option as it is missing right now.

lleachii · October 25, 2024, 8:38am

I'm not sure I follow your rationale, but your candor and honestly brought clarity to the discussion. Thanks.

brada4 · October 25, 2024, 5:57pm

First the option needs to pass from config file to command line. For Next DNS you can have DoH (dns-http-proxy) DoT (stubby) or native LuCI interface, but likely there are other use cases.

systemcrash · October 25, 2024, 8:00pm

As a workaround, it's possible to add the raw parameter to a custom config. That possibility was merged finally a few days ago to dnsmasq packge.

Otherwise, every new flag needs to be individually added to dnsmasq init script.

Edit: you're welcome to make a PR to add it to dnsmasq package. It might take a while to go in tho.