Sometimes, we need to configure devices like IP Cameras or Sensors that relies on Ethernet Protocol to communicate with the other Host devices to transmit data. Most of the time, these devices come with static IP Address from the manufacturer, and we just have to set our ethernet subnet to the device's subnet, then we ca easily communicate with the device from our computer using the ethernet port. Just a point to note, I'm a Windows go-to user. So, all my work here is based on windows.
So, I had access to a Runcam Wifi link 2. That is a FPV camera that can work both on Wireless 2.4 GHz Link and alternatively provide RTSP feed over ethernet. And if the camera is flashed with openIPC firmware, the camera requests IP Address to a DHCP server. But when you do not have a Router connected between the camera and our computer, you can't really configure the camera. But can you?
Yes, you absolutely can. When you’re in the field or at a workbench without a router, your computer needs to stop acting like a mere "client" and start acting like the "boss" of the network.
To bridge this gap, we use a DHCP Server. On Windows, the lightweight, gold-standard tool for this is Tftpd64. It’s a tiny, portable utility that turns your Ethernet port into a functional network hub.
Let's guide you through the steps now, following these, you can deploy a DHCP server from your LAN port.
Setting a Static IP on Your PC
Since there is no router to hand out addresses, you must first give your computer a fixed "home."
At windows, Go to Network Connections > Right-click your Ethernet adapter > Properties.
Now Select IPv4 and click Properties. Use a static address like 192.168.1.10 with a Subnet Mask of 255.255.255.0. Leave the Gateway blank.
Configure Tftpd64 as a DHCP Server
Once you launch Tftpd64, you'll see several tabs. We are interested in the DHCP Server tab.
IP pool start address: Set this to 192.168.1.11 (one digit up from your PC).
Size of pool: Set this to 5 or 10, you only need one for the camera.
Def. router (Gateway): Enter your PC’s IP: 192.168.1.10.
Mask: 255.255.255.0.
Server interface: Ensure the dropdown menu matches your Ethernet adapter’s static IP (192.168.1.10).
Once you launch Tftpd64, you'll see several tabs. We are interested in the DHCP Server tab.
IP pool start address: Set this to 192.168.1.11 (one digit up from your PC).
Size of pool: Set this to 5 or 10, you only need one for the camera.
Def. router (Gateway): Enter your PC’s IP: 192.168.1.10.
Mask: 255.255.255.0.
Server interface: Ensure the dropdown menu matches your Ethernet adapter’s static IP (192.168.1.10).
Power Up and Bind
Now, connect your Runcam to your PC via Ethernet and power it on. Within a few seconds, look at the DHCP Tab or the Log Viewer in Tftpd64. You will see a "Discovery" and "Request" message from the camera. Tftpd64 will assign it the first available IP (likely 192.168.1.11).
Access the Feed
Now that the Runcam has an IP address on your local subnet, you can reach its web interface or RTSP stream just as if it were plugged into a high-end router.
Pro Tip: If the camera doesn't show up, check your Windows Firewall. It often blocks Tftpd64 from seeing "unidentified" incoming requests on the Ethernet port. Temporarily disabling it or adding an exception usually clears the path.