-
Notifications
You must be signed in to change notification settings - Fork 207
Description
Greetings!
I noticed an odd bug that can occur to clients that are set to grab their IP via DHCP. At times, if you were to disconnect and reconnect, the tap adapter gets the static IP of 9.0.0.1 instead of waiting for a DHCP server to assign its address.
The Host:
The host is running dnsmasq for the DHCP server, and it listens on the tap interface for incoming connections. FreeLAN is started by this command:
freelan --security.passphrase "my secret"
Clients:
Clients join using the following command:
freelan --security.passphrase "my secret" --fscp.contact [IP_ADDRESS]:12000 --tap_adapter.ipv4_dhcp 1 --tap_adapter.dhcp_proxy_enabled 0 --tap_adapter.metric 1
Works Most of the Time
When a client joins for the first time they can gather their IP, provided by the host's DHCP server, quite easily without issues.
How the bug occurs
However if the client were to then disconnect, and reconnect within the span of a few seconds, then FreeLAN defaults the client to the static 9.0.0.1 address. This of course causes issues as the host already has the address of 9.0.0.1
Anyone know if there is a way to fix this, or could it be fixed in a later update to FreeLAN?