Static IP address - Help required.

Some time ago I requested a static IP address from my ISP (Madasafish) with a view to setting up a surveillance web server.
To test things (prior to configuring the NAT), I�ve configured my router to �.
1). Allow access to the config page from the WAN.
2). respond to WAN pings
3). allow WAN access from any IP address.
In this mode the router�s config page will only appear in a browser running this side of my ISP�s servers. If I type the IP address from anywhere else e.g. work (or use a web proxy from home, e.g. VTunnel), the address cannot be resolved.
I suspect that the static IP address I have been given is not live on the WAN side of their servers (just on the client side) and that my static IP address is being translated via their servers.
Note that my router is configured for the fixed WAN side address (no DHCP) & web based searches of my IP address confirm the IP address I have been given.
My ISP has refused to help any further (claiming as far as they�re concerned, it�s okay!)
Is there anyone out there who can help/advise?
Thanks,
PT7777

I think you've set it up wrong. Allocate the IP address to the router and use NAT to forward to your private LAN.

Hi,

I tried the IP you gave me via PM (the one they assigned you), and it did work fine.

I could trace through their network, via their DSL gateways, to your router. ICMP ping also worked fine - which does demonstrate that the IP is configured and routed correctly.

I'm still not sure what you mean that the IP cannot be resolved. By nature, no name resolution is needed on an IP address. (Generally speaking, you only need resolution of a name to an IP).

Matt

Edited by deleted (Sun 11-Oct-09 21:59:48)

Hello Matt / Batboy,
Probably a bad choice of word 'resolve'. I should have said "it just can't find it"!
With the router configured as detailed earlier, surely I should be able to see its config page? (�. Or should the router�s front side WAN address be forwarded to the client side LAN address?) I wouldn't have thought so.
Even so, why does it work here .... but not from anywhere else?
You say you've traced it back to my router??
What I've seen only shows something back to the Brightview servers. I get the same results when testing it from work (� when my router's turned off!)

I just don't know what you mean by 'just can't find it'.

Should you be able to see the router config page from an external location? Maybe but some routers have it disabled, or have firewall rules blocking it - OR - even have it run on a complete different port such as 8080.

As I showed the other night - a trace does get to the router and ends there.

traceroute to 80.189.x.x (80.189.x.x), 30 hops max, 40 byte packets
1 91.199.78.254 0.022 ms 0.018 ms 0.009 ms
2 lonap-gw2.plus.net (193.203.5.155) 1.862 ms 1.926 ms 1.991 ms
3 x.x.adsl.brightview.com (80.189.x.x) 34.039 ms 35.732 ms 37.757 ms

If your router was off, it would likely get to hop 2 and then time out. Their system (workplace) may have assigned the same IP to another user as well but that is unlikely as you would have greater problems like not being able to access the internet at all.

Matt

Edited by deleted (Sun 11-Oct-09 22:49:20)

Hello Matt,
Can I EM you with the setup page for the router's config?
It confirms the port as 8080.
I understand that it is possible to force the port used when typing the address in the browser?? .... i.e you simply type "80.189.xxx.yyy:8080")
Still nothing though.
Should I be using some other port?
(I'll retest the traceroute tomorrow when the router is off)

Message me with the IP and the port you have assigned it. I don't need to login details to be able to see if the port is opened.

Just ensure you have turned on remote access and allowed it in the firewall.

Matt

Right.

That works fine. I can get to your router pages (Voyager 2091). However, I urge you to password protect it - if possible, as it's giving away loads of potentially sensitive information to any one that can get to the IP/port.

Matt

Hello Matt,
Well I'm impressed! ... but how did you manage to access it??
I'm also surprised what you say about a password on the router. It does have a password (& it's not the default!) + it needs the password to access the 'advanced' pages.
PT7777

I just put it in to my browser.

Well, the router gives away a lot of information for something that has a password. I would turn the remote web admin off, unless you really need it!

Matt

Hi Matt,
I appreciate your time/input on this.
However, I still don't understand how it is working for you when I have been doing just the same.
Can I confirm that you just typed the IP address appended with ":8080" to access the router?
PT7777

Correct.

It is possible that the other locations you have tried it from, do not allow outbound port 8080 access.?

Matt

OK
Can you identify a proxy server that'll show it working from here??
PT7777

None that I know of that will allow access to that port.

Matt

What's so special about this port that sites would want to block it?
Is there another port I can try that's unlikely to be blocked?
PT7777

I mean the computer or network you are trying from might block it due to firewall walls.

Proxy sites, generally speaking will only give access to port 80 or 443 as they are the most common web ports. People generally don't need to access higher ports like 8080.

Ok Matt,
I'll have to test this from somewhere else tomorrow (daytime).
Regards,
PT7777

Given xilo has shown the web admin is working, time to move onto the web server and get that up and running, and if this is on port 80 then most of the proxy and other confusion will go away.

Best testing is another connection that does not use a proxy, i.e. proxies can cause all sorts of confusion

Is anyone else wondering why the OP needs/wants the router's admin pages accessible? Surely he needs to be forwarding to the camera's (web)server?

Yeap am wondering, perhaps they thought it was a good test of the static ip side of things

In reply to a post by Xris:

Is anyone else wondering why the OP needs/wants the router's admin pages accessible? Surely he needs to be forwarding to the camera's (web)server?

I'm not wondering because I read the first post where it is explained.

What DVR / security system are you using? Does it have a web based GUI or does it have software specific to the DVR? Typically you get two types of system, the ones with web front ends require port 80 forwarding to the IP of the DVR and the ones with specific software require a range of ports forwarding to the DVR (IE the ones I have installed require ports 30010-30020 forwarding to the DVR)

Hope this helps!

Hello All,
Just for your info, this has been resolved okay.
I seemed to be unfortunate in that every location I initially tested the remote access, the IP was blocked.
After Xilonet confirmed he could access the IP I tried other locations (thanks for your help Xilonet!)
..... and yes, I was just using the router's page as a simple means to confirm I could access the IP remotely.
Regards to all,
PT7777

You're welcome.

Glad you have it all working now.

Matt