Hmm, another user suggested port 4029 to me as well, and I tried it and it didn't work. I'll dig a little deeper and try to figure it out, thanks.
its the same as cgminer api but its set to use 4029 instead of 4028.
Nope, that didn't do it, still shows it as "off line". I tried 4027 and 4030, too. No other ip addresses show on my router so it must be behind the R1 somewhere.
Edit
I looked into the running processes and it does appear that port 4029 is the correct port, but CryptoGlance does not want to talk to the U3 on that port. Any other ideas?
On another note, I restarted the R1 and now the U3 isn't hashing at all. I restarted it several times last night and the U3 always came back hashing, but it's dead now after a restart of the R1 (I'm not at home, I am accessing my home computer over VPN).
its the same as cgminer api but its set to use 4029 instead of 4028.
Nope, that didn't do it, still shows it as "off line". I tried 4027 and 4030, too. No other ip addresses show on my router so it must be behind the R1 somewhere.
Edit
I looked into the running processes and it does appear that port 4029 is the correct port, but CryptoGlance does not want to talk to the U3 on that port. Any other ideas?
On another note, I restarted the R1 and now the U3 isn't hashing at all. I restarted it several times last night and the U3 always came back hashing, but it's dead now after a restart of the R1 (I'm not at home, I am accessing my home computer over VPN).
I haven't tried accessing the api outside of the R1. It's possible openwrt may have a light version of ip tables blocking that port. If so, you'll need to allow inbound/outbound traffic on that port.
.