A WAN ip is showing up as a LAN IP in router status

[SEANHAWG 1]

I tried to help one of my customers get his DVR set up. I was going to login to his router and set up his port forwarding. So I told him to go to IP chicken and tell me what his IP says:

So I got it and it definetely looked like a normal WAN IP.

SO I then told him to go into his router menu and tell me what his WAN IP shows up in there as:

The problem is that it was showing up as a typical 192.1.1.2 LAN IP?????? Why is that?

 

So the problem is that I cannot log into his router and I cannot setup his port forwarding. And if I cant log into his router than how is he going to log into this DVR from a remote location?

[thewireguys 3]

What type of ISP does he have? is his modem also a router?

[SEANHAWG 1]

Its DSL. His modem runs into his router. Much like how mine was setup.

[thewireguys 3]

What is the manufacture and model number of the modem?

[SEANHAWG 1]

I'll have to get that when I talk to him again on Monday. I know it was a Netgear, not sure on the model.

 

I am thinking it may have something to do with a wierd ISP configuration. Gosh dang networking, there are so many variables that can come into play .

[Soundy 1]

192.1.* isn't actually a LAN IP. 192.168.* are reserved for class-C private addresses, but 192.anythingelse isn't.

 

Either way, it's possible the ISP is running an extra NAT layer of their own, which would make it practically impossible to route connections back into a customer's system - they'd need to set up their own VPN using a service like TeamViewer or something else along those lines.

[thewireguys 3]

192.1.* isn't actually a LAN IP. 192.168.* are reserved for class-C private addresses, but 192.anythingelse isn't.

 

Either way, it's possible the ISP is running an extra NAT layer of their own, which would make it practically impossible to route connections back into a customer's system - they'd need to set up their own VPN using a service like TeamViewer or something else along those lines.

 

or the modem is also a router.... I had the same problem with a customer and you have to bridge the modem/router or remove the other router.

[Soundy 1]

192.1.* isn't actually a LAN IP. 192.168.* are reserved for class-C private addresses, but 192.anythingelse isn't.

 

Either way, it's possible the ISP is running an extra NAT layer of their own, which would make it practically impossible to route connections back into a customer's system - they'd need to set up their own VPN using a service like TeamViewer or something else along those lines.

 

or the modem is also a router.... I had the same problem with a customer and you have to bridge the modem/router or remove the other router.

This is true, too... it would be helpful to know the model of the modem.