During boot the failsafe mode packet is sent to inform that the router is in the time window for entering failsafe mode. I noticed that the packet source ip address is 192.168.1.1 and this is conflicting with another device in my network that triggers a duplicate address alarm.
Why it's sending out a packet with a source address that isn't the actual interface address? Any solution or workaround?
This is part of preinit, so it will always come from that address as that's the failsafe address. Your config hasn't even been loaded yet.
You can change this in the build config if you compile your own images.
CONFIG_TARGET_PREINIT_IP
@lantis1008
Given this, I think I would prefer to deactivate the packet sending (or at most use a dummy ip address just for this packet, preserving 192.168.1.1 as failsafe ip address).
It looks like setting CONFIG_TARGET_PREINIT_SUPPRESS_FAILSAFE_NETMSG in your config and compiling your own image might keep the failsafe functionality, but stop it broadcasting the packet.
What i can't quite figure out is whether it is going to broadcast something anyway during preinit? The logic looks a bit weird to me but i don't have time to dig further about where it goes.
In addition it looks like CONFIG_TARGET_PREINIT_SHOW_NETMSG must be not set (default) to not have that packet sent.
Anyway I'm thinking about opening a bug report, because it's not expected that the router sends out packets from addresses different than those configured.
It is to ensure a consistent experience during failsafe. I don't really think it is a bug.
You can raise a bug but i don't think it will be accepted. However please link it to here if you do, i would be interested to know the outcome.
Like i said, the filesystem hasn't even loaded at this point so how can it know what IP you have configured? This is the preinit environment.
It's exactly about consistency! Net msg with failsafe sender address are ok to me only after failsafe mode is entered. If it's not possibile to get the configured address during preinit, it would be safer to just not send those messages.
You're right it's not a bug, but it's a matter of default configuration.. it's not safe.