问题[network-bridge](ubuntu)

我在 Ubuntu 22.04.5 LTS 服务器上。网络端口已中继。我正尝试使用 netplan 在 VLAN 202 上设置一个绑定为从属的虚拟网桥。以下不起作用：

$ cat /etc/netplan/00-bond-bridge-config.yaml
network:
  version: 2
  renderer: networkd
  ethernets:
    eno3:
      dhcp4: false
    eno4:
      dhcp4: false
  bonds:
    bond0:
      dhcp4: false
      interfaces: [eno3, eno4]
      parameters:
        mode: active-backup
        mii-monitor-interval: 100
  vlans:
    bond0.202:
        id: 202
        link: bond0
  bridges:
    br0:
      dhcp4: false
      interfaces: [bond0.202]
      addresses: [192.168.1.2/24]
      routes:
        - to: default
          via: 192.168.1.1
      nameservers:
        addresses: [1.1.1.1, 8.8.8.8]
        search: []

我无法 ping 通我的 Ubuntu 主机。我的 yaml 文件中有什么错误？

问题前的解释

我正在尝试使用 Ubuntu Core 20.04 在树莓派上配置 LXD。它的本地 IP 被初始化为192.168.2.64. 在我运行之前，lxd init它可以毫无问题地连接到网络。在配置过程中，我创建了一个地址为 192.168.2.33/27 的网桥，它应该允许192.168.2.33-62容器的范围。但是，在保存配置文件后，Pi 从本地网络中消失了。当我插入 HDMI 电缆时，它说可以通过它访问192.168.2.64并显示指向 Ubuntu 帐户页面的链接。我无法通过网络访问它，也无法直接插入键盘（我猜是 Ubuntu Core 的东西？）。

现在的问题

我的网桥子网有问题，还是我在这个过程中搞砸了其他东西？如何连接和重新配置设备，或更改安装操作系统的 micro SD 卡中的文件？如果可能的话，我不想删除磁盘的内容。

与普通熊相比，我对网络的熟悉程度要低得多，因此也感谢任何解释或额外支持。

提前致谢。

我无法在来宾 VM 内建立网络以在运行官方 Ubuntu 20.04 映像的 Raspberry Pi 4 8​​GB 上使用 KVM。据我所知，我的网络配置正确。而且我真的希望有人会告诉我我做错了什么，并可以为我指出更好的文档。我已经阅读了 netplan 的文档、十几个关于 KVM 设置的不同教程，甚至还查看了一些与 CPU 配置相关的 QEMU 文档，因为我发现 QEMU 对 aarch64 的构建不如对 x86_64 的构建好。

我通过与在十几个教程中找到的相同方式安装 KVM：

$ sudo apt install qemu qemu-kvm libvirt-clients libvirt-daemon-system virtinst bridge-utils
$ sudo systemctl enable libvirtd
$ sudo systemctl start libvirtd

这是我的网络计划：

$ cat /etc/netplan/01-netcfg.yaml 
network:
    ethernets:
        eth0:
            dhcp4: false
            dhcp6: false
            optional: true
            nameservers:
                addresses: [1.1.1.1, 1.0.0.1]
    wifis:
        wlan0:
            dhcp4: true
            dhcp6: false
            optional: true
            access-points:
                "censored":
                    password: "censored"
    bridges:
        br0:
            interfaces: [eth0]
            nameservers:
                addresses: [1.1.1.1, 1.0.0.1]
            parameters:
                stp: true
                forward-delay: 4
            dhcp4: true
            dhcp6: false
    version: 2
    renderer: networkd

然后我为 KVM 域定义了它：

$ sudo mkdir -p /opt/kvm
$ sudo nano /opt/kvm/host-bridge.xml

<network>
    <name>host-bridge</name>
    <forward mode="bridge"/>
    <bridge name="br0"/>
</network>

$ virsh net-define /opt/kvm/host-bridge.xml
$ virsh net-start host-bridge
$ virsh net-autostart host-bridge

然后我检查了它是否确实存在并且配置正确：

$ virsh net-list --all
 Name          State      Autostart   Persistent
--------------------------------------------------
 default       inactive   no          yes
 host-bridge   active     yes         yes

开始创建 VM 后，我检查了它的 vnet0 是否已正确添加到网桥：

$ sudo virt-install --name Test-VM --ram=2048 --vcpus=2 --cpu max --hvm --disk path=/opt/vhd/test-vhd,size=16 --cdrom /opt/iso/ubuntu-20.04.1-live-server-arm64.iso --network bridge=br0 --graphics vnc

$ virsh domiflist Test-VM
 Interface   Type     Source   Model    MAC
-----------------------------------------------------------
 vnet0       bridge   br0      virtio   52:54:00:64:58:9e

$ brctl show
bridge name     bridge id               STP enabled     interfaces
br0             8000.dca632b43f5b       yes             eth0
                                                        vnet0
docker0         8000.0242aa58079a       no
docker1         8000.024296884d89       no              veth239b4dd
                                                        veth76e81fc
                                                        vethdffe7c7
                                                        vethef20e5a

然而，在这一切之后，我的客人内部的网络似乎不起作用。它只是不停地试图获得一个 IP 地址，但它永远不会得到一个。有什么我错过的吗？

我还检查了虚拟机实际上正在使用桥接接口，它似乎是：

$ virsh edit Test-VM
...
    <interface type='bridge'>
      <mac address='52:54:00:64:58:9e'/>
      <source bridge='br0'/>
      <model type='virtio'/>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
    </interface>
...

这是客人正在旋转的屏幕。如您所见，我通过主机上的桥接接口具有完整的网络能力，可以通过 VNC 连接到 KVM。 截屏

我的主机上有几个静态公共 IP 地址。我想将该 IP 分配给某个容器，但我真的找不到任何关于它的更新信息。我尝试使用辅助 IP 创建一个新网络并将其分配给一个容器，但是在这样做之后，容器失去了互联网连接。

我做了什么：

lxc network create publicip #New network
lxc network add publicip ipv4.address 10.3.3.3/30 #add random local IP
lxc network add publicip ipv4.routes 138.*.16.151/32 #add route to the actual public IP that I want to assign to the container
lxc network attach publicip myContainer eth0 #attach it as eth0 interface to the container
lxc config device set myContainer eth0 ipv4.address 10.3.3.2 #assign container local IP from the range of the new network I created with first command

任何想法我做错了什么，我的容器失去了与外界的联系？

输出：lxc network show publicip

config:
  ipv4.address: 10.3.3.3/30
  ipv4.nat: "true"
  ipv4.routes: 138.201.16.151/32
  ipv6.address: fd42:cefa:6941:1e25::1/64
  ipv6.nat: "true"
description: ""
name: publicip
type: bridge
used_by:
- /1.0/instances/myContainer
managed: true
status: Created
locations:
- none

和 lxc 列表的输出：

+--------+---------+---------------------+-----------------------------------------------+-----------+-----------+
| myContainer    | RUNNING | 10.3.3.2 (eth0)     | fd42:cefa:6941:1e25:216:3eff:fefe:2e29 (eth1) | CONTAINER | 0         |
|        |         |                     | fd42:cefa:6941:1e25:216:3eff:fe6a:3cdc (eth0) |           |           |
|        |         |                     | fd42:cefa:6941:1e25:216:3eff:fe0d:a57c (eth2) |           |           |
+--------+---------+---------------------+-----------------------------------------------+-----------+-----------+

所以我有一台新安装的ubuntu机器。我打算输入一些网络设置，但是这个文件丢失了：/etc/network/interfaces. 我也检查过root。机器上有本地环回。不应该吗？是否只是从头开始创建它并在重新启动时自动拾取？

目标是让来宾与主机在同一网络上（使用与主机相同的 DHCP 服务器）。

我已经到了主机通过外部 DHCP 配置的地步，来宾配置了静态 IP，它们可以通信，主机可以与网络的其余部分通信，但来宾不能。

我正在遵循有关使用 NetworkManager 创建网桥并在 KVM 中使用它的指南（我还从主机中删除了所有 Wi-Fi 连接，并从 KVM 中删除了默认网桥）：

$ nmcli con add ifname br0 type bridge con-name br0
$ nmcli con add type bridge-slave ifname enp59s0 master br0
$ nmcli con modify br0 bridge.stp no
$ nmcli con up br0
$ nmcli c
NAME                  UUID                                  TYPE      DEVICE  
br0                   39f90a3b-6090-4b4f-a9c4-76d6b980c8c4  bridge    br0     
bridge-slave-enp59s0  dd58e274-8cfa-4102-b524-fd16d96516b8  ethernet  enp59s0 
docker0               901ac863-2d2b-4351-9b81-fbc2096e398b  bridge    docker0
$ brctl show br0
bridge name  bridge id          STP enabled interfaces
br0          8000.54bf6428c24c  no          enp59s0

在ip a br0 中获取 IP，enp59s0是从接口，因此它显示没有 IP。

/tmp/br0.xml：

<network>
  <name>br0</name>
  <forward mode="bridge"/>
  <bridge name="br0" />
</network>

设置 KVM：

$ virsh net-define /tmp/br0.xml
$ virsh net-start br0
$ virsh net-autostart br0
$ virsh net-list --all
 Name                 State      Autostart     Persistent
----------------------------------------------------------
 br0                  active     yes           yes

访客/etc/netplan/01-netcfg.yaml：

network:
  version: 2
  renderer: networkd
  ethernets:
    ens3:
      addresses: [192.168.5.100/24]
      gateway4: 192.168.5.254
      dhcp4: no
      dhcp6: no

当虚拟机运行时有vnet0：

$ nmcli c
NAME                  UUID                                  TYPE      DEVICE  
br0                   39f90a3b-6090-4b4f-a9c4-76d6b980c8c4  bridge    br0     
bridge-slave-enp59s0  dd58e274-8cfa-4102-b524-fd16d96516b8  ethernet  enp59s0 
docker0               901ac863-2d2b-4351-9b81-fbc2096e398b  bridge    docker0 
vnet0                 1e6cdf02-8f57-4670-b6a7-b72e15151137  tun       vnet0  
$ brctl show br0
bridge name  bridge id          STP enabled interfaces
br0          8000.54bf6428c24c  no          enp59s0
                                            vnet0

在br0上的主机上的 Wireshark 中，我看到所有尝试从访客到网络以及从网络到访客的数据包（我尝试从访客 ping/连接到外部服务器并从外部服务器 ping/连接到访客）。但是连接没有通过，来宾无法与网络的其余部分进行通信。

这看起来像一个主机桥问题。桥怎么了？

双频 USB 适配器 2.4/5GHz 1200(866+300)Mbps 无线速度与 802.11ac

所以最近我购买了带有 CD 上驱动程序的双频 USB 适配器，以安装在 Windows、Mac 和 Linux 上。

我正在使用Ubuntu 18.04.4 LTS - 64 位

1. 将适配器连接到USB端口后，我检查了输入终端的端口lsusb，我得到以下信息：

Bus 001 Device 007: ID 0bda:b812 Realtek Semiconductor Corp.

2. sudo dkms status然后我什么也没得到。

3. 然后我在 CD 中名为 ( RTL81888192EUS_linux_v4.3.0.4_11485.20140519chmod +x install.sh ) 的文件夹中安装 Wi-Fi 2.4GHz，在终端中输入，然后sudo ./install.sh我得到以下结果：

##################################################
Realtek Wi-Fi driver Auto installation script
Novembor, 21 2011 v1.1.0
##################################################
Decompress the driver source tar ball:
    rtl8188EUS_linux_v4.3.0.4_11485.20140519.tar.gz
rtl8188EUS_linux_v4.3.0.4_11485.20140519/ (all files)

Authentication requested [root] for make clean:
cd hal/OUTSRC/ ; rm -fr */*.mod.c */*.mod */*.o */.*.cmd */*.ko
cd hal/OUTSRC/ ; rm -fr *.mod.c *.mod *.o .*.cmd *.ko 
cd hal/led ; rm -fr *.mod.c *.mod *.o .*.cmd *.ko
cd hal ; rm -fr */*/*.mod.c */*/*.mod */*/*.o */*/.*.cmd */*/*.ko
cd hal ; rm -fr */*.mod.c */*.mod */*.o */.*.cmd */*.ko
cd hal ; rm -fr *.mod.c *.mod *.o .*.cmd *.ko
cd core/efuse ; rm -fr *.mod.c *.mod *.o .*.cmd *.ko
cd core ; rm -fr *.mod.c *.mod *.o .*.cmd *.ko
cd os_dep/linux ; rm -fr *.mod.c *.mod *.o .*.cmd *.ko
cd os_dep ; rm -fr *.mod.c *.mod *.o .*.cmd *.ko
cd platform ; rm -fr *.mod.c *.mod *.o .*.cmd *.ko
rm -fr Module.symvers ; rm -fr Module.markers ; rm -fr modules.order
rm -fr *.mod.c *.mod *.o .*.cmd *.ko *~
rm -fr .tmp_versions
Authentication requested [root] for make driver:
make ARCH=x86_64 CROSS_COMPILE= -C /lib/modules/4.15.0-101-generic/build M=/home/luisito/Documents/RTL81888192EUS_linux_v4.3.0.4_11485.20140519/driver/rtl8188EUS_linux_v4.3.0.4_11485.20140519  modules
make[1]: Entering directory '/usr/src/linux-headers-4.15.0-101-generic'
CC [M]  /home/luisito/Documents/RTL81888192EUS_linux_v4.3.0.4_11485.20140519/driver/rtl8188EUS_linux_v4.3.0.4_11485.20140519/core/rtw_cmd.o
In file included from /home/luisito/Documents/RTL81888192EUS_linux_v4.3.0.4_11485.20140519/driver/rtl8188EUS_linux_v4.3.0.4_11485.20140519/include/osdep_service.h:41:0,
                 from /home/luisito/Documents/RTL81888192EUS_linux_v4.3.0.4_11485.20140519/driver/rtl8188EUS_linux_v4.3.0.4_11485.20140519/include/drv_types.h:32,
                 from /home/luisito/Documents/RTL81888192EUS_linux_v4.3.0.4_11485.20140519/driver/rtl8188EUS_linux_v4.3.0.4_11485.20140519/core/rtw_cmd.c:22:
/home/luisito/Documents/RTL81888192EUS_linux_v4.3.0.4_11485.20140519/driver/rtl8188EUS_linux_v4.3.0.4_11485.20140519/include/osdep_service_linux.h: In function ‘_init_timer’:
/home/luisito/Documents/RTL81888192EUS_linux_v4.3.0.4_11485.20140519/driver/rtl8188EUS_linux_v4.3.0.4_11485.20140519/include/osdep_service_linux.h:253:8: error: ‘_timer {aka struct timer_list}’ has no member named ‘data’
  ptimer->data = (unsigned long)cntx;
        ^~
/home/luisito/Documents/RTL81888192EUS_linux_v4.3.0.4_11485.20140519/driver/rtl8188EUS_linux_v4.3.0.4_11485.20140519/include/osdep_service_linux.h:254:2: error: implicit declaration of function ‘init_timer’; did you mean ‘_init_timer’? [-Werror=implicit-function-declaration]
  init_timer(ptimer);
  ^~~~~~~~~~
  _init_timer
In file included from /home/luisito/Documents/RTL81888192EUS_linux_v4.3.0.4_11485.20140519/driver/rtl8188EUS_linux_v4.3.0.4_11485.20140519/include/drv_types.h:32:0,
             from /home/luisito/Documents/RTL81888192EUS_linux_v4.3.0.4_11485.20140519/driver/rtl8188EUS_linux_v4.3.0.4_11485.20140519/core/rtw_cmd.c:22:
/home/luisito/Documents/RTL81888192EUS_linux_v4.3.0.4_11485.20140519/driver/rtl8188EUS_linux_v4.3.0.4_11485.20140519/include/osdep_service.h: In function ‘thread_enter’:
/home/luisito/Documents/RTL81888192EUS_linux_v4.3.0.4_11485.20140519/driver/rtl8188EUS_linux_v4.3.0.4_11485.20140519/include/osdep_service.h:342:2: error: implicit declaration of function ‘allow_signal’; did you mean ‘do_signal’? [-Werror=implicit-function-declaration]
  allow_signal(SIGTERM);
  ^~~~~~~~~~~~
  do_signal
/home/luisito/Documents/RTL81888192EUS_linux_v4.3.0.4_11485.20140519/driver/rtl8188EUS_linux_v4.3.0.4_11485.20140519/include/osdep_service.h: In function ‘flush_signals_thread’:
/home/luisito/Documents/RTL81888192EUS_linux_v4.3.0.4_11485.20140519/driver/rtl8188EUS_linux_v4.3.0.4_11485.20140519/include/osdep_service.h:352:6: error: implicit declaration of function ‘signal_pending’; did you mean ‘timer_pending’? [-Werror=implicit-function-declaration]
  if (signal_pending (current))
      ^~~~~~~~~~~~~~
      timer_pending
/home/luisito/Documents/RTL81888192EUS_linux_v4.3.0.4_11485.20140519/driver/rtl8188EUS_linux_v4.3.0.4_11485.20140519/include/osdep_service.h:354:3: error: implicit declaration of function ‘flush_signals’; did you mean ‘do_signal’? [-Werror=implicit-function-declaration]
   flush_signals(current);
   ^~~~~~~~~~~~~
   do_signal
cc1: some warnings being treated as errors
scripts/Makefile.build:330: recipe for target '/home/luisito/Documents/RTL81888192EUS_linux_v4.3.0.4_11485.20140519/driver/rtl8188EUS_linux_v4.3.0.4_11485.20140519/core/rtw_cmd.o' failed
make[2]: *** [/home/luisito/Documents/RTL81888192EUS_linux_v4.3.0.4_11485.20140519/driver/rtl8188EUS_linux_v4.3.0.4_11485.20140519/core/rtw_cmd.o] Error 1
Makefile:1577: recipe for target '_module_/home/luisito/Documents/RTL81888192EUS_linux_v4.3.0.4_11485.20140519/driver/rtl8188EUS_linux_v4.3.0.4_11485.20140519' failed
make[1]: *** [_module_/home/luisito/Documents/RTL81888192EUS_linux_v4.3.0.4_11485.20140519/driver/rtl8188EUS_linux_v4.3.0.4_11485.20140519] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-4.15.0-101-generic'
Makefile:1318: recipe for target 'modules' failed
make: *** [modules] Error 2
##################################################
Compile make driver error: 2
Please check error Mesg
##################################################

似乎该文件夹中不存在文件rtw_cmd.o，因此它已失败。

4.最后，我在 CD 中名为 ( RTL8821AU_Linux_v5.2.6_21981_COEX20170206-6760.20170407 ) 的文件夹中安装了 Wi-Fi 5GHz，在终端中输入chmod +x install.sh，然后sudo ./install.sh我得到以下结果：

##################################################
Realtek Wi-Fi driver Auto installation script
Novembor, 21 2011 v1.1.0
##################################################
Decompress the driver source tar ball:
    rtl8821AU_WiFi_linux_v5.2.6_21981.20170407_COEX20170206-6760.tar.gz
rtl8821AU_WiFi_linux_v5.2.6_21981.20170407_COEX20170206-6760/ (all files)

Authentication requested [root] for make clean:
#make -C /lib/modules/4.15.0-101-generic/build M=/home/luisito/Documents/RTL8821AU_Linux_v5.2.6_21981_COEX20170206-6760.20170407/driver/rtl8821AU_WiFi_linux_v5.2.6_21981.20170407_COEX20170206-6760 clean
cd hal ; rm -fr */*/*/*.mod.c */*/*/*.mod */*/*/*.o */*/*/.*.cmd */*/*/*.ko
cd hal ; rm -fr */*/*.mod.c */*/*.mod */*/*.o */*/.*.cmd */*/*.ko
cd hal ; rm -fr */*.mod.c */*.mod */*.o */.*.cmd */*.ko
cd hal ; rm -fr *.mod.c *.mod *.o .*.cmd *.ko
cd core/efuse ; rm -fr *.mod.c *.mod *.o .*.cmd *.ko
cd core ; rm -fr *.mod.c *.mod *.o .*.cmd *.ko
cd os_dep/linux ; rm -fr *.mod.c *.mod *.o .*.cmd *.ko
cd os_dep ; rm -fr *.mod.c *.mod *.o .*.cmd *.ko
cd platform ; rm -fr *.mod.c *.mod *.o .*.cmd *.ko
rm -fr Module.symvers ; rm -fr Module.markers ; rm -fr modules.order
rm -fr *.mod.c *.mod *.o .*.cmd *.ko *~
rm -fr .tmp_versions
Authentication requested [root] for make driver:
make ARCH=x86_64 CROSS_COMPILE= -C /lib/modules/4.15.0-101-generic/build M=/home/luisito/Documents/RTL8821AU_Linux_v5.2.6_21981_COEX20170206-6760.20170407/driver/rtl8821AU_WiFi_linux_v5.2.6_21981.20170407_COEX20170206-6760  modules
make[1]: Entering directory '/usr/src/linux-headers-4.15.0-101-generic'
  CC [M]  /home/luisito/Documents/RTL8821AU_Linux_v5.2.6_21981_COEX20170206-6760.20170407/driver/rtl8821AU_WiFi_linux_v5.2.6_21981.20170407_COEX20170206-6760/core/rtw_cmd.o
In file included from /home/luisito/Documents/RTL8821AU_Linux_v5.2.6_21981_COEX20170206-6760.20170407/driver/rtl8821AU_WiFi_linux_v5.2.6_21981.20170407_COEX20170206-6760/include/osdep_service.h:47:0,
                 from /home/luisito/Documents/RTL8821AU_Linux_v5.2.6_21981_COEX20170206-6760.20170407/driver/rtl8821AU_WiFi_linux_v5.2.6_21981.20170407_COEX20170206-6760/include/drv_types.h:32,
                 from /home/luisito/Documents/RTL8821AU_Linux_v5.2.6_21981_COEX20170206-6760.20170407/driver/rtl8821AU_WiFi_linux_v5.2.6_21981.20170407_COEX20170206-6760/core/rtw_cmd.c:22:
/home/luisito/Documents/RTL8821AU_Linux_v5.2.6_21981_COEX20170206-6760.20170407/driver/rtl8821AU_WiFi_linux_v5.2.6_21981.20170407_COEX20170206-6760/include/osdep_service_linux.h: In function ‘_init_timer’:
/home/luisito/Documents/RTL8821AU_Linux_v5.2.6_21981_COEX20170206-6760.20170407/driver/rtl8821AU_WiFi_linux_v5.2.6_21981.20170407_COEX20170206-6760/include/osdep_service_linux.h:288:8: error: ‘_timer {aka struct timer_list}’ has no member named ‘data’
  ptimer->data = (unsigned long)cntx;
        ^~
/home/luisito/Documents/RTL8821AU_Linux_v5.2.6_21981_COEX20170206-6760.20170407/driver/rtl8821AU_WiFi_linux_v5.2.6_21981.20170407_COEX20170206-6760/include/osdep_service_linux.h:289:2: error: implicit declaration of function ‘init_timer’; did you mean ‘_init_timer’? [-Werror=implicit-function-declaration]
  init_timer(ptimer);
  ^~~~~~~~~~
  _init_timer
In file included from /home/luisito/Documents/RTL8821AU_Linux_v5.2.6_21981_COEX20170206-6760.20170407/driver/rtl8821AU_WiFi_linux_v5.2.6_21981.20170407_COEX20170206-6760/include/drv_types.h:32:0,
                 from /home/luisito/Documents/RTL8821AU_Linux_v5.2.6_21981_COEX20170206-6760.20170407/driver/rtl8821AU_WiFi_linux_v5.2.6_21981.20170407_COEX20170206-6760/core/rtw_cmd.c:22:
/home/luisito/Documents/RTL8821AU_Linux_v5.2.6_21981_COEX20170206-6760.20170407/driver/rtl8821AU_WiFi_linux_v5.2.6_21981.20170407_COEX20170206-6760/include/osdep_service.h: In function ‘thread_enter’:
/home/luisito/Documents/RTL8821AU_Linux_v5.2.6_21981_COEX20170206-6760.20170407/driver/rtl8821AU_WiFi_linux_v5.2.6_21981.20170407_COEX20170206-6760/include/osdep_service.h:375:2: error: implicit declaration of function ‘allow_signal’; did you mean ‘do_signal’? [-Werror=implicit-function-declaration]
  allow_signal(SIGTERM);
  ^~~~~~~~~~~~
  do_signal
/home/luisito/Documents/RTL8821AU_Linux_v5.2.6_21981_COEX20170206-6760.20170407/driver/rtl8821AU_WiFi_linux_v5.2.6_21981.20170407_COEX20170206-6760/include/osdep_service.h: In function ‘flush_signals_thread’:
/home/luisito/Documents/RTL8821AU_Linux_v5.2.6_21981_COEX20170206-6760.20170407/driver/rtl8821AU_WiFi_linux_v5.2.6_21981.20170407_COEX20170206-6760/include/osdep_service.h:385:6: error: implicit declaration of function ‘signal_pending’; did you mean ‘timer_pending’? [-Werror=implicit-function-declaration]
  if (signal_pending(current))
      ^~~~~~~~~~~~~~
      timer_pending
/home/luisito/Documents/RTL8821AU_Linux_v5.2.6_21981_COEX20170206-6760.20170407/driver/rtl8821AU_WiFi_linux_v5.2.6_21981.20170407_COEX20170206-6760/include/osdep_service.h:386:3: error: implicit declaration of function ‘flush_signals’; did you mean ‘do_signal’? [-Werror=implicit-function-declaration]
   flush_signals(current);
   ^~~~~~~~~~~~~
   do_signal
cc1: some warnings being treated as errors
scripts/Makefile.build:330: recipe for target '/home/luisito/Documents/RTL8821AU_Linux_v5.2.6_21981_COEX20170206-6760.20170407/driver/rtl8821AU_WiFi_linux_v5.2.6_21981.20170407_COEX20170206-6760/core/rtw_cmd.o' failed
make[2]: *** [/home/luisito/Documents/RTL8821AU_Linux_v5.2.6_21981_COEX20170206-6760.20170407/driver/rtl8821AU_WiFi_linux_v5.2.6_21981.20170407_COEX20170206-6760/core/rtw_cmd.o] Error 1
Makefile:1577: recipe for target '_module_/home/luisito/Documents/RTL8821AU_Linux_v5.2.6_21981_COEX20170206-6760.20170407/driver/rtl8821AU_WiFi_linux_v5.2.6_21981.20170407_COEX20170206-6760' failed
make[1]: *** [_module_/home/luisito/Documents/RTL8821AU_Linux_v5.2.6_21981_COEX20170206-6760.20170407/driver/rtl8821AU_WiFi_linux_v5.2.6_21981.20170407_COEX20170206-6760] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-4.15.0-101-generic'
Makefile:1877: recipe for target 'modules' failed
make: *** [modules] Error 2
##################################################
Compile make driver error: 2
Please check error Mesg
##################################################

似乎该文件夹中不存在文件rtw_cmd.o，因此它也失败了。

- 那么任何人都可以修复Wi-Fi 2.4GHz 和 5GHz 两个文件夹中的文件rtw_cmd.o吗？

文件夹位于以下链接中：Linux 的双频 USB 适配器 Wifi

我在 Ubuntu 20.04 Desktop 上使用了 netplan，并使用了一个 yaml 文件，就像这个网站上的文件一样：

https://webby.land/2018/04/27/bridging-under-ubuntu-18-04/

但是，我的主机现在没有ip？我该如何解决这个问题？我仍然可以 ping 出并接收连接，但我不能使用 xrdp，因为我不知道使用什么 IP 来连接。

2 个新的 Ubuntu Server 20.04 安装（1 个在 Hyper-V 上，1 个在裸机上）在引导时无法正确启动桥接接口。手动运行netplan apply将成功启动网桥（目前在引导时在 crontab 中作为一种解决方法）。

在我看来，在应用 IP 或运营商启动之前正在应用网桥上的网关并因此出错？纯粹是猜测，但考虑到它在应用后启动时工作正常，肯定看起来像是某种竞争条件。

任何帮助，将不胜感激。netplan 配置和输出如下。

/etc/netplan/50-netinit-config.yaml

network:
  version: 2
  renderer: networkd
  ethernets:
    eth0:
      dhcp4: no
  bridges:
    br0:
      interfaces: [eth0]
      dhcp4: no
      addresses: [192.168.1.220/24]
      gateway4: 192.168.1.1
      nameservers:
        addresses: [8.8.8.8, 8.8.4.4]
        search: [blah.net.au]

ifconfig -a

br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        ether 00:15:5d:86:b8:01  txqueuelen 1000  (Ethernet)
        RX packets 1406  bytes 136275 (136.2 KB)
        RX errors 0  dropped 581  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        ether 00:15:5d:86:b8:01  txqueuelen 1000  (Ethernet)
        RX packets 1918  bytes 213299 (213.2 KB)
        RX errors 0  dropped 190  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 560  bytes 43120 (43.1 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 560  bytes 43120 (43.1 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

网络统计 -rn

Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface

networkctl -a 状态

 1: lo
             Link File: /usr/lib/systemd/network/99-default.link
          Network File: n/a
                  Type: loopback
                 State: carrier (unmanaged)
                   MTU: 65536
  Queue Length (Tx/Rx): 1/1
               Address: 127.0.0.1

 2: eth0
             Link File: /usr/lib/systemd/network/99-default.link
          Network File: /run/systemd/network/10-netplan-eth0.network
                  Type: ether
                 State: enslaved (configured)
                  Path: acpi-VMBUS:00
                Driver: hv_netvsc
            HW Address: 00:15:5d:86:b8:01 (Microsoft Corporation)
                   MTU: 1500 (min: 68, max: 65521)
  Queue Length (Tx/Rx): 64/64
      Auto negotiation: no
                 Speed: 1Gbps
                Duplex: full

May 03 21:25:55 seraph-test systemd-networkd[759]: eth0: Link UP
May 03 21:25:56 seraph-test systemd-networkd[759]: eth0: Gained carrier

 3: br0
               Link File: /usr/lib/systemd/network/99-default.link
            Network File: /run/systemd/network/10-netplan-br0.network
                    Type: bridge
                   State: carrier (failed)
                  Driver: bridge
              HW Address: 00:15:5d:86:b8:01 (Microsoft Corporation)
                     MTU: 1500 (min: 68, max: 65535)
           Forward Delay: 15s
              Hello Time: 2s
                 Max Age: 20s
             Ageing Time: 5min
                Priority: 32768
                     STP: no
  Multicast IGMP Version: 2
    Queue Length (Tx/Rx): 1/1
                     DNS: 8.8.8.8
                          8.8.4.4
          Search Domains: teese.net.au

May 03 21:25:55 seraph-test systemd-udevd[502]: br0: Could not generate persistent MAC: No data available
May 03 21:25:55 seraph-test systemd-networkd[759]: br0: netdev ready
May 03 21:25:55 seraph-test systemd-networkd[759]: br0: Link UP
May 03 21:25:55 seraph-test systemd-networkd[759]: br0: Gained carrier
May 03 21:25:55 seraph-test systemd-networkd[759]: br0: Lost carrier
May 03 21:25:55 seraph-test systemd-networkd[759]: br0: Could not set route: Nexthop has invalid gateway. Network is unreachable
May 03 21:25:55 seraph-test systemd-networkd[759]: br0: Failed
May 03 21:25:56 seraph-test systemd-networkd[759]: br0: Gained carrier

我有一台带有 3 个网络接口的计算机：

• eth_adsl : 与我的 ADSL 盒子连接的以太网接口
• eth_local ：与我的本地网络链接的以太网接口
• wlan_local : 我的本地网络的 WIFI 接口

这台计算机是我本地网络中其他计算机（和设备）的网关。它转发来自和发送到 Internet 的包。有了这台电脑的WIFI，我想做一个AP（接入点）。为了简化配置，我在两个本地接口之间使用了一个网桥（参见下面的 /etc/network interfaces）

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# Interface de boucle local
auto lo
iface lo inet loopback

# Interface Ethernet secondaire 
# interface de connection a Internet
auto eth_adsl
iface eth_adsl inet dhcp

# WIFI
iface wlan_local inet static
        wireless-mode master

#Bridge
auto 
bridge_local
iface bridge_local inet static
        address 192.168.0.1
        netmask 255.255.255.0
        broadcast 192.168.0.255
        bridge_ports eth_local wlan_local
        post-up /etc/init.d/isc-dhcp-server start
        pre-down /etc/init.d/isc-dhcp-server stop

在我的 DHCP 服务器中，我进行了以下配置（/etc/default/isc-dhcp-server）

INTERFACES= "bridge_local"

结果： 本地网络中与以太网连接的其他计算机正常工作，但尝试通过 WIFI 连接的计算机无法正常工作。他们可以与 AP 关联，但在获得有效 IP 之后是不可能的。所以似乎 DHCP 不适用于接口 wlan_local.... 这很奇怪，因为我在 /var/log/syslog 中没有任何关于 DHCP 的错误消息

我被这个问题困扰了好几天。你有什么想法或测试吗？非常感谢

我的发行版是 Ubuntu 16.04.6 LTS