Link to home
Start Free TrialLog in
Avatar of pauldownham
pauldownham

asked on

Wireless IP camera port forwarding on a Sagem 3102

On my previous router (Netgear), the only port forwarding boxes to fill in to set up a wireless IP camera were: name, from port, to port, and protocol, where I'd answer them as "camera","4440","4440" and "TCP". And this worked fine.

That router broke, so now I've got a Sagem Fast3102, and this one's port forwarding screen includes two extra boxes for redirection port and local IP address - and both are required fields.

In the list of built-in existing rules, all the entries (things like Skype and Spotify) have the redirection port as "(null)" - but when trying to save the camera entry with nothing in the box an error message pops up saying it requires a value between 0 and 65535. The IP addresses for the existing rules are all 192.168.1.10 to 192.168.1.13.

What values should I try in the these two new boxes?

 
Avatar of lords1979
lords1979
Flag of United States of America image

If this router allows for multiple external ip addresses, it is asking for the external ip address, port, internal ip address, and port.
do you have a screen print of the page in question you can post to get a better understanding of what you are referring to?
Avatar of pauldownham
pauldownham

ASKER

Hi,

here is the screenshot of the page where a new port forwarding rule is added . you will see that all the fields are required (red boxes).User generated image
I would set from port, to port, and redirection port as the the 4440.  The local ip address would be the ip of the camera.  Let me know if this works.
Hi, I've been playing around with it during the day and discovered that a redirection port entry of "0" results in the same "(null)" entry on the rule table as the built-in services, so I'm assuming that's probably best?  

Unfortunately this is a remote system (the camera is looking after an empty house), so I can't cable to the camera to discover what IP address its set to, and I didn't need to know it on the previous router to connect wirelessly.  
Let me ensure I am understanding this correctly.  The camera is plugged in to the local side of this router at the remote location?
No, its a wireless camera. It was originally set up and was working fine using a netgear router, but that router broke. So a friend who happened to be passing the house (which is in another country) popped in and replaced the netgear with the Sagem 3102. I can attach to the Sagem from home (the overseas phone line has a static ip address) and I changed the SSID and WEP of the Sagem  to match the old settings on the netgear and opened up port 4440 (as before) as a new rule, then remotely rebooted it. I had expected the camera to then connect successfully but it didn't. So I assumed I had made a mistake filling out the port forwarding (because it had the extra boxes compared to the netgear), and hence I asked the question here.
Because it is on the wireless of the router, this is on the local network to the router.  You have to tell the router when it receives packets destined to the external ip address with the 4440 port where to forward those packets on the internal network.  You will need to put the ip address of the camera in there for the port forward to work.  What is the DHCP scope setup on the router?  If you don't have the camera set to a static ip, it should most likely be grabbing the first address from the DHCP pool (assuming there is nothing else connected to this router wirelessly or wired).  Put that IP address in as the forwarding address to the forwarding rule.
The router says its DHCP runs from 192.168.1.10 to 192.168.1.50, and I don't seem to be able to alter those settings.

My old notes say the camera was on 192.168.1.253, which if thats a fixed address I guess I can only alter by connecting the camera to the router by cable - which would be a bummer!

There's nothing else currently attached to the router, and I've already tried 192.168.1.10 to 192.168.1.20 as hopeful guesses for the setting - so its looking like bad news!
try 192.168.1.253 incase it was statically assigned.  This is on the same subnet so it will work if this was a static assignment.
ASKER CERTIFIED SOLUTION
Avatar of pauldownham
pauldownham

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial