以下是解决嵌入式板子eth0网口IP变化问题的几种方法
加入技术交流群
以下是解决嵌入式板子eth0网口IP变化问题的几种方法：
### 检查网络配置文件
- **检查配置文件内容**：查看`/etc/network/interface
s`文件，
确认是否将`eth0`配置为动态获取IP地址，即`iface eth0 inet dhcp`。
如果是，改为静态IP配置，如：
```
auto eth0
iface eth0 inet static
address 192.168.1.100
netmask 255.255.255.0
gateway 192.168.1.1
```
- **检查是否有重复或冲突的配置**：确保文件中没有其他可能导致IP地址变动的配置，
例如重复的`auto eth0`或`iface eth0 inet dhcp`等。
### 检查系统服务与进程
- **检查DHCP服务**：如果系统中运行了DHCP客户端服务，如`dhclient`，
可能会自动获取并更新IP地址。可以尝试停止该服务，命令为`sudo systemctl stop dhclient`，
或者禁用该服务，命令为`sudo systemctl disable dhclient`。
- **检查其他网络管理工具**：某些系统可能使用了其他网络管理工具，
如`NetworkManager`或`netplan`，这些工具可能会覆盖手动配置的IP地址。
可以尝试停止或禁用这些服务，例如`sudo systemctl stop NetworkManager`。
### 检查硬件与驱动
- **检查网卡硬件**：确认网卡硬件正常工作，无故障。
可以尝试更换网卡或检查网卡连接是否松动。
- **检查网卡驱动**：确保网卡驱动程序是最新的，并且与系统兼容。
可以尝试更新网卡驱动，
例如在Debian/Ubuntu系统中使用命令`sudo apt-get update && sudo apt-get upgrade`。
### 检查系统日志
- **查看系统日志**：查看系统日志文件，
如`/var/log/syslog`或`/var/log/messages`，以了解IP地址变化的原因。
可以使用命令`grep eth0 /var/log/syslog`或
`grep eth0 /var/log/messages`来查找与`eth0`相关的日志信息。
### 其他方法
- **检查系统是否被克隆**：如果系统是通过克隆创建的，可能会导致网卡名称或MAC地址发生变化。可以检查`/etc/udev/rules.d/70-persistent-net.rules`文件，确认网卡名称和MAC地址是否正确。
- **检查是否有其他设备抢占IP**：在某些网络环境中，可能存在其他设备与嵌入式板子抢占相同的IP地址。可以尝试在其他设备上检查IP地址配置，避免冲突。
查了日志以后：
root@myd-imx8mm:~# grep eth0 /var/log/syslog
May 22 05:24:50 myd-imx8mm connmand[3747]: eth0 {create} index 2 type 1 <ETHER>
May 22 05:24:50 myd-imx8mm connmand[3747]: eth0 {update} flags 4099 <UP>
May 22 05:24:50 myd-imx8mm connmand[3747]: eth0 {newlink} index 2 address 42:F0:75:57:3E:FB mtu 1500
May 22 05:24:50 myd-imx8mm connmand[3747]: eth0 {newlink} index 2 operstate 2 <DOWN>
May 22 05:24:50 myd-imx8mm connmand[3747]: Adding interface eth0 [ ethernet ]
May 22 05:24:51 myd-imx8mm kernel: [ 1.601157] fec 30be0000.ethernet eth0: registered PHC device 0
May 22 05:24:51 myd-imx8mm kernel: [ 6.428819] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
May 22 05:24:51 myd-imx8mm avahi-daemon[3726]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.100.102.
May 22 05:24:51 myd-imx8mm connmand[3747]: eth0 {add} address 192.168.100.102/24 label eth0 family 2
May 22 05:24:51 myd-imx8mm avahi-daemon[3726]: New relevant interface eth0.IPv4 for mDNS.
May 22 05:24:51 myd-imx8mm connmand[3747]: eth0 {add} route 192.168.100.0 gw 0.0.0.0 scope 253 <LINK>
May 22 05:24:51 myd-imx8mm avahi-daemon[3726]: Registering new address record for 192.168.100.102 on eth0.IPv4.
May 22 05:25:27 myd-imx8mm kernel: [ 44.322208] fec 30be0000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
May 22 05:25:27 myd-imx8mm kernel: [ 44.330018] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
May 22 05:25:27 myd-imx8mm connmand[3747]: eth0 {add} route ff00:: gw :: scope 0 <UNIVERSE>
May 22 05:25:27 myd-imx8mm connmand[3747]: eth0 {add} route fe80:: gw :: scope 0 <UNIVERSE>
May 22 05:25:27 myd-imx8mm connmand[3747]: eth0 {update} flags 69699 <UP,RUNNING,LOWER_UP>
May 22 05:25:27 myd-imx8mm connmand[3747]: eth0 {newlink} index 2 address 42:F0:75:57:3E:FB mtu 1500
May 22 05:25:27 myd-imx8mm connmand[3747]: eth0 {newlink} index 2 operstate 6 <UP>
May 22 05:25:27 myd-imx8mm avahi-daemon[3726]: Registering new address record for 192.168.30.202 on eth0.IPv4.
May 22 05:25:27 myd-imx8mm connmand[3747]: eth0 {add} address 192.168.30.202/24 label eth0 family 2
May 22 05:25:27 myd-imx8mm connmand[3747]: eth0 {add} route 192.168.30.0 gw 0.0.0.0 scope 253 <LINK>
May 22 05:25:29 myd-imx8mm avahi-daemon[3726]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::40f0:75ff:fe57:3efb.
May 22 05:25:29 myd-imx8mm avahi-daemon[3726]: New relevant interface eth0.IPv6 for mDNS.
May 22 05:25:29 myd-imx8mm avahi-daemon[3726]: Registering new address record for fe80::40f0:75ff:fe57:3efb on eth0.*.
May 22 05:25:29 myd-imx8mm connmand[3747]: eth0 {RX} 68 packets 48953 bytes
May 22 05:25:29 myd-imx8mm connmand[3747]: eth0 {TX} 18 packets 2648 bytes
May 22 05:25:29 myd-imx8mm connmand[3747]: eth0 {update} flags 4099 <UP>
May 22 05:25:29 myd-imx8mm connmand[3747]: eth0 {newlink} index 2 address 42:F0:75:57:3E:FB mtu 1500
May 22 05:25:29 myd-imx8mm connmand[3747]: eth0 {newlink} index 2 operstate 2 <DOWN>
May 22 05:25:29 myd-imx8mm avahi-daemon[3726]: Withdrawing address record for 192.168.30.202 on eth0.
May 22 05:25:29 myd-imx8mm avahi-daemon[3726]: Withdrawing address record for 192.168.100.102 on eth0.
May 22 05:25:29 myd-imx8mm avahi-daemon[3726]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.100.102.
May 22 05:25:29 myd-imx8mm avahi-daemon[3726]: Interface eth0.IPv4 no longer relevant for mDNS.
May 22 05:25:29 myd-imx8mm kernel: [ 46.368758] fec 30be0000.ethernet eth0: Link is Down
May 22 05:25:29 myd-imx8mm avahi-daemon[3726]: Withdrawing address record for fe80::40f0:75ff:fe57:3efb on eth0.
May 22 05:25:29 myd-imx8mm avahi-daemon[3726]: Leaving mDNS multicast group on interface eth0.IPv6 with address fe80::40f0:75ff:fe57:3efb.
May 22 05:25:29 myd-imx8mm avahi-daemon[3726]: Interface eth0.IPv6 no longer relevant for mDNS.
May 22 05:25:29 myd-imx8mm connmand[3747]: eth0 {del} address 192.168.30.202/24 label eth0
May 22 05:25:29 myd-imx8mm connmand[3747]: eth0 {del} route 192.168.30.0 gw 0.0.0.0 scope 253 <LINK>
May 22 05:25:29 myd-imx8mm connmand[3747]: eth0 {del} address 192.168.100.102/24 label eth0
May 22 05:25:29 myd-imx8mm connmand[3747]: eth0 {del} route 192.168.100.0 gw 0.0.0.0 scope 253 <LINK>
May 22 05:25:29 myd-imx8mm kernel: [ 46.388724] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
May 22 05:25:29 myd-imx8mm connmand[3747]: eth0 {del} route ff00:: gw :: scope 0 <UNIVERSE>
May 22 05:25:29 myd-imx8mm connmand[3747]: eth0 {del} route fe80:: gw :: scope 0 <UNIVERSE>
May 22 05:27:15 myd-imx8mm avahi-daemon[3726]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.100.102.
May 22 05:27:15 myd-imx8mm connmand[3747]: eth0 {add} address 192.168.100.102/24 label eth0 family 2
May 22 05:27:15 myd-imx8mm avahi-daemon[3726]: New relevant interface eth0.IPv4 for mDNS.
May 22 05:27:15 myd-imx8mm avahi-daemon[3726]: Registering new address record for 192.168.100.102 on eth0.IPv4.
May 22 05:27:15 myd-imx8mm connmand[3747]: eth0 {add} route 192.168.100.0 gw 0.0.0.0 scope 253 <LINK>
May 22 05:28:19 myd-imx8mm kernel: [ 216.354208] fec 30be0000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
May 22 05:28:19 myd-imx8mm kernel: [ 216.362022] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
May 22 05:28:19 myd-imx8mm connmand[3747]: eth0 {add} route ff00:: gw :: scope 0 <UNIVERSE>
May 22 05:28:19 myd-imx8mm connmand[3747]: eth0 {add} route fe80:: gw :: scope 0 <UNIVERSE>
May 22 05:28:19 myd-imx8mm connmand[3747]: eth0 {RX} 68 packets 48953 bytes
May 22 05:28:19 myd-imx8mm connmand[3747]: eth0 {TX} 18 packets 2648 bytes
May 22 05:28:19 myd-imx8mm connmand[3747]: eth0 {update} flags 69699 <UP,RUNNING,LOWER_UP>
May 22 05:28:19 myd-imx8mm connmand[3747]: eth0 {newlink} index 2 address 42:F0:75:57:3E:FB mtu 1500
May 22 05:28:19 myd-imx8mm connmand[3747]: eth0 {newlink} index 2 operstate 6 <UP>
May 22 05:28:19 myd-imx8mm avahi-daemon[3726]: Registering new address record for 192.168.30.202 on eth0.IPv4.
May 22 05:28:19 myd-imx8mm connmand[3747]: eth0 {add} address 192.168.30.202/24 label eth0 family 2
May 22 05:28:19 myd-imx8mm connmand[3747]: eth0 {add} route 192.168.30.0 gw 0.0.0.0 scope 253 <LINK>
May 22 05:28:21 myd-imx8mm avahi-daemon[3726]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::40f0:75ff:fe57:3efb.
May 22 05:28:21 myd-imx8mm avahi-daemon[3726]: New relevant interface eth0.IPv6 for mDNS.
May 22 05:28:21 myd-imx8mm avahi-daemon[3726]: Registering new address record for fe80::40f0:75ff:fe57:3efb on eth0.*.
May 22 05:28:25 myd-imx8mm avahi-daemon[3726]: Registering new address record for 192.168.20.44 on eth0.IPv4.
May 22 05:28:25 myd-imx8mm connmand[3747]: eth0 {add} address 192.168.20.44/24 label eth0 family 2
May 22 05:28:25 myd-imx8mm connmand[3747]: eth0 {add} route 192.168.20.0 gw 0.0.0.0 scope 253 <LINK>
May 22 05:28:25 myd-imx8mm connmand[3747]: eth0 {add} route 192.168.9.1 gw 0.0.0.0 scope 253 <LINK>
May 22 05:28:25 myd-imx8mm connmand[3747]: eth0 {add} route 114.114.114.114 gw 192.168.9.1 scope 0 <UNIVERSE>
May 22 05:28:25 myd-imx8mm connmand[3747]: eth0 {add} route 8.8.4.4 gw 192.168.9.1 scope 0 <UNIVERSE>
May 22 05:47:39 myd-imx8mm connmand[3747]: eth0 {RX} 128154 packets 81763098 bytes
May 22 05:47:39 myd-imx8mm connmand[3747]: eth0 {TX} 2204 packets 631335 bytes
May 22 05:47:39 myd-imx8mm connmand[3747]: eth0 {update} flags 4099 <UP>
May 22 05:47:39 myd-imx8mm avahi-daemon[3726]: Withdrawing address record for 192.168.30.202 on eth0.
May 22 05:47:39 myd-imx8mm avahi-daemon[3726]: Withdrawing address record for 192.168.20.44 on eth0.
May 22 05:47:39 myd-imx8mm avahi-daemon[3726]: Withdrawing address record for 192.168.100.102 on eth0.
May 22 05:47:39 myd-imx8mm avahi-daemon[3726]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.100.102.
May 22 05:47:39 myd-imx8mm avahi-daemon[3726]: Interface eth0.IPv4 no longer relevant for mDNS.
May 22 05:47:39 myd-imx8mm kernel: [ 1376.544633] fec 30be0000.ethernet eth0: Link is Down
May 22 05:47:39 myd-imx8mm connmand[3747]: eth0 {newlink} index 2 address 42:F0:75:57:3E:FB mtu 1500
May 22 05:47:39 myd-imx8mm connmand[3747]: eth0 {newlink} index 2 operstate 2 <DOWN>
May 22 05:47:39 myd-imx8mm avahi-daemon[3726]: Withdrawing address record for fe80::40f0:75ff:fe57:3efb on eth0.
May 22 05:47:39 myd-imx8mm avahi-daemon[3726]: Leaving mDNS multicast group on interface eth0.IPv6 with address fe80::40f0:75ff:fe57:3efb.
May 22 05:47:39 myd-imx8mm avahi-daemon[3726]: Interface eth0.IPv6 no longer relevant for mDNS.
May 22 05:47:39 myd-imx8mm connmand[3747]: eth0 {del} address 192.168.30.202/24 label eth0
May 22 05:47:39 myd-imx8mm connmand[3747]: eth0 {del} route 192.168.30.0 gw 0.0.0.0 scope 253 <LINK>
May 22 05:47:39 myd-imx8mm connmand[3747]: eth0 {del} address 192.168.20.44/24 label eth0
May 22 05:47:39 myd-imx8mm connmand[3747]: eth0 {del} route 192.168.20.0 gw 0.0.0.0 scope 253 <LINK>
May 22 05:47:39 myd-imx8mm kernel: [ 1376.576527] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
May 22 05:47:39 myd-imx8mm connmand[3747]: eth0 {del} address 192.168.100.102/24 label eth0
May 22 05:47:39 myd-imx8mm connmand[3747]: eth0 {del} route 192.168.100.0 gw 0.0.0.0 scope 253 <LINK>
May 22 05:47:39 myd-imx8mm connmand[3747]: eth0 {del} route ff00:: gw :: scope 0 <UNIVERSE>
May 22 05:47:39 myd-imx8mm connmand[3747]: eth0 {del} route fe80:: gw :: scope 0 <UNIVERSE>
May 22 05:47:41 myd-imx8mm kernel: [ 1378.594204] fec 30be0000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
May 22 05:47:41 myd-imx8mm kernel: [ 1378.602023] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
May 22 05:47:41 myd-imx8mm connmand[3747]: eth0 {add} route ff00:: gw :: scope 0 <UNIVERSE>
May 22 05:47:41 myd-imx8mm connmand[3747]: eth0 {add} route fe80:: gw :: scope 0 <UNIVERSE>
May 22 05:47:41 myd-imx8mm connmand[3747]: eth0 {RX} 128154 packets 81763098 bytes
May 22 05:47:41 myd-imx8mm connmand[3747]: eth0 {TX} 2204 packets 631335 bytes
May 22 05:47:41 myd-imx8mm connmand[3747]: eth0 {update} flags 69699 <UP,RUNNING,LOWER_UP>
May 22 05:47:41 myd-imx8mm connmand[3747]: eth0 {newlink} index 2 address 42:F0:75:57:3E:FB mtu 1500
May 22 05:47:41 myd-imx8mm connmand[3747]: eth0 {newlink} index 2 operstate 6 <UP>
May 22 05:47:41 myd-imx8mm avahi-daemon[3726]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.30.202.
May 22 05:47:41 myd-imx8mm avahi-daemon[3726]: New relevant interface eth0.IPv4 for mDNS.
May 22 05:47:41 myd-imx8mm avahi-daemon[3726]: Registering new address record for 192.168.30.202 on eth0.IPv4.
May 22 05:47:41 myd-imx8mm connmand[3747]: eth0 {add} address 192.168.30.202/24 label eth0 family 2
May 22 05:47:41 myd-imx8mm connmand[3747]: eth0 {add} route 192.168.30.0 gw 0.0.0.0 scope 253 <LINK>
May 22 05:47:43 myd-imx8mm avahi-daemon[3726]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::40f0:75ff:fe57:3efb.
May 22 05:47:43 myd-imx8mm avahi-daemon[3726]: New relevant interface eth0.IPv6 for mDNS.
May 22 05:47:43 myd-imx8mm avahi-daemon[3726]: Registering new address record for fe80::40f0:75ff:fe57:3efb on eth0.*.
May 22 05:47:47 myd-imx8mm avahi-daemon[3726]: Registering new address record for 192.168.20.44 on eth0.IPv4.
May 22 05:47:47 myd-imx8mm connmand[3747]: eth0 {add} address 192.168.20.44/24 label eth0 family 2
May 22 05:47:47 myd-imx8mm connmand[3747]: eth0 {add} route 192.168.20.0 gw 0.0.0.0 scope 253 <LINK>
May 22 05:47:47 myd-imx8mm connmand[3747]: eth0 {add} route 192.168.9.1 gw 0.0.0.0 scope 253 <LINK>
May 22 05:47:47 myd-imx8mm connmand[3747]: eth0 {add} route 114.114.114.114 gw 192.168.9.1 scope 0 <UNIVERSE>
May 22 05:47:47 myd-imx8mm connmand[3747]: eth0 {add} route 8.8.4.4 gw 192.168.9.1 scope 0 <UNIVERSE>
May 22 19:51:15 myd-imx8mm connmand[3747]: eth0 {del} address 192.168.30.202/24 label eth0
May 22 19:51:15 myd-imx8mm avahi-daemon[3726]: Withdrawing address record for 192.168.30.202 on eth0.
May 22 19:51:15 myd-imx8mm connmand[3747]: eth0 {del} route 192.168.30.0 gw 0.0.0.0 scope 253 <LINK>
May 22 19:51:15 myd-imx8mm avahi-daemon[3726]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.30.202.
May 22 19:51:15 myd-imx8mm avahi-daemon[3726]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.20.44.
May 22 19:51:15 myd-imx8mm connmand[3747]: eth0 {add} address 192.168.100.102/24 label eth0 family 2
May 22 19:51:15 myd-imx8mm avahi-daemon[3726]: Registering new address record for 192.168.100.102 on eth0.IPv4.
May 22 19:51:15 myd-imx8mm connmand[3747]: eth0 {add} route 192.168.100.0 gw 0.0.0.0 scope 253 <LINK>
May 22 19:51:16 myd-imx8mm avahi-daemon[3726]: Withdrawing address record for 192.168.20.44 on eth0.
May 22 19:51:16 myd-imx8mm connmand[3747]: eth0 {del} address 192.168.20.44/24 label eth0
May 22 19:51:16 myd-imx8mm connmand[3747]: eth0 {del} route 192.168.20.0 gw 0.0.0.0 scope 253 <LINK>
May 22 19:51:16 myd-imx8mm avahi-daemon[3726]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.20.44.
May 22 19:51:16 myd-imx8mm avahi-daemon[3726]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.100.102.从日志来看，`connmand`和`avahi-daemon`这两个服务对`eth0`的IP地址进行了
频繁的添加和删除操作，导致IP地址不断变化。以下是针对这两个服务的解决方法：
### 1. 关闭或配置`connmand`服务
`connmand`是一个网络管理工具，它可能会自动配置网络接口的IP地址。
如果不需要`connmand`管理`eth0`接口，可以尝试关闭它。
- **关闭`connmand`服务**
```bash
sudo systemctl stop connmand
sudo systemctl disable connmand
```
- **配置`connmand`服务**
如果需要使用`connmand`，但希望它不要自动更改IP地址，
可以尝试修改`connmand`的配置文件（通常位于`/etc/connman/main.conf`），
将`TetheringTechnologies=none`添加到文件中，以禁用自动配置功能。
### 2. 配置`avahi-daemon`服务
`avahi-daemon`是一个用于多播DNS（mDNS）的服务，
它主要用于在局域网内自动发现和解析主机名。
从日志来看，`avahi-daemon`也在对`eth0`的IP地址进行操作。
- **关闭`avahi-daemon`服务**
如果不需要`avahi-daemon`的功能，可以关闭它：
```bash
sudo systemctl stop avahi-daemon
sudo systemctl disasble avahi-daemon
```
- **配置`avahi-daemon`服务**
如果需要使用`avahi-daemon`，但希望它不要干扰`eth0`的IP地址配置，可以尝试修改`avahi-daemon`的配置文件（通常位于`/etc/avahi/avahi-daemon.conf`），将`enable-dbus=no`添加到文件中，以禁用通过DBus接口对网络接口的自动配置。
### 3. 配置静态IP地址
为了确保`eth0`接口使用固定的IP地址，可以在网络配置文件中设置静态IP地址。根据你的系统类型，可以参考以下配置方法：
- **Debian/Ubuntu系统（使用`/etc/network/interfaces`文件）**
```bash
auto eth0
iface eth0 inet static
address 192.168.20.44
netmask 255.255.255.0
gateway 192.168.20.1
```
修改完成后，重启网络服务：
```bash
sudo systemctl restart networking
```
- **使用`netplan`配置（适用于较新的Ubuntu系统）**
如果你的系统使用`netplan`进行网络配置，可以在`/etc/netplan/`目录下找到配置文件（如`01-netcfg.yaml`），并进行如下配置：
```yaml
network:
version: 2
ethernets:
eth0:
dhcp4: no
addresses:
- 192.168.20.44/24
gateway4: 192.168.20.1
nameservers:
addresses:
- 8.8.8.8
- 8.8.4.4
```
修改完成后，应用配置：
```bash
sudo netplan apply
```
### 4. 检查其他可能的网络管理工具
除了`connmand`和`avahi-daemon`，系统中可能还存在其他网络管理工具（如`NetworkManager`等），这些工具也可能会对网络接口进行自动配置。可以尝试关闭或配置这些工具，以避免它们对`eth0`接口的IP地址进行更改。
- **检查`NetworkManager`服务**
```bash
sudo systemctl status NetworkManager
```
如果`NetworkManager`正在运行，可以尝试关闭它：
```bash
sudo systemctl stop NetworkManager
sudo systemctl disable NetworkManager
```
### 5. 监控网络接口状态
在完成上述配置后，可以使用以下命令监控`eth0`接口的状态，确保IP地址不再发生变化：
```bash
watch -n 1 "ip addr show eth0"
```
通过以上步骤，应该可以解决`eth0`接口IP地址不断变化的问题。
如果问题仍然存在，可以进一步检查系统中是否有其他脚本或程序在后台修改网络配置。
root@myd-imx8mm:~# sudo systemctl stop connmand Failed to stop connmand.service: Unit connmand.service not loaded. root@myd-imx8mm:~# root@myd-imx8mm:~# root@myd-imx8mm:~# root@myd-imx8mm:~# root@myd-imx8mm:~# systemctl disable connmand Failed to disable unit: Unit file connmand.service does not exist. root@myd-imx8mm:~# root@myd-imx8mm:~# root@myd-imx8mm:~# root@myd-imx8mm:~# sudo systemctl stop avahi-daemon Warning: Stopping avahi-daemon.service, but it can still be activated by: avahi-daemon.socket root@myd-imx8mm:~# root@myd-imx8mm:~# root@myd-imx8mm:~# sudoo systemctl disable avahi-daemon -sh: sudoo: command not found root@myd-imx8mm:~# sudo systemctl disable avahi-daemon Removed /etc/systemd/system/multi-user.target.wants/avahi-daemon.service. Removed /etc/systemd/system/dbus-org.freedesktop.Avahi.service. Removed /etc/systemd/system/sockets.target.wants/avahi-daemon.socket. root@myd-imx8mm:~#
*博客内容为网友个人发布，仅代表博主个人观点，如有侵权请联系工作人员删除。
