[READY] - reenable dhcpv6 kea and nixosTest core updates

[sarcasticadmin]

Description of PR

Relates to: #537 #753

Reenable the dhcpv6 server without any rpi specific tftpboot options. We will reenable the option when #753 and the rpi firmware supports it.

Previous Behavior

• disabled dhcpv6 on core server

New Behavior

• reenable dhcpv6 on core server
• add driverInteractive specific config for nixosTest.core to allow for ssh to each test vm
• reenable driverInteractive graphics during tests

Tests

• nix build .#checks.x86_64-linux.core.driverInteractive works as expected for all vms
• nix build .#checks.x86_64-linux.core works

[kylerisse]

@sarcasticadmin this is cool. I tested the following and confirmed all functional. Please let me know if there's a better method or if there is anything else I should confirm. 🚢 If not I'll go ahead and merge.

1. Both build commands you specified work
2. I didn't know a better way to test the ssh config so I did the following to confirm SSH is listening: nix run .#checks.x86_64-linux.core.driverInteractive once in the shell I did start_all() which booted all 3 vms. On the host I ran netstat -lan | grep 222 | grep LISTEN and got the following output:

tcp        0      0 0.0.0.0:2222            0.0.0.0:*               LISTEN     
tcp        0      0 0.0.0.0:2223            0.0.0.0:*               LISTEN     
tcp        0      0 0.0.0.0:2224            0.0.0.0:*               LISTEN 

3. Confirmed DHCP by reviewing the console output after boot and found this:

client1 # [  104.848672] systemd-networkd[492]: eth1: DHCPv6 client: Sent Renew
client1 # [  104.854158] systemd-networkd[492]: eth1: DHCPv6 client: Next retransmission in 9s
client1 # [  104.861349] systemd-networkd[492]: eth1: DHCPv6 client: Processed Reply message
client1 # [  104.864365] systemd-networkd[492]: eth1: DHCPv6 client: T1 expires in 1min 33s
client1 # [  104.868636] systemd-networkd[492]: eth1: DHCPv6 client: T2 expires in 2min 17s
client1 # [  104.872425] systemd-networkd[492]: eth1: DHCPv6 client: Valid lifetime expires in 5min
client1 # [  104.876315] systemd-networkd[492]: eth1: DHCPv6 client: State changed: renew -> bound
client1 # [  104.880296] systemd-networkd[492]: eth1: DHCPv6 address 2001:470:f026:103:d8c::1/128 (valid for 4min 59s, preferred for 3min 6s)

[sarcasticadmin]

@kylerisse thanks for diving in and confirm the changes 🚀

2. I didn't know a better way to test the ssh config so I did the following to confirm SSH is listening: `nix run .#checks.x86_64-linux.core.driverInteractive` once in the shell I did `start_all()` which booted all 3 vms. On the host I ran `netstat -lan | grep 222 | grep LISTEN` and got the following output:

tcp        0      0 0.0.0.0:2222            0.0.0.0:*               LISTEN     
tcp        0      0 0.0.0.0:2223            0.0.0.0:*               LISTEN     
tcp        0      0 0.0.0.0:2224            0.0.0.0:*               LISTEN 

You can connect to each node via root and no password 🙂 Glad its looking for so far on your end

3. Confirmed DHCP by reviewing the console output after boot and found this:

client1 # [  104.848672] systemd-networkd[492]: eth1: DHCPv6 client: Sent Renew
client1 # [  104.854158] systemd-networkd[492]: eth1: DHCPv6 client: Next retransmission in 9s
client1 # [  104.861349] systemd-networkd[492]: eth1: DHCPv6 client: Processed Reply message
client1 # [  104.864365] systemd-networkd[492]: eth1: DHCPv6 client: T1 expires in 1min 33s
client1 # [  104.868636] systemd-networkd[492]: eth1: DHCPv6 client: T2 expires in 2min 17s
client1 # [  104.872425] systemd-networkd[492]: eth1: DHCPv6 client: Valid lifetime expires in 5min
client1 # [  104.876315] systemd-networkd[492]: eth1: DHCPv6 client: State changed: renew -> bound
client1 # [  104.880296] systemd-networkd[492]: eth1: DHCPv6 address 2001:470:f026:103:d8c::1/128 (valid for 4min 59s, preferred for 3min 6s)

Nice, yes that's looking good!