WAN in router settings gives me an internal IP. Why?

bibi-phoque

I'm trying to help a friend setting up a new Wifi IP Camera. It works perfect from within his network, however we haven't been successful connecting on it from the outside. Usually, I check with the WAN IP to see if the port are forwarding correctly (actually this camera is upnp so there is no need to forward anything), however there is something really weird with this network setup.
When logging to the router, I was expecting an external IP for the WAN but instead the IP is 192.168.10.227... This doesn't make any sense!
His provider is Ripplecom which works with a dish on the roof and a modem (plugged on a socket). basically, the input of the modem is the dish, the output goes to the router.

If I tried to log on the modem (192.168.10.227), I end up on a page call "mikrotik" which looks like an admin page but I don't have the password.

Is anybody familiar with this setup? The problem is that we can't figure out what is his real external IP and how we can let ports "go through" this modem to reach the camera from the outside.

Need help from the experts :-)

FSL

You need the public IP of your connection and then you need to forward the in coming port to the internal IP address of the camera. You can use What's My IP to find out your public IP address.

You may not have a fixed IP address and may need to use something like DynDNS, so you could access the camera regardless of the IP address allocated by Ripplecom.

Kensington

Do Ripplecom provide you with a public, globally routable IP address?

Some of the wireless providers are just one big NAT based network - one public IP and every subscriber sits behind that and gets a private IP assigned by Ripplecom.

bibi-phoque

Kensington wrote: »

Do Ripplecom provide you with a public, globally routable IP address?

Some of the wireless providers are just one big NAT based network - one public IP and every subscriber sits behind that and gets a private IP assigned by Ripplecom.

This is exactly what I'm thinking so I'm glad you are saying this. I didn't know those type of setup existed, i.e. it is like being part of a huge internal network.
So now the question is how do I access the home network from Internet because the IP shown on whatismyip.com just times out (obviously as Ripplecom doesn't redirect to my friend's network).

Funny, I went to my friend so confident, thinking I have seen it all, but this is new to me!

vibe666

as FSL says, go to http://www.whatsmyip.org/ and see what your external IP address is showing up as and then see if you can use a similar service to what dyndns used to do, i think http://www.no-ip.com/services/managed_dns/free_dynamic_dns.html still do a free redirection service.

you might even find that the IP cam has an option for it in the settings if it's a half decent one.

bibi-phoque

vibe666 wrote: »

as FSL says, go to http://www.whatsmyip.org/ and see what your external IP address is showing up as and then see if you can use a similar service to what dyndns used to do, i think http://www.no-ip.com/services/managed_dns/free_dynamic_dns.html still do a free redirection service.

you might even find that the IP cam has an option for it in the settings if it's a half decent one.

This is not the problem unfortunately. It is not a DNS issue. This IP seems to be shared by all ripplecom customers and what I'm looking for is how to reach the home network from WWW.
Using noIP will basically send 192.168.10.227 to their server which as you can see is not an external IP.

vibe666

have you confirmed 100% that ripplecom don't provide you with your own external IP?

Kensington wasn't sure, so it's possible that your modem just isn't passing an external IP to your router's WAN port and instead is just assigning an internal address for some reason.

all i'm saying is don't give up until you know for sure as it *might* still be a fixable problem.

i just checked the Ripplecom T&C's and section 7.9 says:

7.9 Any network address assignments issued by Ripplecom (i.e., Class C address Internet Protocol numbers) are the property of Ripplecom and are hereby deemed to have been loaned to the Subscriber for so long as this Agreement shall subsist. In the event that the Services to the Subscriber are discontinued for any reason, all such network address assignments, including IP addresses, will revert to Ripplecom immediately.

which seems to indicate that all may not be lost.

bibi-phoque

vibe666 wrote: »

have you confirmed 100% that ripplecom don't provide you with your own external IP?

Kensington wasn't sure, so it's possible that your modem just isn't passing an external IP to your router's WAN port and instead is just assigning an internal address for some reason.

all i'm saying is don't give up until you know for sure as it *might* still be a fixable problem.

i just checked the Ripplecom T&C's and section 7.9 says:

which seems to indicate that all may not be lost.

Thanks for the reply. We will give a call to Ripplecom today and see.
There is an admin page on the modem (something call mikrotik that you can reach at 192.168.10.227), if I could login maybe I can set it up to passthrough the external IP.