I need some clarification on the roll of wiser being the intermediary when accessing a set of static images from a ipcam via WAN. I have found these two post extremely helpful in setting up the wiser and have followed them to access my cameras via LAN & WAN : [URL]http://www.cbusforums.com/forums/showthread.php?t=5867[/URL] & [URL]http://www.cbusforums.com/forums/showthread.php?t=6451[/URL] This, however has confused/eluded me (ref the text in the red): [quote="kjayakumar, post: 30355"]Here are some quick notes: - since you are Wiser-as-a-LAN-device mode, traffic routing is thus dependent on both your actual router and the Wiser - lets say I have an IP camera, 192.168.2.100, wiser on 192.168.2.1 and the actual router on 192.168.2.50 - The PICED project will need to be informed about the camera's internal URL and its external port, eg: 9090 - you'll need to set the IP camera's gateway to point to the Wiser, 192.168.2.1 - you'll need to ensure that the Wiser is setup to have its LAN gateway set to the actual router, 192.168.2.50 - you'll need to setup a port forward of port 9090 on your actual router to go to Wiser. so the rule on the router, would look like: external port: 9090 internal ip: 192.168.2.1, internal port: 9090 . [COLOR="Red"]What this means is that when a user interface (Flash, iphone, etc) connects from the outside world, it will send a message to Wiser on its control port (8888, you'll need that to be port forwarded as well) asking Wiser to setup its own port forward to the camera. Wiser will do this.[/COLOR] Then the traffic path will look like external ip->actual router external ip->actual router internal ip 192.168.2.50 fwd -> Wiser fwd -> camera and then the return path is the exact reverse. - There's a lot of settings to check so I recommend drawing all this out on paper, writing out what each devices gateway is, setting up all the relevant port forwards. The other alternative is of course to just expose the camera's directly to your actual router. So just port forward 9090 straight from your router to the camera IP and make sure the camera is set to gateway to your router. The penalty there is that your camera's will always be visible to the external world [COLOR="YellowGreen"]whereas in the Wiser-as-middle-man scenario, it will close the port forwards after the last UI has disconnected.[/COLOR][/QUOTE] What I make from all this is that: wiser should see that the Iphone app is calling up the camera widget (piced project) and that the port forward settings put into the widget should be called upon with the trigger given by the control port 8888. This would then inturn open up my port on the wiser and let the goodness flow.... However; it doesn't work like this. The only way I can get the Iphone to work via WAN is to put a port forward into the wiser too. This means if anyone on the WAN types in the external IP address with the correct port they can get directed straight through to my axis cameras live view page...... I want what kjayakumar has stated in green in the above quote but can't seem to get it to work. Maybe I have misread things but the only way I can see that wiser is able to open the correct camera port is via the port number entered into the 'forwarded port' value of the widget; although this doesn't seem to make wiser turn that specific port on & off. This stuff is complicated :D and I know that it is a setting in the wiser or piced project that will do what we want as everything else works perfectly. What is the missing piece?
