以下是解決嵌入式板子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地址?？梢試L試停止該服務，命令為`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地址發生變化?？梢詸z查`/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`等），這些工具也可能會對網絡接口進行自動配置?？梢試L試關閉或配置這些工具，以避免它們對`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:~#
*博客內容為網友個人發布，僅代表博主個人觀點，如有侵權請聯系工作人員刪除。
