db9d4d3a3c
If the attribute 'interface' is not set in a 'domain' tag, the router tries to dynamically receive and maintain an IP configuration for that domain by using DHCP in the client role at all interfaces that connect to the domain. In the DHCP discover phase, the router simply chooses the first DHCP offer that arrives. So, no comparison of different DHCP offers is done. In the DHCP request phase, the server is expected to provide an IP address, a gateway, a subnet mask, and an IP lease time to the router. If anything substantial goes wrong during a DHCP exchange, the router discards the outcome of the exchange and goes back to the DHCP discover phase. At any time where there is no valid IP configuration present at a domain, the domain does only act as DHCP client and all other router functionality is disabled for the domain. A domain cannot act as DHCP client and DHCP server at once. So, a 'domain' tag must either have an 'interface' attribute or must not contain a 'dhcp-server' tag. Ref #2534 |
||
|---|---|---|
| .. | ||
| doc | ||
| include | ||
| lib | ||
| recipes | ||
| run | ||
| src | ||
| README | ||
This source-code repository contains genuine low-level OS components and interfaces of Genode. It solely depends on the framework's base API.