Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

uplink-notunnel: two dhcp-requests for a node #624

Open
SvenRoederer opened this issue Nov 19, 2018 · 1 comment
Open

uplink-notunnel: two dhcp-requests for a node #624

SvenRoederer opened this issue Nov 19, 2018 · 1 comment

Comments

@SvenRoederer
Copy link
Contributor

when using the notunnel uplink our node requests 2 ipadresses via dhcp. one for interfave WAN, another for interface ffuplink.
On both requests the same client-id is used (the hostname), which causes error-messages on the uplink-dhcp server.

We can change the default clientid via uci. As the hostname is not known when creating the ffuplink-interface via uci-defaults, I suggest to use a random name, e.g. freifunk-uplink-xxxx

@pmelange
Copy link
Contributor

I think that is a great idea. And once the wizard has been ran, it can be set to ffreifunk-uplink-$HOSTNAME.

I think using a shorter prefix to the hostname (like ffuplink) would be better. Many of the web interfaces from the telecom will cut off the name after X characters.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants