ExternalVendorCode/genode
1
0
Fork 0
mirror of https://github.com/genodelabs/genode.git synced 2024-12-27 17:18:53 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
424ed1b79a
genode/repos/os/run/nic_router_dhcp.inc

368 lines
9.9 KiB
PHP
Raw Normal View History

nic_router: support multiple DHCP option 6 entries * The NIC router now considers, memorizes, and, if configured, reports multiple DHCP option 6 entries from DHCP replies that it received as DHCP client * A DHCP server at the NIC router can now be configured statically with multiple DNS server addresses to propagate * The 'dns_server_from' attribute of the DHCP server of the NIC router now supports the forwarding of multiple DNS server addresses * The automated run/nic_router_dhcp test tests all the above mentioned new functionality and reconfiguring it at runtime. The test was added to the autopilot. * All run scripts were adapted to fit the new NIC router configuration interface Fixes #3952
2020-11-16 14:43:40 +00:00
#
# See os/src/test/nic_router_dhcp/README for a documentation.
#
create_boot_directory
import_from_depot [depot_user]/src/[base_src]
set build_components {
init
server/dynamic_rom
test/nic_router_dhcp/client
server/nic_router
}
lappend_if [nic_router_2_managed] build_components test/nic_router_dhcp/manager
lappend_if [nic_router_2_managed] build_components server/report_rom
build $build_components
append config {
<config>
<parent-provides>
<service name="ROM"/>
<service name="IRQ"/>
<service name="IO_MEM"/>
<service name="IO_PORT"/>
<service name="PD"/>
<service name="RM"/>
<service name="CPU"/>
<service name="LOG"/>
</parent-provides>
<default-route>
<any-service> <parent/> <any-child/> </any-service>
</default-route>
<default caps="200"/>
<start name="timer">
<resource name="RAM" quantum="1M"/>
<provides><service name="Timer"/></provides>
</start>
<start name="dynamic_rom">
<resource name="RAM" quantum="4M"/>
<provides><service name="ROM"/> </provides>
<config verbose="yes">
<rom name="nic_router_1.config">
<inline>
<config>
<policy label="nic_router_2 -> " domain="downlink"/>
<domain name="downlink" interface="10.2.3.1/24">
<dhcp-server ip_first="10.2.3.2"
run/nic_router_dhcp: DHCP RENEW and some fixes * Test DHCP RENEW by the test client in the unmanaged variant. * Add event IDs to log output of test client in order to prevent false positive result in the managed variant. * Let managed and unmanaged variant have separate string patterns for 'run_genode_until' because they already had different output and it will differ even more as we don't want to test DHCP RENEW with the managed variant. * Delay first test client DHCP in order to fix unexpected sporadic initial IP config. * Remove some unnecessary code from the run script Fixes #4460
2022-03-28 14:16:48 +00:00
ip_last="10.2.3.2">
nic_router: support multiple DHCP option 6 entries * The NIC router now considers, memorizes, and, if configured, reports multiple DHCP option 6 entries from DHCP replies that it received as DHCP client * A DHCP server at the NIC router can now be configured statically with multiple DNS server addresses to propagate * The 'dns_server_from' attribute of the DHCP server of the NIC router now supports the forwarding of multiple DNS server addresses * The automated run/nic_router_dhcp test tests all the above mentioned new functionality and reconfiguring it at runtime. The test was added to the autopilot. * All run scripts were adapted to fit the new NIC router configuration interface Fixes #3952
2020-11-16 14:43:40 +00:00
<dns-server ip="1.2.3.4"/>
<dns-server ip="2.3.4.5"/>
<dns-server ip="3.4.5.6"/>
nic_router: propagate dns domain name via dhcp With this commit, the NIC router DHCP client reads out the first DNS domain name (DHCP option 15) if any from a DHCP reply that generates an IPv4 config for a domain and stores the name together with the IPv4 config for that domain. DNS domain names are reported via the new report tag '<dns-domain>' if the 'config' attribute in the config tag '<report>' is set. Furthermore, the NIC router DHCP server becomes able to obtain a DNS domain name from another domain that has a DHCP client dynamically (given the config attribute 'dns_config_from' is set and no static DNS config is given) or statically from its configuration (new config tag '<dns-domain>') and propagate this name with DHCP replies (DHCP option 15). The 'nic_router_dhcp_*' tests are adapted to test the new feautures. The commit also gets rid of some mirrored files in 'test/nic_router_dhcp/manager'. Fixes #4246
2021-08-10 14:57:25 +00:00
<dns-domain name="genode.org"/>
nic_router: support multiple DHCP option 6 entries * The NIC router now considers, memorizes, and, if configured, reports multiple DHCP option 6 entries from DHCP replies that it received as DHCP client * A DHCP server at the NIC router can now be configured statically with multiple DNS server addresses to propagate * The 'dns_server_from' attribute of the DHCP server of the NIC router now supports the forwarding of multiple DNS server addresses * The automated run/nic_router_dhcp test tests all the above mentioned new functionality and reconfiguring it at runtime. The test was added to the autopilot. * All run scripts were adapted to fit the new NIC router configuration interface Fixes #3952
2020-11-16 14:43:40 +00:00
</dhcp-server>
</domain>
</config>
</inline>
nic_router_dhcp_*: raise timeouts On okl4, pistachio, sel4 the test didn't come up fast enough in order to still experience the first configuration of NIC router #1. This commit doubles the lifetime of the first configuration of NIC router #1 to 4 seconds and raises the overall test timeout accordingly. Ref #4555
2022-07-26 09:38:46 +00:00
<sleep milliseconds="4000"/>
nic_router: support multiple DHCP option 6 entries * The NIC router now considers, memorizes, and, if configured, reports multiple DHCP option 6 entries from DHCP replies that it received as DHCP client * A DHCP server at the NIC router can now be configured statically with multiple DNS server addresses to propagate * The 'dns_server_from' attribute of the DHCP server of the NIC router now supports the forwarding of multiple DNS server addresses * The automated run/nic_router_dhcp test tests all the above mentioned new functionality and reconfiguring it at runtime. The test was added to the autopilot. * All run scripts were adapted to fit the new NIC router configuration interface Fixes #3952
2020-11-16 14:43:40 +00:00
<inline>
<config>
<policy label="nic_router_2 -> " domain="downlink"/>
<domain name="downlink" interface="10.2.3.1/24">
<dhcp-server ip_first="10.2.3.2"
run/nic_router_dhcp: DHCP RENEW and some fixes * Test DHCP RENEW by the test client in the unmanaged variant. * Add event IDs to log output of test client in order to prevent false positive result in the managed variant. * Let managed and unmanaged variant have separate string patterns for 'run_genode_until' because they already had different output and it will differ even more as we don't want to test DHCP RENEW with the managed variant. * Delay first test client DHCP in order to fix unexpected sporadic initial IP config. * Remove some unnecessary code from the run script Fixes #4460
2022-03-28 14:16:48 +00:00
ip_last="10.2.3.2">
nic_router: support multiple DHCP option 6 entries * The NIC router now considers, memorizes, and, if configured, reports multiple DHCP option 6 entries from DHCP replies that it received as DHCP client * A DHCP server at the NIC router can now be configured statically with multiple DNS server addresses to propagate * The 'dns_server_from' attribute of the DHCP server of the NIC router now supports the forwarding of multiple DNS server addresses * The automated run/nic_router_dhcp test tests all the above mentioned new functionality and reconfiguring it at runtime. The test was added to the autopilot. * All run scripts were adapted to fit the new NIC router configuration interface Fixes #3952
2020-11-16 14:43:40 +00:00
<dns-server ip="4.5.6.7"/>
<dns-server ip="5.6.7.8"/>
</dhcp-server>
</domain>
</config>
</inline>
run/nic_router_dhcp: DHCP RENEW and some fixes * Test DHCP RENEW by the test client in the unmanaged variant. * Add event IDs to log output of test client in order to prevent false positive result in the managed variant. * Let managed and unmanaged variant have separate string patterns for 'run_genode_until' because they already had different output and it will differ even more as we don't want to test DHCP RENEW with the managed variant. * Delay first test client DHCP in order to fix unexpected sporadic initial IP config. * Remove some unnecessary code from the run script Fixes #4460
2022-03-28 14:16:48 +00:00
<sleep milliseconds="4000"/>
nic_router: support multiple DHCP option 6 entries * The NIC router now considers, memorizes, and, if configured, reports multiple DHCP option 6 entries from DHCP replies that it received as DHCP client * A DHCP server at the NIC router can now be configured statically with multiple DNS server addresses to propagate * The 'dns_server_from' attribute of the DHCP server of the NIC router now supports the forwarding of multiple DNS server addresses * The automated run/nic_router_dhcp test tests all the above mentioned new functionality and reconfiguring it at runtime. The test was added to the autopilot. * All run scripts were adapted to fit the new NIC router configuration interface Fixes #3952
2020-11-16 14:43:40 +00:00
<inline>
run/nic_router_dhcp: DHCP RENEW and some fixes * Test DHCP RENEW by the test client in the unmanaged variant. * Add event IDs to log output of test client in order to prevent false positive result in the managed variant. * Let managed and unmanaged variant have separate string patterns for 'run_genode_until' because they already had different output and it will differ even more as we don't want to test DHCP RENEW with the managed variant. * Delay first test client DHCP in order to fix unexpected sporadic initial IP config. * Remove some unnecessary code from the run script Fixes #4460
2022-03-28 14:16:48 +00:00
<config>
nic_router: support multiple DHCP option 6 entries * The NIC router now considers, memorizes, and, if configured, reports multiple DHCP option 6 entries from DHCP replies that it received as DHCP client * A DHCP server at the NIC router can now be configured statically with multiple DNS server addresses to propagate * The 'dns_server_from' attribute of the DHCP server of the NIC router now supports the forwarding of multiple DNS server addresses * The automated run/nic_router_dhcp test tests all the above mentioned new functionality and reconfiguring it at runtime. The test was added to the autopilot. * All run scripts were adapted to fit the new NIC router configuration interface Fixes #3952
2020-11-16 14:43:40 +00:00
<policy label="nic_router_2 -> " domain="downlink"/>
nic_router: fix exc. in Interface::handle_config_3 When Interface::handle_config_3 (third step of applying a new configuration to interfaces) tried to detach the interface from the current IP config because the old and new IP config differed, it did so using the new domain. The former steps of the reconfiguration already installed the new domain reference at the interface. Therefore, also the DHCP server of the new domain was used. This, however caused uncaught exceptions because detaching from an IP config includes dissolving all DHCP allocations. This dissolving of DHCP allocations now operated on a DHCP server (the one of the new domain) that wasn't related to the allocations and, in the worst case, caused an uncaught exception because the IPs were out of its range. That said, this commit ensures that detaching an interface from an IP config is always done on the domain from which the IP config originated. Normally, this is the domain the interface is attached to. But in the case of Interface::handle_config_3, it is another - the former domain the interface was attached to. The commit also adapts the nic_router_dhcp_* tests in a way that they reconfigure the router in a way that would trigger the uncaught exception without the fix. Fixes #4200
2021-06-24 12:34:13 +00:00
<domain name="downlink" interface="10.2.4.1/24">
nic_router: support multiple DHCP option 6 entries * The NIC router now considers, memorizes, and, if configured, reports multiple DHCP option 6 entries from DHCP replies that it received as DHCP client * A DHCP server at the NIC router can now be configured statically with multiple DNS server addresses to propagate * The 'dns_server_from' attribute of the DHCP server of the NIC router now supports the forwarding of multiple DNS server addresses * The automated run/nic_router_dhcp test tests all the above mentioned new functionality and reconfiguring it at runtime. The test was added to the autopilot. * All run scripts were adapted to fit the new NIC router configuration interface Fixes #3952
2020-11-16 14:43:40 +00:00
nic_router: fix exc. in Interface::handle_config_3 When Interface::handle_config_3 (third step of applying a new configuration to interfaces) tried to detach the interface from the current IP config because the old and new IP config differed, it did so using the new domain. The former steps of the reconfiguration already installed the new domain reference at the interface. Therefore, also the DHCP server of the new domain was used. This, however caused uncaught exceptions because detaching from an IP config includes dissolving all DHCP allocations. This dissolving of DHCP allocations now operated on a DHCP server (the one of the new domain) that wasn't related to the allocations and, in the worst case, caused an uncaught exception because the IPs were out of its range. That said, this commit ensures that detaching an interface from an IP config is always done on the domain from which the IP config originated. Normally, this is the domain the interface is attached to. But in the case of Interface::handle_config_3, it is another - the former domain the interface was attached to. The commit also adapts the nic_router_dhcp_* tests in a way that they reconfigure the router in a way that would trigger the uncaught exception without the fix. Fixes #4200
2021-06-24 12:34:13 +00:00
<dhcp-server ip_first="10.2.4.2"
ip_last="10.2.4.2">
nic_router: support multiple DHCP option 6 entries * The NIC router now considers, memorizes, and, if configured, reports multiple DHCP option 6 entries from DHCP replies that it received as DHCP client * A DHCP server at the NIC router can now be configured statically with multiple DNS server addresses to propagate * The 'dns_server_from' attribute of the DHCP server of the NIC router now supports the forwarding of multiple DNS server addresses * The automated run/nic_router_dhcp test tests all the above mentioned new functionality and reconfiguring it at runtime. The test was added to the autopilot. * All run scripts were adapted to fit the new NIC router configuration interface Fixes #3952
2020-11-16 14:43:40 +00:00
<dns-server ip="6.7.8.9"/>
nic_router: propagate dns domain name via dhcp With this commit, the NIC router DHCP client reads out the first DNS domain name (DHCP option 15) if any from a DHCP reply that generates an IPv4 config for a domain and stores the name together with the IPv4 config for that domain. DNS domain names are reported via the new report tag '<dns-domain>' if the 'config' attribute in the config tag '<report>' is set. Furthermore, the NIC router DHCP server becomes able to obtain a DNS domain name from another domain that has a DHCP client dynamically (given the config attribute 'dns_config_from' is set and no static DNS config is given) or statically from its configuration (new config tag '<dns-domain>') and propagate this name with DHCP replies (DHCP option 15). The 'nic_router_dhcp_*' tests are adapted to test the new feautures. The commit also gets rid of some mirrored files in 'test/nic_router_dhcp/manager'. Fixes #4246
2021-08-10 14:57:25 +00:00
<dns-domain name="this_is_a_way_to_long_dns_domain_name_that_should_be_rejected_by_the_router_and_cause_the_corresponding_dhcp_option_to_disappear_but_you_never_know_and_so_we_better_test_it"/>
nic_router: support multiple DHCP option 6 entries * The NIC router now considers, memorizes, and, if configured, reports multiple DHCP option 6 entries from DHCP replies that it received as DHCP client * A DHCP server at the NIC router can now be configured statically with multiple DNS server addresses to propagate * The 'dns_server_from' attribute of the DHCP server of the NIC router now supports the forwarding of multiple DNS server addresses * The automated run/nic_router_dhcp test tests all the above mentioned new functionality and reconfiguring it at runtime. The test was added to the autopilot. * All run scripts were adapted to fit the new NIC router configuration interface Fixes #3952
2020-11-16 14:43:40 +00:00
</dhcp-server>
</domain>
</config>
</inline>
nic_router: fix exc. in Interface::handle_config_3 When Interface::handle_config_3 (third step of applying a new configuration to interfaces) tried to detach the interface from the current IP config because the old and new IP config differed, it did so using the new domain. The former steps of the reconfiguration already installed the new domain reference at the interface. Therefore, also the DHCP server of the new domain was used. This, however caused uncaught exceptions because detaching from an IP config includes dissolving all DHCP allocations. This dissolving of DHCP allocations now operated on a DHCP server (the one of the new domain) that wasn't related to the allocations and, in the worst case, caused an uncaught exception because the IPs were out of its range. That said, this commit ensures that detaching an interface from an IP config is always done on the domain from which the IP config originated. Normally, this is the domain the interface is attached to. But in the case of Interface::handle_config_3, it is another - the former domain the interface was attached to. The commit also adapts the nic_router_dhcp_* tests in a way that they reconfigure the router in a way that would trigger the uncaught exception without the fix. Fixes #4200
2021-06-24 12:34:13 +00:00
<sleep milliseconds="2000"/>
<inline>
<config>
<policy label="nic_router_2 -> " domain="downlink"/>
<domain name="downlink" interface="10.2.4.1/24">
<dhcp-server ip_first="10.2.4.200"
ip_last="10.2.4.200">
nic_router: propagate dns domain name via dhcp With this commit, the NIC router DHCP client reads out the first DNS domain name (DHCP option 15) if any from a DHCP reply that generates an IPv4 config for a domain and stores the name together with the IPv4 config for that domain. DNS domain names are reported via the new report tag '<dns-domain>' if the 'config' attribute in the config tag '<report>' is set. Furthermore, the NIC router DHCP server becomes able to obtain a DNS domain name from another domain that has a DHCP client dynamically (given the config attribute 'dns_config_from' is set and no static DNS config is given) or statically from its configuration (new config tag '<dns-domain>') and propagate this name with DHCP replies (DHCP option 15). The 'nic_router_dhcp_*' tests are adapted to test the new feautures. The commit also gets rid of some mirrored files in 'test/nic_router_dhcp/manager'. Fixes #4246
2021-08-10 14:57:25 +00:00
<dns-domain name="genodians.org"/>
nic_router: fix exc. in Interface::handle_config_3 When Interface::handle_config_3 (third step of applying a new configuration to interfaces) tried to detach the interface from the current IP config because the old and new IP config differed, it did so using the new domain. The former steps of the reconfiguration already installed the new domain reference at the interface. Therefore, also the DHCP server of the new domain was used. This, however caused uncaught exceptions because detaching from an IP config includes dissolving all DHCP allocations. This dissolving of DHCP allocations now operated on a DHCP server (the one of the new domain) that wasn't related to the allocations and, in the worst case, caused an uncaught exception because the IPs were out of its range. That said, this commit ensures that detaching an interface from an IP config is always done on the domain from which the IP config originated. Normally, this is the domain the interface is attached to. But in the case of Interface::handle_config_3, it is another - the former domain the interface was attached to. The commit also adapts the nic_router_dhcp_* tests in a way that they reconfigure the router in a way that would trigger the uncaught exception without the fix. Fixes #4200
2021-06-24 12:34:13 +00:00
</dhcp-server>
</domain>
</config>
</inline>
<sleep milliseconds="2000"/>
nic_router: support multiple DHCP option 6 entries * The NIC router now considers, memorizes, and, if configured, reports multiple DHCP option 6 entries from DHCP replies that it received as DHCP client * A DHCP server at the NIC router can now be configured statically with multiple DNS server addresses to propagate * The 'dns_server_from' attribute of the DHCP server of the NIC router now supports the forwarding of multiple DNS server addresses * The automated run/nic_router_dhcp test tests all the above mentioned new functionality and reconfiguring it at runtime. The test was added to the autopilot. * All run scripts were adapted to fit the new NIC router configuration interface Fixes #3952
2020-11-16 14:43:40 +00:00
<inline>
<config>
<policy label="nic_router_2 -> " domain="downlink"/>
<domain name="downlink" interface="10.2.3.1/24">
<dhcp-server ip_first="10.2.3.2"
ip_last="10.2.3.2">
nic_router: propagate dns domain name via dhcp With this commit, the NIC router DHCP client reads out the first DNS domain name (DHCP option 15) if any from a DHCP reply that generates an IPv4 config for a domain and stores the name together with the IPv4 config for that domain. DNS domain names are reported via the new report tag '<dns-domain>' if the 'config' attribute in the config tag '<report>' is set. Furthermore, the NIC router DHCP server becomes able to obtain a DNS domain name from another domain that has a DHCP client dynamically (given the config attribute 'dns_config_from' is set and no static DNS config is given) or statically from its configuration (new config tag '<dns-domain>') and propagate this name with DHCP replies (DHCP option 15). The 'nic_router_dhcp_*' tests are adapted to test the new feautures. The commit also gets rid of some mirrored files in 'test/nic_router_dhcp/manager'. Fixes #4246
2021-08-10 14:57:25 +00:00
<dns-domain name="genodians.org"/>
nic_router: support multiple DHCP option 6 entries * The NIC router now considers, memorizes, and, if configured, reports multiple DHCP option 6 entries from DHCP replies that it received as DHCP client * A DHCP server at the NIC router can now be configured statically with multiple DNS server addresses to propagate * The 'dns_server_from' attribute of the DHCP server of the NIC router now supports the forwarding of multiple DNS server addresses * The automated run/nic_router_dhcp test tests all the above mentioned new functionality and reconfiguring it at runtime. The test was added to the autopilot. * All run scripts were adapted to fit the new NIC router configuration interface Fixes #3952
2020-11-16 14:43:40 +00:00
</dhcp-server>
</domain>
</config>
</inline>
nic_router: fix exc. in Interface::handle_config_3 When Interface::handle_config_3 (third step of applying a new configuration to interfaces) tried to detach the interface from the current IP config because the old and new IP config differed, it did so using the new domain. The former steps of the reconfiguration already installed the new domain reference at the interface. Therefore, also the DHCP server of the new domain was used. This, however caused uncaught exceptions because detaching from an IP config includes dissolving all DHCP allocations. This dissolving of DHCP allocations now operated on a DHCP server (the one of the new domain) that wasn't related to the allocations and, in the worst case, caused an uncaught exception because the IPs were out of its range. That said, this commit ensures that detaching an interface from an IP config is always done on the domain from which the IP config originated. Normally, this is the domain the interface is attached to. But in the case of Interface::handle_config_3, it is another - the former domain the interface was attached to. The commit also adapts the nic_router_dhcp_* tests in a way that they reconfigure the router in a way that would trigger the uncaught exception without the fix. Fixes #4200
2021-06-24 12:34:13 +00:00
<sleep milliseconds="2000"/>
nic_router: support multiple DHCP option 6 entries * The NIC router now considers, memorizes, and, if configured, reports multiple DHCP option 6 entries from DHCP replies that it received as DHCP client * A DHCP server at the NIC router can now be configured statically with multiple DNS server addresses to propagate * The 'dns_server_from' attribute of the DHCP server of the NIC router now supports the forwarding of multiple DNS server addresses * The automated run/nic_router_dhcp test tests all the above mentioned new functionality and reconfiguring it at runtime. The test was added to the autopilot. * All run scripts were adapted to fit the new NIC router configuration interface Fixes #3952
2020-11-16 14:43:40 +00:00
</rom>
</config>
</start>
<start name="nic_router_1">
<binary name="nic_router"/>
<resource name="RAM" quantum="10M"/>
nic_router: act as "Uplink" server Let the NIC router provide an Uplink service besides the Nic service that it already provided. Requests for an Uplink session towards the NIC router are assigned to Domains using the same <policy> configuration tags that are used in order to assign Nic session requests. The MAC addresses of Uplink session components are _NOT_ considered during the allocation of MAC addresses for NIC session components at the same Domain. The task of avoiding MAC address clashes between Uplink session components and Nic session components is therefore left to the integrator. Apart from that, Uplink session components are treated by the NIC router like any other interface. Ref #3961
2020-12-07 15:46:15 +00:00
<provides>
<service name="Nic"/>
<service name="Uplink"/>
</provides>
nic_router: support multiple DHCP option 6 entries * The NIC router now considers, memorizes, and, if configured, reports multiple DHCP option 6 entries from DHCP replies that it received as DHCP client * A DHCP server at the NIC router can now be configured statically with multiple DNS server addresses to propagate * The 'dns_server_from' attribute of the DHCP server of the NIC router now supports the forwarding of multiple DNS server addresses * The automated run/nic_router_dhcp test tests all the above mentioned new functionality and reconfiguring it at runtime. The test was added to the autopilot. * All run scripts were adapted to fit the new NIC router configuration interface Fixes #3952
2020-11-16 14:43:40 +00:00
<route>
<service name="ROM" label="config">
<child name="dynamic_rom" label="nic_router_1.config"/>
</service>
<any-service> <parent/> <any-child/> </any-service>
</route>
</start>
<start name="nic_router_2">
<binary name="nic_router"/>
<resource name="RAM" quantum="10M"/>
nic_router: act as "Uplink" server Let the NIC router provide an Uplink service besides the Nic service that it already provided. Requests for an Uplink session towards the NIC router are assigned to Domains using the same <policy> configuration tags that are used in order to assign Nic session requests. The MAC addresses of Uplink session components are _NOT_ considered during the allocation of MAC addresses for NIC session components at the same Domain. The task of avoiding MAC address clashes between Uplink session components and Nic session components is therefore left to the integrator. Apart from that, Uplink session components are treated by the NIC router like any other interface. Ref #3961
2020-12-07 15:46:15 +00:00
<provides>
<service name="Nic"/>
<service name="Uplink"/>
</provides>}
nic_router: support multiple DHCP option 6 entries * The NIC router now considers, memorizes, and, if configured, reports multiple DHCP option 6 entries from DHCP replies that it received as DHCP client * A DHCP server at the NIC router can now be configured statically with multiple DNS server addresses to propagate * The 'dns_server_from' attribute of the DHCP server of the NIC router now supports the forwarding of multiple DNS server addresses * The automated run/nic_router_dhcp test tests all the above mentioned new functionality and reconfiguring it at runtime. The test was added to the autopilot. * All run scripts were adapted to fit the new NIC router configuration interface Fixes #3952
2020-11-16 14:43:40 +00:00
append_if [expr ![nic_router_2_managed]] config {
<config verbose_packets="no">
<policy label="test_client -> " domain="downlink"/>
nic_router: replace term "uplink" with "NIC client" BREAKS CONFIG COMPATIBILITY: This commit changes the configuration interface of the NIC router in a way that may break systems that use the component without proper adjustment! HOW TO ADJUST: At each occurrence of the '<uplink ...>' tag in a NIC router configuration replace the tag name 'uplink' with 'nic-client'. The rest of the tag stays the same. The term "uplink" for network interfaces in the router that have a NIC session client as back end was introduced in a time when Uplink sessions didn't yet exist. Now, they do and, although both an uplink and an Uplink session normally describe a network session between router and network device driver, they are based on two different service types (NIC and Uplink). This can easily cause confusion when integrating the router (the <uplink> is not related to Uplink sessions) or trying to understand its functioning (an 'Uplink' object has nothing to do with the Uplink service). Therefore, this commit introduces the more specific term "NIC client" for an interface that is based on a NIC session requested by the router. This doesn't imply any semantic changes at the NIC router. However, the commit also brings a broader update of the router's README and removes the term "downlink" that was used only in documentation to refer to interfaces backed by a NIC session provided by the router. The term was only associated with this meaning because it is the natural counterpart to an uplink. This isn't appropriate anymore as the terms for interface types have moved to a more technical level. The commit adjusts all scenarios in the basic Genode repositories properly. Fixes #4238
2021-07-27 11:52:21 +00:00
<nic-client domain="uplink"/>
nic_router: support multiple DHCP option 6 entries * The NIC router now considers, memorizes, and, if configured, reports multiple DHCP option 6 entries from DHCP replies that it received as DHCP client * A DHCP server at the NIC router can now be configured statically with multiple DNS server addresses to propagate * The 'dns_server_from' attribute of the DHCP server of the NIC router now supports the forwarding of multiple DNS server addresses * The automated run/nic_router_dhcp test tests all the above mentioned new functionality and reconfiguring it at runtime. The test was added to the autopilot. * All run scripts were adapted to fit the new NIC router configuration interface Fixes #3952
2020-11-16 14:43:40 +00:00
<domain name="uplink"/>
<domain name="downlink" interface="10.0.3.1/24">
<dhcp-server ip_first="10.0.3.2"
ip_last="10.0.3.2"
run/nic_router_dhcp: DHCP RENEW and some fixes * Test DHCP RENEW by the test client in the unmanaged variant. * Add event IDs to log output of test client in order to prevent false positive result in the managed variant. * Let managed and unmanaged variant have separate string patterns for 'run_genode_until' because they already had different output and it will differ even more as we don't want to test DHCP RENEW with the managed variant. * Delay first test client DHCP in order to fix unexpected sporadic initial IP config. * Remove some unnecessary code from the run script Fixes #4460
2022-03-28 14:16:48 +00:00
ip_lease_time_sec="6"
nic_router: config attribute 'dns_config_from' WARNING: BREAKS CONFIG COMPATIBILITY! This commit changes the configuration interface of the NIC router in a way that may break systems that use the component without proper adjustment! How to adjust: At each occurrence of the 'dns_server_from' attribute in a NIC router configuration replace the attribute name with 'dns_config_from'. The attribute value remains unaltered. DETAILED DESCRIPTION The new attribute name 'dns_config_from' reflects that also other aspects of the DNS configuration of the denominated domain are used by the DHCP server that holds the attribute. This commit is a preparation for forwarding also the domain name (DHCP option 15) with the mechanism behind the attribute. Ref #4246
2021-08-05 11:31:13 +00:00
dns_config_from="uplink"/>
nic_router: support multiple DHCP option 6 entries * The NIC router now considers, memorizes, and, if configured, reports multiple DHCP option 6 entries from DHCP replies that it received as DHCP client * A DHCP server at the NIC router can now be configured statically with multiple DNS server addresses to propagate * The 'dns_server_from' attribute of the DHCP server of the NIC router now supports the forwarding of multiple DNS server addresses * The automated run/nic_router_dhcp test tests all the above mentioned new functionality and reconfiguring it at runtime. The test was added to the autopilot. * All run scripts were adapted to fit the new NIC router configuration interface Fixes #3952
2020-11-16 14:43:40 +00:00
</domain>
</config>}
append config {
<route>
<service name="Nic"> <child name="nic_router_1"/> </service>}
append_if [nic_router_2_managed] config {
<service name="ROM" label="config">
<child name="report_rom"/>
</service>}
append config {
<any-service> <parent/> <any-child/> </any-service>
</route>
</start>
<start name="test_client">
<binary name="test-nic_router_dhcp-client"/>
<resource name="RAM" quantum="10M"/>
<config verbose="no"/>
<route>
<service name="Nic"> <child name="nic_router_2"/> </service>
<any-service> <parent/> <any-child/> </any-service>
</route>
</start>}
append_if [nic_router_2_managed] config {
<start name="report_rom">
<resource name="RAM" quantum="1M"/>
<provides> <service name="Report"/> <service name="ROM"/> </provides>
<config verbose="no">
<policy label="test_manager -> router_state"
report="nic_router_2 -> state"/>
<policy label="nic_router_2 -> config"
report="test_manager -> router_config"/>
</config>
</start>
<start name="test_manager">
<binary name="test-nic_router_dhcp-manager"/>
<resource name="RAM" quantum="1M"/>
<route>
<service name="ROM" label="router_state">
<child name="report_rom"/>
</service>
<service name="Report"> <child name="report_rom"/> </service>
<any-service> <parent/> <any-child/> </any-service>
</route>
</start>}
append config {
</config>}
install_config $config
set boot_modules {
init
dynamic_rom
nic_router
test-nic_router_dhcp-client
}
lappend_if [nic_router_2_managed] boot_modules test-nic_router_dhcp-manager
lappend_if [nic_router_2_managed] boot_modules report_rom
build_boot_image $boot_modules
append qemu_args " -nographic "
append_qemu_nic_args
run/nic_router_dhcp: DHCP RENEW and some fixes * Test DHCP RENEW by the test client in the unmanaged variant. * Add event IDs to log output of test client in order to prevent false positive result in the managed variant. * Let managed and unmanaged variant have separate string patterns for 'run_genode_until' because they already had different output and it will differ even more as we don't want to test DHCP RENEW with the managed variant. * Delay first test client DHCP in order to fix unexpected sporadic initial IP config. * Remove some unnecessary code from the run script Fixes #4460
2022-03-28 14:16:48 +00:00
if {[nic_router_2_managed]} {
append done_string ".*Event 1, DHCP request completed:.*\n"
nic_router: support multiple DHCP option 6 entries * The NIC router now considers, memorizes, and, if configured, reports multiple DHCP option 6 entries from DHCP replies that it received as DHCP client * A DHCP server at the NIC router can now be configured statically with multiple DNS server addresses to propagate * The 'dns_server_from' attribute of the DHCP server of the NIC router now supports the forwarding of multiple DNS server addresses * The automated run/nic_router_dhcp test tests all the above mentioned new functionality and reconfiguring it at runtime. The test was added to the autopilot. * All run scripts were adapted to fit the new NIC router configuration interface Fixes #3952
2020-11-16 14:43:40 +00:00
append done_string ".* IP lease time: 3600 seconds.*\n"
append done_string ".* Interface: 10.0.3.2/24.*\n"
append done_string ".* Router: 10.0.3.1.*\n"
append done_string ".* DNS server #1: 1.2.3.4.*\n"
append done_string ".* DNS server #2: 2.3.4.5.*\n"
append done_string ".* DNS server #3: 3.4.5.6.*\n"
nic_router: propagate dns domain name via dhcp With this commit, the NIC router DHCP client reads out the first DNS domain name (DHCP option 15) if any from a DHCP reply that generates an IPv4 config for a domain and stores the name together with the IPv4 config for that domain. DNS domain names are reported via the new report tag '<dns-domain>' if the 'config' attribute in the config tag '<report>' is set. Furthermore, the NIC router DHCP server becomes able to obtain a DNS domain name from another domain that has a DHCP client dynamically (given the config attribute 'dns_config_from' is set and no static DNS config is given) or statically from its configuration (new config tag '<dns-domain>') and propagate this name with DHCP replies (DHCP option 15). The 'nic_router_dhcp_*' tests are adapted to test the new feautures. The commit also gets rid of some mirrored files in 'test/nic_router_dhcp/manager'. Fixes #4246
2021-08-10 14:57:25 +00:00
append done_string ".* DNS domain name: genode.org.*\n"
run/nic_router_dhcp: DHCP RENEW and some fixes * Test DHCP RENEW by the test client in the unmanaged variant. * Add event IDs to log output of test client in order to prevent false positive result in the managed variant. * Let managed and unmanaged variant have separate string patterns for 'run_genode_until' because they already had different output and it will differ even more as we don't want to test DHCP RENEW with the managed variant. * Delay first test client DHCP in order to fix unexpected sporadic initial IP config. * Remove some unnecessary code from the run script Fixes #4460
2022-03-28 14:16:48 +00:00
append done_string ".*Event 2, DHCP request completed:.*\n"
nic_router: support multiple DHCP option 6 entries * The NIC router now considers, memorizes, and, if configured, reports multiple DHCP option 6 entries from DHCP replies that it received as DHCP client * A DHCP server at the NIC router can now be configured statically with multiple DNS server addresses to propagate * The 'dns_server_from' attribute of the DHCP server of the NIC router now supports the forwarding of multiple DNS server addresses * The automated run/nic_router_dhcp test tests all the above mentioned new functionality and reconfiguring it at runtime. The test was added to the autopilot. * All run scripts were adapted to fit the new NIC router configuration interface Fixes #3952
2020-11-16 14:43:40 +00:00
append done_string ".* IP lease time: 3600 seconds.*\n"
append done_string ".* Interface: 10.0.3.2/24.*\n"
append done_string ".* Router: 10.0.3.1.*\n"
append done_string ".* DNS server #1: 4.5.6.7.*\n"
append done_string ".* DNS server #2: 5.6.7.8.*\n"
run/nic_router_dhcp: DHCP RENEW and some fixes * Test DHCP RENEW by the test client in the unmanaged variant. * Add event IDs to log output of test client in order to prevent false positive result in the managed variant. * Let managed and unmanaged variant have separate string patterns for 'run_genode_until' because they already had different output and it will differ even more as we don't want to test DHCP RENEW with the managed variant. * Delay first test client DHCP in order to fix unexpected sporadic initial IP config. * Remove some unnecessary code from the run script Fixes #4460
2022-03-28 14:16:48 +00:00
append done_string ".*Event 3, DHCP request completed:.*\n"
nic_router: support multiple DHCP option 6 entries * The NIC router now considers, memorizes, and, if configured, reports multiple DHCP option 6 entries from DHCP replies that it received as DHCP client * A DHCP server at the NIC router can now be configured statically with multiple DNS server addresses to propagate * The 'dns_server_from' attribute of the DHCP server of the NIC router now supports the forwarding of multiple DNS server addresses * The automated run/nic_router_dhcp test tests all the above mentioned new functionality and reconfiguring it at runtime. The test was added to the autopilot. * All run scripts were adapted to fit the new NIC router configuration interface Fixes #3952
2020-11-16 14:43:40 +00:00
append done_string ".* IP lease time: 3600 seconds.*\n"
append done_string ".* Interface: 10.0.3.2/24.*\n"
append done_string ".* Router: 10.0.3.1.*\n"
append done_string ".* DNS server #1: 6.7.8.9.*\n"
run/nic_router_dhcp: DHCP RENEW and some fixes * Test DHCP RENEW by the test client in the unmanaged variant. * Add event IDs to log output of test client in order to prevent false positive result in the managed variant. * Let managed and unmanaged variant have separate string patterns for 'run_genode_until' because they already had different output and it will differ even more as we don't want to test DHCP RENEW with the managed variant. * Delay first test client DHCP in order to fix unexpected sporadic initial IP config. * Remove some unnecessary code from the run script Fixes #4460
2022-03-28 14:16:48 +00:00
append done_string ".*Event 4, DHCP request completed:.*\n"
nic_router: support multiple DHCP option 6 entries * The NIC router now considers, memorizes, and, if configured, reports multiple DHCP option 6 entries from DHCP replies that it received as DHCP client * A DHCP server at the NIC router can now be configured statically with multiple DNS server addresses to propagate * The 'dns_server_from' attribute of the DHCP server of the NIC router now supports the forwarding of multiple DNS server addresses * The automated run/nic_router_dhcp test tests all the above mentioned new functionality and reconfiguring it at runtime. The test was added to the autopilot. * All run scripts were adapted to fit the new NIC router configuration interface Fixes #3952
2020-11-16 14:43:40 +00:00
append done_string ".* IP lease time: 3600 seconds.*\n"
append done_string ".* Interface: 10.0.3.2/24.*\n"
append done_string ".* Router: 10.0.3.1.*\n"
nic_router: propagate dns domain name via dhcp With this commit, the NIC router DHCP client reads out the first DNS domain name (DHCP option 15) if any from a DHCP reply that generates an IPv4 config for a domain and stores the name together with the IPv4 config for that domain. DNS domain names are reported via the new report tag '<dns-domain>' if the 'config' attribute in the config tag '<report>' is set. Furthermore, the NIC router DHCP server becomes able to obtain a DNS domain name from another domain that has a DHCP client dynamically (given the config attribute 'dns_config_from' is set and no static DNS config is given) or statically from its configuration (new config tag '<dns-domain>') and propagate this name with DHCP replies (DHCP option 15). The 'nic_router_dhcp_*' tests are adapted to test the new feautures. The commit also gets rid of some mirrored files in 'test/nic_router_dhcp/manager'. Fixes #4246
2021-08-10 14:57:25 +00:00
append done_string ".* DNS domain name: genodians.org.*\n"
run/nic_router_dhcp: DHCP RENEW and some fixes * Test DHCP RENEW by the test client in the unmanaged variant. * Add event IDs to log output of test client in order to prevent false positive result in the managed variant. * Let managed and unmanaged variant have separate string patterns for 'run_genode_until' because they already had different output and it will differ even more as we don't want to test DHCP RENEW with the managed variant. * Delay first test client DHCP in order to fix unexpected sporadic initial IP config. * Remove some unnecessary code from the run script Fixes #4460
2022-03-28 14:16:48 +00:00
append done_string ".*Event 5, DHCP request completed:.*\n"
nic_router: support multiple DHCP option 6 entries * The NIC router now considers, memorizes, and, if configured, reports multiple DHCP option 6 entries from DHCP replies that it received as DHCP client * A DHCP server at the NIC router can now be configured statically with multiple DNS server addresses to propagate * The 'dns_server_from' attribute of the DHCP server of the NIC router now supports the forwarding of multiple DNS server addresses * The automated run/nic_router_dhcp test tests all the above mentioned new functionality and reconfiguring it at runtime. The test was added to the autopilot. * All run scripts were adapted to fit the new NIC router configuration interface Fixes #3952
2020-11-16 14:43:40 +00:00
append done_string ".* IP lease time: 3600 seconds.*\n"
append done_string ".* Interface: 10.0.3.2/24.*\n"
append done_string ".* Router: 10.0.3.1.*\n"
run/nic_router_dhcp: DHCP RENEW and some fixes * Test DHCP RENEW by the test client in the unmanaged variant. * Add event IDs to log output of test client in order to prevent false positive result in the managed variant. * Let managed and unmanaged variant have separate string patterns for 'run_genode_until' because they already had different output and it will differ even more as we don't want to test DHCP RENEW with the managed variant. * Delay first test client DHCP in order to fix unexpected sporadic initial IP config. * Remove some unnecessary code from the run script Fixes #4460
2022-03-28 14:16:48 +00:00
append done_string ".* DNS server #1: 1.2.3.4.*\n"
append done_string ".* DNS server #2: 2.3.4.5.*\n"
append done_string ".* DNS server #3: 3.4.5.6.*\n"
append done_string ".* DNS domain name: genode.org.*\n"
} else {
append done_string ".*Event 1, DHCP request completed:.*\n"
append done_string ".* IP lease time: 6 seconds.*\n"
append done_string ".* Interface: 10.0.3.2/24.*\n"
append done_string ".* Router: 10.0.3.1.*\n"
append done_string ".* DNS server #1: 1.2.3.4.*\n"
append done_string ".* DNS server #2: 2.3.4.5.*\n"
append done_string ".* DNS server #3: 3.4.5.6.*\n"
append done_string ".* DNS domain name: genode.org.*\n"
append done_string ".*Event 2, DHCP request completed:.*\n"
append done_string ".* IP lease time: 6 seconds.*\n"
append done_string ".* Interface: 10.0.3.2/24.*\n"
append done_string ".* Router: 10.0.3.1.*\n"
append done_string ".* DNS server #1: 4.5.6.7.*\n"
append done_string ".* DNS server #2: 5.6.7.8.*\n"
append done_string ".*Event 3, DHCP renew completed:.*\n"
append done_string ".* IP lease time: 6 seconds.*\n"
append done_string ".* Interface: 10.0.3.2/24.*\n"
append done_string ".* Router: 10.0.3.1.*\n"
append done_string ".* DNS server #1: 4.5.6.7.*\n"
append done_string ".* DNS server #2: 5.6.7.8.*\n"
append done_string ".*Event 4, DHCP request completed:.*\n"
append done_string ".* IP lease time: 6 seconds.*\n"
append done_string ".* Interface: 10.0.3.2/24.*\n"
append done_string ".* Router: 10.0.3.1.*\n"
append done_string ".* DNS server #1: 6.7.8.9.*\n"
append done_string ".*Event 5, DHCP request completed:.*\n"
append done_string ".* IP lease time: 6 seconds.*\n"
append done_string ".* Interface: 10.0.3.2/24.*\n"
append done_string ".* Router: 10.0.3.1.*\n"
nic_router: propagate dns domain name via dhcp With this commit, the NIC router DHCP client reads out the first DNS domain name (DHCP option 15) if any from a DHCP reply that generates an IPv4 config for a domain and stores the name together with the IPv4 config for that domain. DNS domain names are reported via the new report tag '<dns-domain>' if the 'config' attribute in the config tag '<report>' is set. Furthermore, the NIC router DHCP server becomes able to obtain a DNS domain name from another domain that has a DHCP client dynamically (given the config attribute 'dns_config_from' is set and no static DNS config is given) or statically from its configuration (new config tag '<dns-domain>') and propagate this name with DHCP replies (DHCP option 15). The 'nic_router_dhcp_*' tests are adapted to test the new feautures. The commit also gets rid of some mirrored files in 'test/nic_router_dhcp/manager'. Fixes #4246
2021-08-10 14:57:25 +00:00
append done_string ".* DNS domain name: genodians.org.*\n"
run/nic_router_dhcp: DHCP RENEW and some fixes * Test DHCP RENEW by the test client in the unmanaged variant. * Add event IDs to log output of test client in order to prevent false positive result in the managed variant. * Let managed and unmanaged variant have separate string patterns for 'run_genode_until' because they already had different output and it will differ even more as we don't want to test DHCP RENEW with the managed variant. * Delay first test client DHCP in order to fix unexpected sporadic initial IP config. * Remove some unnecessary code from the run script Fixes #4460
2022-03-28 14:16:48 +00:00
append done_string ".*Event 6, DHCP request completed:.*\n"
append done_string ".* IP lease time: 6 seconds.*\n"
append done_string ".* Interface: 10.0.3.2/24.*\n"
append done_string ".* Router: 10.0.3.1.*\n"
append done_string ".* DNS domain name: genodians.org.*\n"
append done_string ".*Event 7, DHCP request completed:.*\n"
append done_string ".* IP lease time: 6 seconds.*\n"
nic_router: fix exc. in Interface::handle_config_3 When Interface::handle_config_3 (third step of applying a new configuration to interfaces) tried to detach the interface from the current IP config because the old and new IP config differed, it did so using the new domain. The former steps of the reconfiguration already installed the new domain reference at the interface. Therefore, also the DHCP server of the new domain was used. This, however caused uncaught exceptions because detaching from an IP config includes dissolving all DHCP allocations. This dissolving of DHCP allocations now operated on a DHCP server (the one of the new domain) that wasn't related to the allocations and, in the worst case, caused an uncaught exception because the IPs were out of its range. That said, this commit ensures that detaching an interface from an IP config is always done on the domain from which the IP config originated. Normally, this is the domain the interface is attached to. But in the case of Interface::handle_config_3, it is another - the former domain the interface was attached to. The commit also adapts the nic_router_dhcp_* tests in a way that they reconfigure the router in a way that would trigger the uncaught exception without the fix. Fixes #4200
2021-06-24 12:34:13 +00:00
append done_string ".* Interface: 10.0.3.2/24.*\n"
append done_string ".* Router: 10.0.3.1.*\n"
nic_router: support multiple DHCP option 6 entries * The NIC router now considers, memorizes, and, if configured, reports multiple DHCP option 6 entries from DHCP replies that it received as DHCP client * A DHCP server at the NIC router can now be configured statically with multiple DNS server addresses to propagate * The 'dns_server_from' attribute of the DHCP server of the NIC router now supports the forwarding of multiple DNS server addresses * The automated run/nic_router_dhcp test tests all the above mentioned new functionality and reconfiguring it at runtime. The test was added to the autopilot. * All run scripts were adapted to fit the new NIC router configuration interface Fixes #3952
2020-11-16 14:43:40 +00:00
append done_string ".* DNS server #1: 1.2.3.4.*\n"
append done_string ".* DNS server #2: 2.3.4.5.*\n"
append done_string ".* DNS server #3: 3.4.5.6.*\n"
nic_router: propagate dns domain name via dhcp With this commit, the NIC router DHCP client reads out the first DNS domain name (DHCP option 15) if any from a DHCP reply that generates an IPv4 config for a domain and stores the name together with the IPv4 config for that domain. DNS domain names are reported via the new report tag '<dns-domain>' if the 'config' attribute in the config tag '<report>' is set. Furthermore, the NIC router DHCP server becomes able to obtain a DNS domain name from another domain that has a DHCP client dynamically (given the config attribute 'dns_config_from' is set and no static DNS config is given) or statically from its configuration (new config tag '<dns-domain>') and propagate this name with DHCP replies (DHCP option 15). The 'nic_router_dhcp_*' tests are adapted to test the new feautures. The commit also gets rid of some mirrored files in 'test/nic_router_dhcp/manager'. Fixes #4246
2021-08-10 14:57:25 +00:00
append done_string ".* DNS domain name: genode.org.*\n"
nic_router: support multiple DHCP option 6 entries * The NIC router now considers, memorizes, and, if configured, reports multiple DHCP option 6 entries from DHCP replies that it received as DHCP client * A DHCP server at the NIC router can now be configured statically with multiple DNS server addresses to propagate * The 'dns_server_from' attribute of the DHCP server of the NIC router now supports the forwarding of multiple DNS server addresses * The automated run/nic_router_dhcp test tests all the above mentioned new functionality and reconfiguring it at runtime. The test was added to the autopilot. * All run scripts were adapted to fit the new NIC router configuration interface Fixes #3952
2020-11-16 14:43:40 +00:00
run/nic_router_dhcp: DHCP RENEW and some fixes * Test DHCP RENEW by the test client in the unmanaged variant. * Add event IDs to log output of test client in order to prevent false positive result in the managed variant. * Let managed and unmanaged variant have separate string patterns for 'run_genode_until' because they already had different output and it will differ even more as we don't want to test DHCP RENEW with the managed variant. * Delay first test client DHCP in order to fix unexpected sporadic initial IP config. * Remove some unnecessary code from the run script Fixes #4460
2022-03-28 14:16:48 +00:00
}
nic_router_dhcp_*: raise timeouts On okl4, pistachio, sel4 the test didn't come up fast enough in order to still experience the first configuration of NIC router #1. This commit doubles the lifetime of the first configuration of NIC router #1 to 4 seconds and raises the overall test timeout accordingly. Ref #4555
2022-07-26 09:38:46 +00:00
run_genode_until $done_string 35
Reference in New Issue Copy Permalink