Choose style:

Author Topic: DCHP static leases in Amond+  (Read 14110 times)

0 Members and 1 Guest are viewing this topic.

Offline Shazster

  • Newbie
  • ****
  • Posts: 173
  • Thanks: 0
  • Registered : 29/11/2015
    YearsYearsYearsYearsYearsYearsYearsYearsYearsYears
Re: DCHP static leases in Amond+
« Reply #15 on: January 10, 2016, 10:27:26 am »
OK since I am seeing little response, I will have to assume 20 static leases is the limit I am stuck with. So be it. My issue really is less one of Static leases, and more one of host name assignation. It just happens that the easiest/simplest way to assign a hostname is at the same time as assigning a static lease.
I suppose that not everything I put on the network requires a fixed IP, but I would like it to have a defined hostname. "android-dghfdfhjblahblahblah" tells me nothing in a home with 3 current tablets, 2 old ones used as info panels and light controls, and a couple of smartphones. My naming scheme goes like this:
TBLT_(tablet name) for android devices
HOME_(name) fixed aplliances or home devices. Hue hub, satellite pvr, smart TV, bluray, etc. etc.
DESK_(name) desktop pcs
LPTP_(name) laptops netbooks
SRVR_(name) NAS or PC based file server
PRNT_(name) printers
At a glance I can see who is connected and what their function is.

So, other than at at the static lease reservation screen, is there a spot where I can assign hostnames...with the same simplicity?

Offline SecureComp

  • Backer
  • *
  • Posts: 541
  • Thanks: 1
  • Registered : 05/08/2014
    YearsYearsYearsYearsYearsYearsYearsYearsYearsYearsYears
Re: DCHP static leases in Amond+
« Reply #16 on: January 10, 2016, 12:01:28 pm »
/etc/hosts

static assign client
assign hostname to ip in /etc/hosts
Kickstarter Backer
Securifi Wiki Editor and Beta Tester, Not a Securifi employee
Almond+, many sensors, IOS App, Android Apps and Widgets

Offline Shazster

  • Newbie
  • ****
  • Posts: 173
  • Thanks: 0
  • Registered : 29/11/2015
    YearsYearsYearsYearsYearsYearsYearsYearsYearsYears
Re: DCHP static leases in Amond+
« Reply #17 on: January 10, 2016, 05:13:28 pm »
Hostname is assigned to an IP, not linked by MAC address?
And how does one access the etc/hosts file? I assume not through either the Almond interface or OpenWRT.

Offline SecureComp

  • Backer
  • *
  • Posts: 541
  • Thanks: 1
  • Registered : 05/08/2014
    YearsYearsYearsYearsYearsYearsYearsYearsYearsYearsYears
Re: DCHP static leases in Amond+
« Reply #18 on: January 10, 2016, 06:10:23 pm »
Hostname is assigned to an IP, not linked by MAC address?
And how does one access the etc/hosts file? I assume not through either the Almond interface or OpenWRT.

OK, so there are two answers here; the official - it's not supported and the unofficial - this is how you get it done if you really want it

Hostname is not assigned by MAC address, often device type and mac address are used as part of a hostname for users but a hostname can actually be any name. (within reason, special character issues and all of that)

Hostnames are tied to IP addresses. IP addresses, in the case of DHCP are handed out and organized by MAC address and a hostname is automatically assigned, often incorporating a portion of the MAC address and sometimes a little info about the device type.

Stepping outside of the DHCP world and into UNIX in general, hostnames are assigned in the /etc/hosts file and are tied to an IP address.

In order to make changes to an /etc/hosts file, or to even know what an /etc/hosts file is, requires some basic understanding of UNIX, in this case a flavor of LINUX that is used as the O/S for the Almond devices.

You can access the LINUX based OS of the Almond device using SSH. (Secure SHell access) Once in, you can edit files. Again, don't go changing files if you don't know what you are doing and have no understanding of UNIX or say VI.

As it happens, with the A+, yes you can use OpenWRT to access the Network/Hostnames page and make entries for hostnames/IP's.

So, statically assign the IP, DNS and routing info to the client and then use OpenWRT to assign the hostnames to the IP's.
Let us know how it works for you. Haven't bothered to do it myself yet, no real need...yet.
Kickstarter Backer
Securifi Wiki Editor and Beta Tester, Not a Securifi employee
Almond+, many sensors, IOS App, Android Apps and Widgets

Offline Shazster

  • Newbie
  • ****
  • Posts: 173
  • Thanks: 0
  • Registered : 29/11/2015
    YearsYearsYearsYearsYearsYearsYearsYearsYearsYears
Re: DCHP static leases in Amond+
« Reply #19 on: January 11, 2016, 12:27:35 am »
OK. That totally doesn't sound like I could end up bricking $300 bucks worth of gear.

Let me guess, I need to open a terminal (I have a Linux netbook kicking around)
Whatever SSH command is, IP + port number + root login & pw  something along those lines?

Yeah, before I go poking in the code that runs this thing, I think maybe Securifi needs to work on their interface to make it a little more routers-for-humans-sy. It certainly is not getting done before a lot more research, but at least I have a starting point. Thanks.


Offline SecureComp

  • Backer
  • *
  • Posts: 541
  • Thanks: 1
  • Registered : 05/08/2014
    YearsYearsYearsYearsYearsYearsYearsYearsYearsYearsYears
Re: DCHP static leases in Amond+
« Reply #20 on: January 11, 2016, 01:33:06 am »
You are asking how to exceed the current limits. I am providing a work around.

Editing a hosts file is very basic stuff, basically like typing  the following into a text file:

192.168.10.51 laptop
192.168.10.52 iPhone
192.168.10.53 tablet

Knowing about a host file in the first place, knowing how to "get into" a LINUX box or the Almond, assigning a static IP to a Client device, these things take some basic understanding of networking. No black magic, just the basics.

Using OpenWRT makes it that much easier, just go to the section that allows you to edit the hosts file. Google it or check youtube, plenty of videos.

Always make a backup of your configuration before beginning work. (east to do from the web user interface)

But for sure, if you are not comfortable, then don't do it and deal with static IP limit, or don't, up to you.

And yes, SSH is used like this;
ssh -l root 10.10.10.254 ( the IP of your router, whatever it is)

And I'm sure Securifi can make the changes but there are other priorities. DHCP works well and you can modify the hostnames in the Device section. Locking in an IP number, why bother would be my question. Especially if you have already assigned the hostname that is descriptive. But it's your system, whatever works for you.
« Last Edit: January 11, 2016, 01:37:52 am by SecureComp »
Kickstarter Backer
Securifi Wiki Editor and Beta Tester, Not a Securifi employee
Almond+, many sensors, IOS App, Android Apps and Widgets

 

Page created in 0.034 seconds with 18 queries.