# Daemon warning in log

**URL:** <https://forum.openwrt.org/t/daemon-warning-in-log/152406>\
**Category:** Installing and Using OpenWrt\
**Created:** [February 22, 2023, 12:52am UTC](https://forum.openwrt.org/t/daemon-warning-in-log/152406 "2023-02-22T00:52:42Z")\
**Posts on this page:** 14\
**Page:** 1

<div class="post-metadata">

**Author:** ![Peacefuleight](https://forum.openwrt.org/letter_avatar/peacefuleight/32/5_5575768a8748004e209b776fc1b2916d.png) [@Peacefuleight](https://forum.openwrt.org/u/Peacefuleight)\
**Post date:** [February 22, 2023, 12:52am UTC](https://forum.openwrt.org/t/daemon-warning-in-log/152406/1 "2023-02-22T00:52:42Z")

</div>

Can I do something about it?

```plaintext
ue Feb 21 18:18:08 2023 daemon.warn odhcpd[2058]: No default route present, overriding ra_lifetime!
Tue Feb 21 18:21:10 2023 daemon.warn odhcpd[2058]: No default route present, overriding ra_lifetime!
Tue Feb 21 18:27:26 2023 daemon.warn odhcpd[2058]: No default route present, overriding ra_lifetime!
Tue Feb 21 18:32:13 2023 daemon.warn odhcpd[2058]: No default route present, overriding ra_lifetime!
Tue Feb 21 18:41:48 2023 daemon.warn odhcpd[2058]: No default route present, overriding ra_lifetime!
Tue Feb 21 18:48:16 2023 daemon.warn odhcpd[2058]: No default route present, overriding ra_lifetime!
Tue Feb 21 18:52:45 2023 daemon.warn odhcpd[2058]: No default route present, overriding ra_lifetime!
Tue Feb 21 18:57:21 2023 daemon.warn odhcpd[2058]: No default route present, overriding ra_lifetime!
Tue Feb 21 19:04:35 2023 daemon.warn odhcpd[2058]: No default route present, overriding ra_lifetime!
Tue Feb 21 19:13:55 2023 daemon.warn odhcpd[2058]: No default route present, overriding ra_lifetime!

```

---

<div class="post-metadata">

**Author:** ![mk24](https://forum.openwrt.org/letter_avatar/mk24/32/5_5575768a8748004e209b776fc1b2916d.png) [@mk24](https://forum.openwrt.org/u/mk24)\
**Post date:** [February 22, 2023, 1:26am UTC](https://forum.openwrt.org/t/daemon-warning-in-log/152406/2 "2023-02-22T01:26:12Z")

</div>

This is coming from the lan by default configured to try to advertise itself as an IPv6 capable router, but the existing wan connection does not support IPv6.

If your ISP is IPv4 only, make the lan also IPv4 only by disabling ra and dchpv6 in the LAN dhcp configuration.

---

<div class="post-metadata">

**Author:** ![Peacefuleight](https://forum.openwrt.org/letter_avatar/peacefuleight/32/5_5575768a8748004e209b776fc1b2916d.png) [@Peacefuleight](https://forum.openwrt.org/u/Peacefuleight)\
**Post date:** [February 22, 2023, 2:06am UTC](https://forum.openwrt.org/t/daemon-warning-in-log/152406/3 "2023-02-22T02:06:18Z")

</div>

I have that, dont have ra.

```plaintext
config dnsmasq
        option domainneeded '1'
        option localise_queries '1'
        option rebind_protection '1'
        option rebind_localhost '1'
        option local '/lan/'
        option domain 'lan'
        option expandhosts '1'
        option authoritative '1'
        option readethers '1'
        option leasefile '/tmp/dhcp.leases'
        option localservice '1'
        option ednspacket_max '1232'
        option confdir '/tmp/dnsmasq.d'
        option noresolv '1'
        list server '127.0.0.53#53'

config dhcp 'lan'
        option interface 'lan'
        option start '100'
        option limit '150'
        option leasetime '12h'
        option dhcpv4 'server'
        option dhcpv6 'server'
        option ra 'server'
        list ra_flags 'managed-config'
        list ra_flags 'other-config'

config dhcp 'wan'
        option interface 'wan'
        option ignore '1'

config odhcpd 'odhcpd'
        option maindhcp '0'
        option leasefile '/tmp/hosts/odhcpd'
        option leasetrigger '/usr/sbin/odhcpd-update'
        option loglevel '4'

config dhcp 'guest'
        option interface 'guest'
        option start '100'
        option limit '150'
        option leasetime '12h'

```

---

<div class="post-metadata">

**Author:** ![psherman](https://forum.openwrt.org/letter_avatar/psherman/32/5_5575768a8748004e209b776fc1b2916d.png) [@psherman](https://forum.openwrt.org/u/psherman)\
**Post date:** [February 22, 2023, 2:11am UTC](https://forum.openwrt.org/t/daemon-warning-in-log/152406/4 "2023-02-22T02:11:19Z")

</div>

> [@Peacefuleight](#):
>
> dont have ra.

Yes you do.

> [@Peacefuleight](#):
>
> ```plaintext
> option dhcpv6 'server'
> option ra 'server'
> list ra_flags 'managed-config'
> list ra_flags 'other-config'
> 
> ```

---

<div class="post-metadata">

**Author:** ![Peacefuleight](https://forum.openwrt.org/letter_avatar/peacefuleight/32/5_5575768a8748004e209b776fc1b2916d.png) [@Peacefuleight](https://forum.openwrt.org/u/Peacefuleight)\
**Post date:** [February 22, 2023, 2:15am UTC](https://forum.openwrt.org/t/daemon-warning-in-log/152406/5 "2023-02-22T02:15:54Z")

</div>

> [@psherman](#):
>
> Yes you do

😋 you're right 😉 sorry, thanks

---

<div class="post-metadata">

**Author:** ![anon11662642](https://forum.openwrt.org/letter_avatar/anon11662642/32/5_5575768a8748004e209b776fc1b2916d.png) [@anon11662642](https://forum.openwrt.org/u/anon11662642)\
**Post date:** [February 22, 2023, 7:53pm UTC](https://forum.openwrt.org/t/daemon-warning-in-log/152406/6 "2023-02-22T19:53:37Z")

</div>

@stintel

These new commits are the culprits:

> <https://github.com/openwrt/openwrt/commit/65c9b5ffb02ba233e0857c1c035512d88ea3d3d2>
>
> dfab0fa dhcpv4: detect noarp interfaces
> 5a17751 router: improve RA logging
> e…dc5e17 router: always check ra\_default
> 
> Signed-off-by: Stijn Tintel \<stijn@linux-ipv6.be\>

> <https://github.com/openwrt/odhcpd/commit/edc5e1738682e764e64bcbffde1e0a1cc9feac21>
>
> We currently only check ra\_default when an interface has valid
> addresses. This r…esults in ra\_default being ignored in case we have an
> interface with only link-local addresses. This effectively breaks the
> use of value 2 for the ra\_default parameter.
> 
> Fix this by always checking ra\_lifetime, regardless of the interface
> having public addresses or not.
> 
> Fixes: #11930
> Fixes: 83e14f455817 ("router: advertise removed addresses as invalid in 3 consecutive RAs")
> Signed-off-by: Stijn Tintel \<stijn@linux-ipv6.be\>
> Acked-by:Hans Dedecker \<dedeckeh@gmail.com\>

> <https://github.com/openwrt/odhcpd/commit/5a1775178bfbaf3327df99998b60d1c48b2dad9d>
>
> We only set the RA lifetime to what is configured in UCI when there is a
> default… route and valid prefix. In any other case, we set it to 0. This
> leads to confusion where people believe ra\_lifetime is completely
> ignored. In case there is a default route, but no valid prefix, a debug
> message explains this, but if there is no default route, we silently
> override ra\_lifetime.
> 
> Add a debug message for the latter case, and explicitly mention
> overriding ra\_lifetime in both cases.
> 
> Signed-off-by: Stijn Tintel \<stijn@linux-ipv6.be\>
> Acked-by: Hans Dedecker \<dedeckeh@gmail.com\>

---

<div class="post-metadata">

**Author:** ![stintel](https://forum.openwrt.org/user_avatar/forum.openwrt.org/stintel/32/42676_2.png) [@stintel](https://forum.openwrt.org/u/stintel)\
**Post date:** [February 22, 2023, 8:25pm UTC](https://forum.openwrt.org/t/daemon-warning-in-log/152406/7 "2023-02-22T20:25:21Z")

</div>

These warnings are there to tell you something in your config is not right. It has already been suggested to disable ra, this will make the warnings go away.

---

<div class="post-metadata">

**Author:** ![anon11662642](https://forum.openwrt.org/letter_avatar/anon11662642/32/5_5575768a8748004e209b776fc1b2916d.png) [@anon11662642](https://forum.openwrt.org/u/anon11662642)\
**Post date:** [February 22, 2023, 8:42pm UTC](https://forum.openwrt.org/t/daemon-warning-in-log/152406/8 "2023-02-22T20:42:45Z")

</div>

So, now you need to disable the IPv6 settings of the DHCP server on the LAN interface **to not have the log full of spam** like the one shown in the first post, **when it wasn't needed before**.

---

<div class="post-metadata">

**Author:** ![stintel](https://forum.openwrt.org/user_avatar/forum.openwrt.org/stintel/32/42676_2.png) [@stintel](https://forum.openwrt.org/u/stintel)\
**Post date:** [February 22, 2023, 9:36pm UTC](https://forum.openwrt.org/t/daemon-warning-in-log/152406/9 "2023-02-22T21:36:30Z")

</div>

If you read the commit message for [https://github.com/openwrt/odhcpd/commit/5a1775178bfbaf3327df99998b60d1c48b2dad9d](https://github.com/openwrt/odhcpd/commit/5a1775178bfbaf3327df99998b60d1c48b2dad9d) you'll understand why this was added.

Enabling RA on your LAN when you don't have a default route doesn't make a lot of sense, unless maybe in some niche case as discussed in [https://github.com/openwrt/openwrt/issues/11930](https://github.com/openwrt/openwrt/issues/11930).

RA is enabled by default, because it is 2023 and if you don't have IPv6 you should talk to your ISP or seriously consider replacing it with a less ignorant one.

At least now you're made aware that something is not entirely right, while before this was just hidden.

---

<div class="post-metadata">

**Author:** ![anon11662642](https://forum.openwrt.org/letter_avatar/anon11662642/32/5_5575768a8748004e209b776fc1b2916d.png) [@anon11662642](https://forum.openwrt.org/u/anon11662642)\
**Post date:** [February 22, 2023, 9:50pm UTC](https://forum.openwrt.org/t/daemon-warning-in-log/152406/10 "2023-02-22T21:50:59Z")

</div>

> [@stintel](#):
>
> At least now you're made aware that something is not entirely right, **while before this was just hidden**.

If _you_ can't _explain_ it to a six year old, _you don't understand it yourself_. - **Albert Einstein**

Now I understand you.

Thank you so much.

---

<div class="post-metadata">

**Author:** ![stintel](https://forum.openwrt.org/user_avatar/forum.openwrt.org/stintel/32/42676_2.png) [@stintel](https://forum.openwrt.org/u/stintel)\
**Post date:** [February 22, 2023, 10:07pm UTC](https://forum.openwrt.org/t/daemon-warning-in-log/152406/11 "2023-02-22T22:07:32Z")

</div>

So I've given this some more thought, and for a brief moment was considering increasing the log level for this message, but I really think we shouldn't.

Consider the following scenario: your ISP offers proper IPv6 connectivity, your OpenWrt router is announcing an IPv6 prefix to your LAN, and you have working IPv6 connectivity on your clients. One day your ISP messes up and breaks that IPv6 connectivity. In the previous scenario, it would stop working, but no log messages appear in your router, so you assume everything is fine...

You might find out accidentally, but I'd prefer the router being noisy about it.

---

<div class="post-metadata">

**Author:** ![Peacefuleight](https://forum.openwrt.org/letter_avatar/peacefuleight/32/5_5575768a8748004e209b776fc1b2916d.png) [@Peacefuleight](https://forum.openwrt.org/u/Peacefuleight)\
**Post date:** [February 26, 2023, 1:08pm UTC](https://forum.openwrt.org/t/daemon-warning-in-log/152406/13 "2023-02-26T13:08:34Z")

</div>

so ipv4 is not good anymore? no safe or what?

---

<div class="post-metadata">

**Author:** ![slh](https://forum.openwrt.org/user_avatar/forum.openwrt.org/slh/32/113591_2.png) [@slh](https://forum.openwrt.org/u/slh)\
**Post date:** [February 27, 2023, 12:30am UTC](https://forum.openwrt.org/t/daemon-warning-in-log/152406/14 "2023-02-27T00:30:20Z")

</div>

These days, thanks to the proliferation of cgNAT among new ISPs, IPv4 is indeed not 'enough' anymore.

After switching from VDSL to ftth, I only get cgNAT and a semi-static /56 IPv6 prefix - if IPv6 fails for some reason, my incoming (road-warrior) VPN connections are gone, that would be a significant problem for me. With the cgNAT IPv4 address (only), I'd also be hassled a lot more with captchas and other server side defenses against against weird usage patterns and access throttling.

Due to my home VPN gateway naturally being IPv6-only (as I have no external IPv4 address), I obviously care _a lot_ about having IPv6 connectivity client-side as well (mobile uses, LTE/ 5g, etc.).

---

<div class="post-metadata">

**Author:** ![system](https://forum.openwrt.org/uploads/default/original/3X/7/4/740520c71f00039bbf001045c682f0ecb25e905a.png) [@system](https://forum.openwrt.org/u/system)\
**Post date:** [March 9, 2023, 12:31am UTC](https://forum.openwrt.org/t/daemon-warning-in-log/152406/15 "2023-03-09T00:31:00Z")

</div>

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.
