I had the exact same issue.
The problem appears to be that when the Stoker is set for a fixed IP, the subnet and gateway addresses are not getting set correctly. I tried to manually set them on the stoker, but the values wouldn't save.
To get around this, I set the stoker to use DHCP (needed to read the manual(from rocks site) on how to reset this). Then, on my netgear router, I was able to assign a fixed IP address to a MAC address. I only had 2 devices connected to the router at the time, so it was easy to determine the MAC belonged to the Stoker.
I looked briefly, and it doesnt look like the Linksys WRT54G has the ability to assign fixed IPs by MAC address.
My suggestion to test this all out in your environment to confirm if your issue is the same, would be to set the stoker back to DHCP,and let it get assigned a router assigned address. Once assigned, set the port forwarding on the Linksys to the assigned address. Now, try to access it through the 67.131.50.xx address.
If that is indeed the case, a couple of options to fix it long term that I see:
- a netgear router. An added bonus of the netgear is that it also supports dyndns.org, which allows me to setup on the router publishing the routers external address as a URL like marksegg.kicks-***.net, that will always resolve to my external IP.
- assign all OTHER devices on your network fixed IP in the high (200+) range. That way the stoker always gets the .1 address when turned on. in essence, a fixed address I guess.
- Kaytat gets this resolved. I sent a note a couple weeks ago, and it was acknowledged, but no timeline for a fix was provided.
Let me know how this works out for you.
Mark
