On 23 September 2011 13:11, Paul Alfille <[email protected]> wrote: > On Fri, Sep 23, 2011 at 3:54 AM, Colin Law <[email protected]> wrote: > >> I am using Ruby on the plug so I think owshell is what I want. There >> is a ruby gem 'one-wire' which looks like it should do what I want. > > You don't even need owshell except for testing. The Ruby gem should > talk directly to owserver.
Looking at the code I think you are right, so as you say I should not need anything else on the Sheeva. > >> >> I can't seem to get into owserver on the wrt54g remotely, I suspect I >> have to open the owserver port, which means messing with iptables I >> think :( No doubt trivial once you know how. Google here I come. > > It sounds like you are on the "WAN" side of the router. Access from > the internal side (LAN and WIFI) is usually open for most ports. As the router is configured as a *client* on the wifi (with my modem router as the master) the wifi is the WAN port on the router even though it is actually on my LAN. The ethernet ports on the router (which I am not using) are its LAN which would be a different subnet to my LAN. I have opened port 4304 and can now access owserver from my PC so it's all systems go. Many thanks Colin -- gplus.to/clanlaw ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2dcopy2 _______________________________________________ Owfs-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/owfs-developers
