Is it possible to set a fixed IP in the Flukso v2b?
With DHCP the meter can get a different ip everytime, making automated local reading very hard. As this box is linux-based(?) one should be able to disable DHCP and set a fixed IP. Anyone know how to do this?
Using putty ssh:
ssh root@192.168.255.1
...
and then what?
Thx-a-1.000.000
How the flukso do have a different IP ? Did you cut the power of it every night or so ?
I put a fixed IP only on the router/modem.
I have multiple fixed ip's in my network. Any device that can or is supposed to be called on ip number SHOULD have a fixed ip in my opinion. DHCP is for workstations and mobile devices. Anything resembling a server, printer or router is supposed to have a fixed ip. I work in IT and that is very customary.
So the question remains: how can I put a fixed ip in the flukso?
Why are you not allocating a fixed IP address in the DHCP table of your router for the MAC address of the Flukso
Like i did ;-)
I did the above in my router. Fixed it nicely :)
As did I but I would have liked to put the device outside of the DHCP range.
What linux derivative is the flukso based on?
I was also surprised that you can't set a static IP for the flukso. Thats a basic thing that every device can.
I also like to set a static IP for the flukso like I do with every device. A Fixed IP is always working.
Using fixed IP is so past-century and even dangerous. Don't do it!
As suggested above, used MAC-to-IP binding of your router/DHCP server, if it can't do that or if it insists that this 'fixed' address needs to be in the DHCP pool range, consider getting a proper router.
Yeah right!
That's probably why almost every server on the planet has a static IP.
DHCP is shit!
Seriously doubt it!
Anyway, we're talking LAN here, not WAN. The risk of assigning double or incorrect IP addresses is simply to high, DHCP + reservation is a simple solution that gives you administration in one place only.
Using a fixed IP is not so "past century" and it definitely is not even remotely dangerous. But in the same, DHCP is not shit either!
Both fixed IP and DHCP have a time and a place, depending on the scenario. Both fixed IP and DHCP can cause issues if not correctly setup and/or maintained.
Whilst I agree that the flukso should have the ability to set a static IP. Since it doesn't have the ability at present, all we can do is make the best of the situation. This leaves us with DHCP as the only option.
A DHCP pool and an IP reservation based on the flukso's mac address, will ensure it keeps the same IP each time.
For what it's worth, at home I am running a combination of DHCP + DHCP with reservations and static IP addresses for devices on my network.
For example, my flukso, WD live boxes and networked bluray player are DHCP with a static reservation in the DHCP pool. Other devices, such as mobile phones, laptops etc are DHCP and lastly my synology box, microwave link and weather station are on static IP addresses - Like I said, theres a time and a place for either depending on the scenario.
Cheers
Adam
Adam
Great summation and example of how they can all work together
I understand technology but at times have trouble choosing and setting up which is best for situation
Glenn
There seem to be 2 sides on this topic.
@petur: I disagree with you on every argument and I have managed small to very large networks for over 20 years PROFESSIONALLY. That makes me an expert on this topic. There are good arguments for using DHCP but ONLY when you also have a DNS server, which is hardly EVER the case in small networks like home and home-office setups. For DNS you need a domain, hence a domain controller. You know any regular home users with a domain controller? I don't. Also static DHCP is fairly new for home routers and the flukso is INTENDED for home use!
Btw: Are the developpers reading this forum?
@GH
For my better understanding a couple of questions and yes I understand DNS environments in businesses
Why is there any need or advantage to have a fixed IP address for a home environment when a "reserved" address with DHCP is available ?
For example I have a CISCO E4200 router at home which I have setup with a DHCP range table (say 50 to 75) for all the mobile devices in the house
Then I "reserve" an address outside this range for Flukso, Printer, etc that I want on a "fixed" address
Is that not achieving the same thing as a fixed IP ?
Glenn
As I said earlier: Many home routers do not support static DHCP (mine does fortunately). I cannot buy another router because this one is supplied by my internet provider and is also used for telephony. Static DHCP is a work-around, but not a solution to the q. True one can set a DHCP range from e.g. 101 to 165 and then set the Fixed IP to 150 and above. That would be an acceptable workaround.
Strange how this topic turned into a discussion about the question itself.
I give up, famous last words...
Why do you bring DNS into the discussion (I stopped reading after that as that was where you whole case fell over).
And I consider my home network to be about the size of a small company, and I've been managing networks since early 1990, so when I say that it is last century I actually mean it.
I only use static IP for the core network equipment (router, (managed) switches and APs), servers and some computers that need it get a fixed IP from the DHCP in a specific range, and the rest can swim in the pool.
While I actually know several IP addresses of computer equipment on my network, I can just as well use flukso.lan - and I do not even run a DNS server.
And for all I know and see these days, even the cheapest and crapiest routers on the market offer DHCP reservation, that argument is also last-century.
Last point: I do not trust my ISP, neither should you. So that router of them (that they manage from the WAN side, probably with crappy security backdoors to make their life easy) will not be their door to my network, I'll have my own router and firewall inbetween, thank you. Another argument to drop.
And now I'll stop this pointless discussion.
It looks like we can just edit /overlay/etc/config/network
:D
This is what I have for my wan connection in /overlay/etc/config/network
Ugh. Can't even edit a post here...
Again then.
This is what I have for my wan connection in /overlay/etc/config/network
Make sure you know what you are doing because you can loose the connection to your device!
More info: http://wiki.openwrt.org/doc/uci/network