-
Notifications
You must be signed in to change notification settings - Fork 11
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
Configure the DHCP server to hand out unchanging IP addresses to specific MAC addresses #1279
Comments
Yes we can issue static IP's on request. We also maintain a list that is managed by @DoESLiverpool/networking who can see this list however it is kept private right now as it doesn't seem appropriate to publically list devices with their IP's on the internet |
Yes, this is very much a thing we do, and have done on request for MQTT.local, for example. Just let me know what devices you want making static and I can do that.
… On 14 Oct 2019, at 12:12, Jake Oliver ***@***.***> wrote:
Yes we can issue static IP's on request.
We also maintain a list that is managed by @DoESLiverpool/networking <https://github.com/orgs/DoESLiverpool/teams/networking> who can see this list however it is kept private right now as it doesn't seem appropriate to publically list devices with their IP's on the internet
—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub <#1279?email_source=notifications&email_token=AAAGU23G3DUV6RBVSTQLGO3QORHZRA5CNFSM4JANVB22YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBEGYFI#issuecomment-541617173>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAGU25VIWYIRZZP54WNIW3QORHZRANCNFSM4JANVB2Q>.
|
Just realised. This is public! Shall forward the list directly :-D |
It'd be nice if the Pi at mqtt.local was actually set to use its allocated IP address too :-) It's been sat on 10.0.30.194 for a while now... |
@ajlennon The issue from #1210 regarding mDNS I think is still that the Ubiquiti feature John found that essentially caches the last DNS result from a given piece of hardware.
The reason I think this is because even if two devices are running mDNS, they will not discover eachother if their .localdomain (dhcp hostname discovery) has been preferred by this ubiquiti feature. So, it's a race condition, wherein regular DNS is sometimes being preferred, making things subservient to the router's domain (.localdomain or otherwise) or the device's configuration in /etc/hosts. Also an issue is that sometimes the previous hostnames used on a given dhcp lease. |
So if I have two Pi's running avahi-daemon, it will be up in the air whether their hostname resolves .localdomain or .local because this feature is preferring .localdomain some of the time. I don't know if this is simply when the router is discovering it, or how the feature works, but this is something I've observed. |
These have now been configured, I'm afraid I've changed the IP addresses for the 3D printers but they should be easier to remember/transcribe now. |
(I haven't touched the 3D printers themselves though so I believe they're still operating on their old IP addresses for now) |
@MatthewCroughan given these IP addresses won't change again would it be possible for you to update those lovely little stickers you did? If you do make the change could you make the text bigger for #grumpyoldengineers ? |
@ajlennon really we need a better, larger display for them. Maybe made out of laser cut acrylic? All in all we need a bigger label, and we're limited in that regard. I tried to put as much info on them as possible, like cura instructions. Does anyone have any suggestions for making a bigger label? |
There's been a lot of discussion recently around m-DNS, ZeroConf, Bonhour or whatever we want to call it. Whatever the underlying issues they seem to be ongoing.
As a fall-back (e.g. for the Creality Printers) we've been printing the IP address alongside the m-DNS domain name.
Unfortunately these IP addresses keep changing.
There should be a feature in the DHCP server I would think that allows us to create a list of DHCP assigned IP addresses which don't change, and are handed out to specific devices based on the MAC address they report when obtaining an IP address via DHCP.
Assuming we don't already do this and I haven't missed it, can we maintain a list of such devices and their assigned IPs somewhere on the Wiki?
The text was updated successfully, but these errors were encountered: