The network interface names may vary depending on the actual situation.
Display information for a specific network interface
$ ifconfig <dev>
To display information for a specific network interface (e.g., eth0), you can enter ifconfig eth0.
Set the IP address
$ ifconfig eth0 <ip> netmask <nmask>
To set the IP address of the eth0 interface to 192.168.1.101 and the subnet mask to 255.255.255.0, you can use the command ifconfig eth0 192.168.1.101 netmask 255.255.255.0.
Enable a network interface
$ ifconfig <dev> up
To enable the eth0 interface, you can use the ifconfig eth0 up command.
Disable a network interface
$ ifconfig <dev> down
To disable the eth0 interface, use the ifconfig eth0 down command.
Set the MAC address
$ ifconfig <dev> down
$ ifconfig <dev> hw ether <new MAC address>
$ ifconfig <dev> up
Different operating systems may have some differences. Some systems may not allow you to directly set the MAC address through ifconfig, or additional steps may be required.
Command-Line Configuration of WIFI Hotspot (AP) Mode
Check if AP mode is supported
$ iw list | grep AP
Device supports AP-side u-APSD.
* AP
* AP/VLAN
HE Iftypes: AP
HE Iftypes: AP
* wake up on EAP identity request
* AP/VLAN
* #{ managed } <= 1, #{ AP, P2P-client, P2P-GO } <= 1, #{ P2P-device } <= 1,
Driver supports full state transitions for AP/GO clients
Driver/device bandwidth changes during BSS lifetime (AP/GO mode)
* AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
AP/VLAN indicates that the hardware supports AP mode.
Create a Virtual Interface to Create a Hotspot Mode
$ sudo iw dev <wirelessname> interface add <virtualwlanname> type __ap
<wirelessname> is the name of the real wireless network card, which can be viewed through ifconfig. <virtualwlanname> is the name of the virtual wireless network card.
For example:
$ sudo iw dev wlan0 interface add wlo2 type __ap
Add a physical address to the virtual network card:
$ sudo ip link set dev <virtualwlanname> address 22:33:44:55:66:00
You can fill in any address. If there is a conflict, try another one. <virtualwlanname> is the name of the virtual wireless network card.
For example:
$ sudo ip link set dev wlo2 address 22:33:44:55:66:00
<wirelessname> is the name of your wireless network card, <virtualwlanname> is the name of the virtual network card, and <SSID> and <password> are the name and password of the created hotspot Wi-Fi, respectively.
For example:
$ sudo create_ap -c 11 wlo2 wlan0 m3 88888888
If the created hotspot gets stuck and the following error is reported when starting the hotspot:
#RTNETLINK answers: Device or resource busy
#ERROR: Maybe your WiFi adapter does not fully support virtual interfaces.
# Try again with --no-virt.
You can stop the previously created hotspot as follows and then restart it:
$ sudo create_ap --stop <virtualwlanname>
<virtualwlanname> is the name of the virtual network card.
Use a Physical Interface to Create a Hotspot Mode
Install dependencies and create_ap:
$ sudo apt-get install util-linux hostapd dnsmasq iptables iproute2 haveged make
$ git clone https://github.com/oblique/create_ap
$ cd */create_ap
$ sudo make install
Note: After replacing the rootfs in this way, there may be issues with the mount UUID. You can use blkid to view the correct UUID and then modify /etc/fstab.
Connect a USB drive to the board. The USB drive should be at least 16GB in size because the packaged image will be relatively large.
The generated package name will be in the format like rootfs.img.
/mnt/usb is the mount directory of the USB drive.
For the board that needs to replace this system, you can burn the rootfs separately. If you need to repackage it into a complete image, refer to [Firmware Unpacking and Packing](../08-Advanced/03-Firmware Unpacking and Packing.md).
Enter the root User in the Ubuntu Desktop Edition
The default login user for the latest desktop edition system is kickpi.
When using some commands in the Terminal of the desktop edition system, you may encounter permission issues, such as ifconfig.
In this case, you need root permissions. You can add sudo before the command or switch to the root user.
The steps to switch to the root user are as follows:
Set the root password:
$ sudo passwd root
Enter the current user password, e.g., kickpi.
Then enter the new root password (the input will not be displayed).
Confirm the password again.
If you see the message passwd: password updated successfully, it means the password has been set successfully.
Switch to the root user:
$ su
Enter the password you just set, and the current Terminal will enter the root user mode.
Enter the Linux Command-Line Interface
Ubuntu System
Turning off the Ubuntu graphical desktop will make the system enter the Linux command-line interface. The following describes how to turn the Ubuntu graphical desktop on and off.
Temporarily turn off the desktop:
$ sudo systemctl stop slim.service
Temporarily turn on the desktop:
$ sudo systemctl start slim.service
Permanently disable the desktop:
$ sudo systemctl disable slim.service
Permanently enable the desktop:
$ sudo systemctl enable slim.service
If the GUI desktop freezes, you can use the keyboard to enter the command-line interface:
To enter the command-line interface, press the shortcut keys CTRL + ALT + F3.
To return to the GUI desktop, press the shortcut key ALT + F2.
Debian System
Disable the desktop environment and start in pure command-line mode
Modify the default runlevel:
$ systemctl set-default multi-user.target
Check the current system runlevel:
$ systemctl get-default
Restart the system:
$ reboot
Enable the desktop environment
Modify the default runlevel:
$ systemctl set-default graphical.target
Restart the system:
$ reboot
Last updated
The website is . You can directly search for the name of the required dependency package.
