I’m just going to leave this like that for the moment. I have tried various things but my assumptions could be wrong, so I won’t mention them.
- power outage
- router back up after outage
- local names not resolvable
the clients don't know the router rebooted, the names will update next time they renew their DHCP lease.
1 Like
Use multicast DNS. Instead of ping myPC.lan try ping myPC.local, - there is a big chance it's already there. Or issue avahi-browse --all --ignore-local --resolve --terminate.
I agree with @frollic - the router obtained names via their DHCP requests. Since the device rebooted, that cache is gone.
They will reappear upon renewal of the lease.
To be clear, are these wireless or wired clients, and are they directly connected to the OpenWrt, or via a switch, etc.?
@Frolic Thanks, yes. That’s what I thought had happened. The problem is that this doesn’t really help to solve the immediate problem. I don’t want to have to use static leases throughout
@lleachii they are a mixture of wired and wireless clients
1 Like
This is normal on all routers (that save such caches in RAM).
Since you don't want "statically configured" leases and hostnames:
I would advise a UPS for your router?
A disconnect/reconnect of the clients should solve this.
1 Like
if this was planned down time, you could have shortened the DHCP lease time ahead of the reboot, then the clients would have updated sooner.
you can always pull the Ethernet cable/disconnect the wifi to force an instant renewal.
if not, works as designed.
1 Like
That’s probably a good idea. Fortunately this is a rare event but the knock-on effects are annoying
1 Like
@timur.davletshin Actually the first command returned Name or service not known
And the second returned literally nothing
... which means whatever you try to ping doesn't support mDNS or you used wrong name.
The DHCP lease file by default is /tmp/dhcp.leases which means it goes away if the router reboots. If you have storage like a USB flash drive or SSD that can take the writes you can move it there to survive reboots.
Network → DHCP and DNS → Resolve & Hosts Files (tab) → Lease file (edit).
2 Likes
Thanks all. I think this will have to be put down to a general weakness. I can probably mitigate its effects by configuring particular hosts with static addresses
Of the protocol, yes, OpenWRT, no.
Like I said, use short(er) DHCP lease times.
2 Likes
Yes, I mean the general ur-protocol environment
Yes, good idea. At the moment, I’m not finding where that’s set
Thanks for that
1 Like
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.