Quote from: tolip_wen on September 14, 2015, 09:38:39 PM

Quote from: GenTarkin on September 14, 2015, 07:43:19 PM

Quote from: tolip_wen on September 14, 2015, 06:06:43 PM

Quote from: mindtrip on September 14, 2015, 05:35:37 PM

Quote from: GenTarkin on September 14, 2015, 04:16:44 PM

Quote from: mindtrip on September 14, 2015, 02:56:14 AM

not at all Grin

Thank You!

So, theres 1 caveat to allowing access to bfgminer from other network devices. This is easy to do for read only commands but privileged commands would be denied. I dont see anywhere in bfgminer documentation that allows easy full access to the local network.
As far as monitoring goes, would the read only be fine?

Yes read only is all I would asking for Id like to be able to monitor my remote rigs via the VPN without using the webpages Any changes to pool etc id login to the miner web interface and do it manually

bfgminer does what you seek, details in the REAME.RPC file that comes with bfgminer source.

a combination of
--api-allow
and if needed
--api-groups

The "W" group for read/write and "R" group for read only.
Iffin I recollect correctly you can even have a "P" group with selective write access.

I posted somewhere(probably the OC thread) some awk code to gather neat data from a hoopiter remotely.
Same awk code runs local(miner) or remote(PC somewhere on net), I think the pi has awk most *nix systems do.
It can easily be twisted to display whatever is available.
It already has many of the possible responses coded in, just commented out.

YMMV
tolip

EDIT
And "miner.php" is an excellent way to monitor from a PC once access is allowed on the device.

Yeah, i dont think it needs to be that complex if.... and you may know this....
Will --api-network work in conjunction with --api-allow?
The readme says its "overrides" if both are present, but that doesnt mean --api-network goes "ignored" right?

e.g. --api-allow W:192.168.0.1 <- this will allow a specific host
e.g. --api-allow W:192.168.0/24 <- this will allow whole subnet
e.g. --api-allow W:192.168.0.1,10.0.0/24 <- this will allow 1 specific host and whole 10.0.0.0 class C subnet

Not sure but might need 127.0.0.1 if ya want to query the API from the ssh session if you use --api-allow.
It's been a while and my 28nm stuff is 'sleepin' else I'd check.

YMMV
tolip

Well, I need it to allow the whole subnet without knowing the subnet, so Im wondering if the --api-network will still work like that when --api-allow is used for W:127.0.0.1