OpenWrt
OpenWrt news, tools, tips and discussion. Related projects, such as DD-WRT, Tomato and OpenSAN, are also on-topic.
Rules
-
Stay on topic: All posts should be related to OpenWrt and related projects, including DD-WRT, Tomato, OpenSAN, and more!
-
No offensive or low-effort content: Don't post offensive or unhelpful content. Be nice - keep it civil and friendly!
-
Describe images/videos, no memes: Please include a text description when sharing images or videos.
-
No self-promotion spam: Active community members can post their apps if they answer any questions in the comments. Please do not post links to your own website, YouTube, blog content, or communities.
-
No reposts or rehosted content: Share only the original source of an article, unless it's not available in English, behind a paywall or requires logging in (like Twitter). Avoid reposting the same topic from other sources.
-
No editorializing titles: You can add the author or website's name if helpful, but keep article titles unchanged.
-
No piracy: Do not share links or direct people to pirated content.
-
No unauthorized polls, bots, or giveaways: Do not create polls, use bots, or organize giveaways without first contacting mods for approval.
-
No affiliate links: Posting affiliate links is not allowed.
view the rest of the comments
and make sure all static IPs are known to that DHCP server.
Indeed!
@vk6flab
Personally I only assign static IP addresses that are not in the DHCP pool range which should prevent any IP address assignment conflicts... Reserved addresses seem like a hack to enable static addresses within the dynamic pool range...but that's just my opinion
@gratux
Given that everything on my network gets their details via DHCP, I allocate the static ones within the range, generally speaking the pretty (memorable) numbers, but allocated by the DHCP server, so from the perspective of everything on the network, it's just another DHCP address, just that it never changes.