Feature #325
DHCP Router control using HTTPS/SSL instead of plain http
0%
Description
I'm testing and trying to get hda-platform to control my Linksys WRTG54 and in attempt to enable DHCP on the router via the platform, results in error. Here's a snippet from /var/hda/platform/html/log/production.log:
Processing NetworkController#toggle_setting (for 192.168.0.2 at 2009-10-03 11:13:45) [POST]
Session ID: dc6606c6517b79a8578bf3482093b107
Parameters: {"kind"=>"dhcp_in_router", "action"=>"toggle_setting", "id"=>"111", "controller"=>"network"}
Completed in 0.14378 (6 reqs/sec) | Rendering: 0.05767 (40%) | DB: 0.01488 (10%) | 500 Internal Server Error [http://hda/network/toggle_setting/111?kind=dhcp_in_router]
I had to hack the routers/linksys.rb file because my router has been configured to use https versus http and I understand hda-platform linksys.rb was configured to use http. Could this be why I'm getting this HTTP 500 error caused by the network/toggle_setting/111?kind=dhcp_in_router action?
History
#1 Updated by cpg over 11 years ago
actually, we could even try and detect - if port 443 is open and working, try that first!
no need to user interface!
yeah, a feature :)
#2 Updated by cpg over 11 years ago
- Tracker changed from Bug to Feature
#3 Updated by cpg over 11 years ago
- Subject changed from DHCP Router control to DHCP Router control using HTTPS/SSL instead of plain http
Also available in: Atom