I have a router type device that has an ethernet port, a wireless interface and runs the OpenWRT (a linux variant). We do not use the device as a router. It is used as a network client that displays temperature data. Currently, it is difficult for non-IT people to setup. For an IT person, this is easy:
1. Connect power to the router
2. Connect a computer to the router via ethernet cable
3. The router assigns the computer an IP address of 10.1.1.2. So, the user just needs to go to 10.1.1.1 in a web browser to access the web admin built into the router.
4. Once there, the user can change the ethernet settings or setup the wireless connection (as a client on the network NOT a router).
Customers typically want to set it up in one of the following ways:
1. Connect it as a client on a wireless network so I can access the temperature readings over the network via the web interface.
2. Connect it as a client on the wired network so I can access the temperature readings over the network via the web interface.
Sometimes the user wants to use DHCP or Static IPs on the interface.
However, I've noticed that many home wireless routers are now super easy to setup. I'm wonder what's the best way to change my device to allow almost anyone to set it up. For instance, I unpacked a D-link router and connected the wires. The next step was to run a software CD with a wizard that setup the unit. Is this the best way to go? Can you create something like this for me that will run on a PC or Mac?
Thanks for reviewing my project,
PS - the web ui is written in Ruby, but with this thing running Linux, we can pretty much use whatever packages you want to get this solution implemented.
1) All deliverables will be considered "work made for hire" under U.S. Copyright law. Employer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the employer on the site per the worker's Worker Legal Agreement).
2) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done.
3) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables):
a) For web sites or other server-side deliverables intended to only ever exist in one place in the Employer's environment--Deliverables must be installed by the Worker in ready-to-run condition in the Employer's environment.
b) For all others including desktop software or software the employer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this project.