From fca6a74d0c61dd34f252deb900c52027d9fc373f Mon Sep 17 00:00:00 2001 From: Dmitry Vyukov Date: Fri, 3 Jan 2020 09:58:48 +0100 Subject: executor: connect virt_wifi to veth virt_wifi docs say that the enslaved device won't be usable on itself. It's probably not a good idea to make lo unusable. Enslave a dedicated veth instead. --- sys/linux/vnet.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'sys/linux/vnet.txt') diff --git a/sys/linux/vnet.txt b/sys/linux/vnet.txt index af12f2120..6d05cdd29 100644 --- a/sys/linux/vnet.txt +++ b/sys/linux/vnet.txt @@ -53,7 +53,7 @@ mac_addr_link_local { mac_addr_link_local_values = 0x0, 0x1, 0x2, 0x3, 0xe # This corresponds to the last digit in DEV_MAC/DEV_IPV4/DEV_IPV6 in executor/common_linux.h -type netdev_addr_id int8[10:45] +type netdev_addr_id int8[10:47] mac_addr [ empty array[const[0x0, int8], 6] -- cgit mrf-deployment