Connecting dev-board to internet via Ethernet cable connection to host pc

Connect your development board to the internet by configuring a static IP on your host PC, enabling Internet Connection Sharing (ICS) or NAT routing, and setting the dev-board’s gateway to the host’s local IP. This creates a direct routed path through the host’s active network interface, allowing the embedded device to access external services without requiring its own DHCP client or physical router connection.

Understanding the Network Topology

When you connect a development board directly to a host PC via an Ethernet cable, they form an isolated peer-to-peer link. By default, this link has no route to the outside world because neither device knows how to reach networks beyond their immediate subnet. The goal is to transform the host PC into a gateway that forwards traffic from the dev-board to the internet. This setup is particularly useful when working in environments where routers are unavailable, restricted, or when you need a secure, isolated debugging environment. The core mechanism relies on IP forwarding. Your host PC must accept packets arriving on the Ethernet interface connected to the dev-board and forward them out through its primary internet-facing interface (Wi-Fi or another Ethernet port). Simultaneously, the dev-board must be configured with a static IP address on the same subnet as the host’s side of the connection, and it must designate the host PC’s IP as its default gateway. Without these two components working in tandem, packets will either be dropped locally or sent into a black hole.

Configuring the Host PC

The configuration steps vary slightly depending on your operating system, but the logical requirements remain consistent. On Linux systems, you typically enable IP forwarding by modifying the sysctl settings. You can achieve this temporarily by running sudo sysctl -w net.ipv4.ip_forward=1. To make this persistent across reboots, add net.ipv4.ip_forward=1 to /etc/sysctl.conf. Additionally, you may need to configure iptables rules to perform Network Address Translation (NAT), which masquerades the dev-board’s traffic so it appears to come from the host PC. A common rule for this is sudo iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE, assuming eth0 is your internet-connected interface. On Windows, the process is often more streamlined through the graphical interface. Navigate to the Network Connections panel, right-click the adapter that provides your internet access, and select Properties. Go to the Sharing tab and check the box for "Allow other network users to connect through this computer’s Internet connection." Then, select the specific Ethernet adapter connected to the dev-board from the dropdown menu. Windows will automatically assign a static IP (usually 192.168.137.1) to that adapter and handle the NAT routing behind the scenes. macOS users can use the Sharing preferences pane. Select "Internet Sharing" from the sidebar, choose the source of your internet connection (e.g., Wi-Fi), and share it with computers using Ethernet. Check the box for the Ethernet port connected to the dev-board. macOS will automatically configure the necessary DHCP and NAT services for the connected device. If you have previously flashed incorrect network masks on similar devices, such as in the case discussed in Flashed a wrong network mask in a PoE device, ensure your subnet masks align correctly between the host and the dev-board to prevent routing ambiguities.

Setting Up the Development Board

Once the host is ready, the dev-board requires manual network configuration. Most development boards do not have built-in DHCP clients enabled by default for security or simplicity reasons in headless setups. You must log in to the board’s console, either via UART serial connection or SSH if already reachable on a local LAN, and edit the network configuration files. For Linux-based boards, this usually involves editing /etc/network/interfaces or /etc/netplan/*.yaml. You need to assign a static IP address that falls within the same subnet as the host’s side of the Ethernet link. For example, if the host is 192.168.137.1, the dev-board might be 192.168.137.2. Crucially, you must set the default gateway to the host’s IP address (192.168.137.1) and specify a DNS server, such as 8.8.8.8 or your local router’s IP. After applying the changes, restart the network service. Verify connectivity by pinging the host’s IP from the dev-board, then pinging an external IP like 8.8.8.8. If the ping to 8.8.8.8 succeeds but domain names fail, your DNS configuration is incorrect. If the ping to the host fails, check your firewall settings on the host to ensure ICMP traffic is allowed from the dev-board’s subnet.

Troubleshooting Connectivity Issues

Even with correct configurations, several common pitfalls can disrupt the connection. First, verify that the Ethernet cable is functional and supports auto-negotiation. While most modern ports handle crossover cables automatically, older hardware might require a specific cable type. Second, check for IP conflicts. Ensure no other device on the host’s local network is trying to use the static IP assigned to the dev-board. Firewalls on the host PC are another frequent culprit. Even with ICS enabled, strict firewall rules might block forwarded traffic. Temporarily disabling the firewall can help isolate whether it is the cause. If you are experiencing bandwidth limitations or instability, consider if your current setup resembles scenarios where multiple NICs are used, as discussed in Can I Use Two NICs to Get Double the Bandwidth to a Switch?, though in this simple passthrough scenario, single-link speed is determined by the slowest link in the chain. Finally, ensure that the dev-board’s kernel supports the necessary networking modules. Some minimal embedded builds may lack TCP/IP stack optimizations or required drivers for the specific Ethernet controller, leading to intermittent drops. Checking kernel logs via dmesg can reveal driver errors or link state changes that indicate hardware-level issues rather than configuration errors.

Frequently Asked Questions

Why can't my dev-board get an IP address automatically?

Many development boards disable DHCP clients by default to prevent accidental connections to untrusted networks. You must manually configure a static IP address and gateway in the board’s network configuration files to establish a fixed route through your host PC.

How do I know if IP forwarding is enabled on my host?

You can check the status by running cat /proc/sys/net/ipv4/ip_forward on Linux; a value of 1 indicates it is enabled. On Windows, look at the properties of your network adapters under the Sharing tab to see if Internet Connection Sharing is active.

What happens if I ping an external IP but not a domain name?

This indicates that basic routing and NAT are working, but DNS resolution is failing. Ensure you have specified valid DNS servers, such as Google's 8.8.8.8 or Cloudflare's 1.1.1.1, in your dev-board’s network configuration file.

Can I use this setup for high-speed data transfer?

While suitable for general development, this single-hop NAT setup may introduce overhead compared to direct switch connections. If you require maximum throughput, consider bonding adapters or using dedicated switches as described in How to Bond Two 2.5 Gbps Realtek R8152 Ethernet Adapters via LACP in Linux for a Network Speed Boost.

Is this method secure for production environments?

No, this setup is intended for development and testing. It lacks the isolation, authentication, and monitoring features of a proper router or firewall. For production, always use dedicated network infrastructure to manage traffic and security policies.