Networking and security

Reliable connectivity and controlled access boundaries underpin secure edge device operation. JelinaOS provides comprehensive network configuration and multilayer security mechanisms.

Network connectivity

Wired networking

Connect an Ethernet cable to obtain an address automatically through DHCP, without additional configuration. For a fixed address, configure a static address for the interface in system network settings.

Wireless networking

Use the system network management tool to connect to Wi-Fi:

nmcli device wifi connect "SSID" password "password"

View network status

ip addr          # View interfaces and addresses
nmcli device     # View network device status

Network addresses reported by the device agent are visible in the cloud device dashboard.

Firewall

The system provides firewall capabilities through iptables for basic device protection:

# View current rules
iptables -L -n

# Allow a specified port, for example TCP 8080
iptables -A INPUT -p tcp --dport 8080 -j ACCEPT

Change firewall rules carefully to avoid losing remote connectivity.

Secure channels

Devices communicate with the cloud through encrypted channels. Before using remote maintenance, confirm that the device is activated and Online:

Remote SSH, remote desktop, and service proxying are available by default.
In production mode, devices accept access only through the cloud. Direct access is unavailable even from the same LAN.
To allow direct LAN access, open the required ports in the release configuration.

Access security

Measure	Description
Change default passwords	Factory credentials are only for initial access and must be changed before normal use
Minimize exposed ports	Open only ports required by the application
Production mode	Devices communicate with the cloud only through secure channels
Access keys	Local device interfaces use key authentication; keys can be regenerated at any time

Network troubleshooting

Symptom	Troubleshooting steps
Device offline	Check connectivity → confirm the device agent is running → inspect agent logs
Remote access unavailable	Confirm the device is activated and Online → check permissions and target service configuration
Application cannot access the network	Check firewall rules → check container port mappings
DNS resolution fails	Check DNS configuration with resolvectl status
Time is not synchronized	Check system time and time synchronization service status with timedatectl
Investigating exposed ports	Inspect listening ports with ss -lntup and check firewall rules

Security notes

Remote container management ports, such as Docker port 2375, are closed by default. If needed, enable them only on trusted networks with access controls.
Before changing firewall rules, ensure an alternative access method is available to avoid losing the remote connection.

Security and data isolation — Complete security design
Fleet management and remote maintenance — Cloud remote maintenance capabilities