> For the complete documentation index, see [llms.txt](https://book.ferro.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://book.ferro.pro/openwrt/dhcp_dns.md).

# DHCP\_DNS

* [Docs](#docs)
* [Static](#static)
  * [Luci](#luci)
  * [uci](#uci)
* [Lease Time](#lease-time)
  * [per client](#per-client)
  * [remove active](#remove-active)

## Docs

<https://openwrt.org/docs/guide-user/base-system/dhcp\\_configuration>

## Static

/etc/config/dhcp

### Luci

* all conf: <http://wrt.lan/cgi-bin/luci/admin/network/dhcp>
* dynamic -> static : <http://wrt.lan/cgi-bin/luci/admin/status/overview>

### uci

```
uci show | grep dhcp | grep host

uci add dhcp host         # will create `dhcp.@host[INDEX]=host`
uci set dhcp.@host[-1].ITEM # -1 : last | -x: xth from last

uci delete dhcp.@host[-1]

uci commit dhcp         # refresh Luci
service dnsmasq restart # reconnect client
```

## Lease Time

```
cat /tmp/dhcp.leases 

uci show | grep dhcp | grep lease
=> dhcp.lan.leasetime='12h'

uci set dhcp.lan.leasetime='10m'
uci commit dhcp; service odhcpd restart ; service dnsmasq restart
```

### per client

<https://openwrt.org/docs/guide-user/dhcp/dhcp\\_configuration#dhcp\\_pools>

luci: <http://wrt.lan/cgi-bin/luci/admin/network/dhcp>

### remove active

```
vi /tmp/dhcp.leases
/etc/init.d/dnsmasq restart
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://book.ferro.pro/openwrt/dhcp_dns.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.