Static IP Settings
Starting from FlyOS-Fast v1.3.9, the wired Ethernet port supports automatic recognition of direct connections to a PC or router. If the device's Ethernet port is directly connected to a PC, you can access the device via 10.10.10.1 or local.klipper.cn after waiting approximately 15 seconds; manual static IP configuration for direct connection scenarios is generally no longer required.
Purpose and Advantages of Static IP
Static IP configuration ensures the device has a fixed address on the network, providing stable and reliable network connectivity for various application scenarios.
Main Application Scenarios
-
Ensure Stable Device Accessibility
- The device maintains the same IP address at all times, facilitating remote access and control
- Suitable for scenarios requiring fixed addresses, such as web servers, MQTT communication, and PLC control
-
Simplify Network Management
- Devices like cameras, sensors, and controllers require fixed IPs on local area networks or industrial networks
- Facilitates stable connections for other systems and services
-
Adapt to Special Network Environments
- Static IPs are mandatory in environments without DHCP services (e.g., industrial control, edge computing)
- Avoids reliance on dynamic address assignment
-
Enhance Development and Debugging Efficiency
- Fixed IPs facilitate rapid device location and connection
- Simplifies repetitive testing processes
-
Support Device Discovery Mechanisms
- When accessing devices via preset IP ranges, static IPs ensure devices respond as expected
Comparison of Static IP Advantages
| Advantage | Description |
|---|---|
| Stable and Reliable | The IP address remains fixed, ensuring stable communication for long-running devices |
| Friendly for Headless Environments | Suitable for use in environments without a graphical interface, such as embedded devices |
| Convenient Remote Maintenance | More efficient when connecting via SSH, Web, API, etc. |
| Closed Network Adaptation | Static IPs are necessary in industrial networks or private networks without DHCP |
| Automation Support | Deployment, monitoring, and update scripts rely on IP consistency for proper operation |
System-Side Configuration
- Avoid using IP addresses near boundary values such as
0,1,254, or255 - Using an address like
192.168.1.254might be preempted by other applications, leading to unstable connections - It is recommended to use IP addresses in the middle range, such as
192.168.1.100-192.168.1.200
Configuration Steps
-
Connect to the System Terminal
- Use SSH to connect to the device system
-
Check the Network Interface
- Execute command:
ip link show - Note the network interface name, e.g.,
eth0,end0
Loading... - Execute command:
-
Edit the Network Configuration File
- Execute command:
nano /etc/systemd/network/end0.network - Note: Replace
end0in the filename with your actual network interface name
Loading... - Execute command:
-
Configure Static IP Parameters
- Modify the file content as follows (adjust according to your actual network environment):
[Match]# Match the network interface name, modify as neededName=end0[Network]# Set the static IP address and subnet mask# /24 indicates a subnet mask of 255.255.255.0Address=192.168.1.100/24# Set the default gateway addressGateway=192.168.1.1# Set the DNS serversDNS=8.8.8.8DNS=114.114.114.114Loading... -
Save and Apply the Configuration
- Press
Ctrl + Sto save the file - Press
Ctrl + Xto exit the editor - Execute command to restart the network service:
systemctl restart systemd-networkd
- Press
-
Verify the Configuration Result
- Execute command:
ip a - Confirm that the displayed IP address matches the configured one
Loading... - Execute command:
PC-Side Configuration
To ensure the PC can communicate properly with the device configured with a static IP, corresponding network configuration is required on the PC side.
Network Parameter Settings
| Parameter | Configuration Requirement | Description |
|---|---|---|
| Host IP | 192.168.1.xxx | Must be on the same subnet as the device IP |
| Gateway | 192.168.1.1 | Must match the gateway configured on the device |
| Subnet Mask | 255.255.255.0 | Corresponds to the /24 configuration on the device IP |
| DNS Server | 8.8.8.8, 114.114.114.114 | Use common public DNS services |
Configuration Methods
Windows System
- Open "Network and Sharing Center"
- Click "Change adapter settings"
- Right-click the current network connection, select "Properties"
- Double-click "Internet Protocol Version 4 (TCP/IPv4)"
- Select "Use the following IP address" and fill in the corresponding parameters
macOS System
- Open "System Preferences" → "Network"
- Select the current network connection
- Click "Advanced" → "TCP/IP"
- Configure "IPv4" to "Manually"
- Enter the corresponding IP address, Subnet Mask, and Router address
Connectivity Test
After configuration, it is recommended to perform a connectivity test:
# Execute the ping command on the PC to test connectivity
ping 192.168.1.100
# If you receive replies, the network configuration is successful
If the device cannot be pinged, please check:
- Whether the network cable connection is normal
- Whether the firewall settings are blocking communication
- Whether the IP addresses are on the same subnet
- Whether the subnet mask and gateway configurations are correct