I have all hubs that you can buy! Honey is my favorite and most stable one, the only issue is my fiber internet which is 1Gps up/down so I needed a serous Security appliance who can have that output with all security enabled functions. The only option in this case is a corporate grade router which donāt have DHCP with static lease I have workarounds with PiHole as a DHCP and DNS, but having a static up at honey will make my setup easy and less disruptive.
I have two 5512x in ha (older one) and one 5506 in my office. Those are TNGās. Grab any small router even small cisco isr router and voila you have dhcp reservation.
Like you said corporate or enterprise firewalls are not meant to be fully blown dhcp. On the other hand Homey simply doesnāt have static ip. I donāt think this will soon be on the priority.
I need static IP or at least, a way to assign a different gateway than the one that my DHCP-server gives. I have two gateways (2x isp:s) and want to force homey to connect to another gateway. I guess this isnt possible? I want all my clients to connect through the DHCP servers gateway but not homey because I want homey to connect to another ISP which is more stable and not used by others.
Should be possible with any good DHCP server (on Khggg Windows or probably most other OSās) wth a Reservation an specific options for that reservation.
Can imagine that that is not an option on many SOHO routers.
and yes, itās sound that you could not config homey with a static ip-adress. But maybe in the futore they will make this happens in a change. Till then you must work with it.
It is the same as to get SSH to the Homey. If you should have that then you go dive deeper into the OS (linux?) then maybe you can set it well. But also the SSH is on the wish list
So everybody needs to work with the workaround and have a DHCP server live in his network.
Of course they do.
That prevents the competition from snooping around, leaves hackers more in the dark as to where the the weaknesses are, prevents support calls because someone messed up their Homey etc.
Agreed, but when running such a setup with such demands you would also be using a real DHCP solution, preferably dedicated, redundant and fully featured. In such setup, the last thing you would do would be decentralising your configuration by manualy(!) configuring end devices.
(And why give homey a fixed address, Iād suppose you would also make sure to have a rock solid name resolution system, canāt imagine you want it for port forwarding)
maybe you can create a seperate vlan for homey and have your dhcp server assign a single adress to it.
if the dhcp range for the vlan is x.x.x.250 - x.x.x.251 and no other devices will connect to this vlan, homey will always get .250.
Yes, but homey development team didnāt reinvented the DHCP from scratch! they just implemented in the OS they are using underhood, so for some nonsense reason they decided to keep the STATIC ip and SSH disabled in their OS.