Fixing Networking and DHCP Issues on Haiku
No network connectivity, or an interface that won't get an IP address — here's how to work through Haiku's networking stack from hardware detection through DHCP.
Networking problems on Haiku generally trace to one of a few specific layers — the network hardware not being detected, the interface not being configured, or DHCP itself failing — this works through each in order.
Step 1: confirm the network interface is detected at all
Network preferences (or from Terminal): ifconfigIf no network interface beyond loopback appears at all, this points at a driver-support gap for your specific network hardware — a genuine possibility given Haiku’s smaller driver ecosystem relative to Linux or the BSDs, worth checking against known hardware compatibility before assuming a configuration problem.
Step 2: check the interface’s current configuration
ifconfig <interface-name>Confirm whether the interface has any IP address assigned at all, versus being correctly detected but simply unconfigured.
Step 3: try requesting a DHCP lease explicitly
Network preferences → select the interface →
set to "DHCP" if not already configured that wayMost networks provide addressing via DHCP automatically — confirm the interface is actually configured to request one, rather than expecting a static address that was never set.
Step 4: check whether DHCP is failing specifically, versus the interface being down entirely
ifconfig <interface-name> | grep -i "up\|running"An interface reported as down at the hardware/link level won’t succeed at DHCP regardless of configuration — confirm basic link state (cable connected, Wi-Fi associated) before troubleshooting DHCP specifically.
Step 5: check for a Wi-Fi-specific association problem, if applicable
Network preferences → Wi-Fi networks →
confirm the correct network is selected and the
password/security type matchesWi-Fi introduces an additional layer (network association and authentication) before DHCP even begins — a failure here looks similar to a DHCP failure but has a completely different cause and fix.
Step 6: try manually configuring a static IP to isolate the problem
Network preferences → set a static IP matching your
network's actual subnet (e.g. 192.168.1.50/24 with
gateway 192.168.1.1)If a manually-configured static address works while DHCP does not, the problem is specifically with the DHCP negotiation (or the DHCP server itself) rather than the network interface or basic connectivity generally.
Step 7: check for a firewall or router-side DHCP issue, if static addressing works
Confirm the router's DHCP server is actually running
and has available addresses in its pool — a saturated
or misconfigured DHCP server affects every client on
the network, not just Haiku specifically.Step 8: restart networking services without a full reboot
# specific service restart commands vary by Haiku version;
# check current documentation for the equivalent of
# restarting net_serverHaiku’s networking stack runs as ordinary user-space services rather than requiring a full system restart to reset — worth trying before a full reboot if a configuration change doesn’t seem to take effect.
Why isolating hardware detection from DHCP failure matters most
A missing driver and a DHCP negotiation failure look identical from a “no internet” perspective but have completely different fixes — one requires hardware compatibility research (and possibly isn’t fixable without upstream driver work), the other is usually a quick configuration check. Confirming the interface is detected and shows as up at the link layer, before troubleshooting DHCP specifically, is what prevents chasing a configuration fix for what’s actually an unsupported hardware problem.