Can't assign Static IP

Did you forget to type in your default gateway into your router? Your gateway can't be from the 10.0.0.0 - 10.255.255.255 range.

Could you do a traceroute to your public IP.

Could be that your ISP has configured static IP on one of their router's interface facing towards the next hop router on the internet. And then dest NAT your connection through one of their NAT concentrators.

 

Well the gateway he gave me to use was 10.108.xx.x. I haven't entered anything into my router.

Have done via commando prompt. What do you need from it?

A question- is it possible to only have the Xbox have a public IP and then the other computers, tablets etc. have private IPs, for security reasons? Or need they all have the public IP for it to work. The ISP made it sound like I could simply enter the settings
into a computer/Xbox and then only that device would get the public IP.

 

Regardless if the public IP is assigned by a DHCP server, or made static, your router should still overload this one public IP into many with the force of Network Address Translation.

I don't know the subnet mask of your public IP, but the default gateway (next hop router) should be in the same subnet. The 10.108 is not.

It's not likely that your D-Link support more than one WAN interface.

Could you do a traceroute to the 10.108.xx.x (default gateway) and post up the result.

 

I think we should have as much details as possible, before you reach back to your provider.

I'm still curious to what device (inside of your home) your D-Link terminates into. It has to be a networking device of some kind. Somwhere.

Perhaps the traceroute to your default gateway will reveal such information.

 

For Large Scale NAT (CGN), the IANAs recommendation is not to use the
RFC1918 shared address space, since the subscriber and provider may overlap with one or the other. They instead recommend the 100.64.0.0/10 (255.192.0.0) address space.

 

Do you live in an apartment? Where your fiber feeds into provider router, placed in the basement of your building.

 

@Taidara , if he plugs the xbox right into the wall bypassing the router and his nat is still not open , I was under the impression that there is NOTHING he can do on his end to remedy that , but is there ?

 

@Bimnoggy - That is correct.

I think there might be a misconception from the provider's perspective, exactly where this public IP should be assigned. As it seems know, this public IP has been assigned to an interface on the boundry between the provider network and the Internet. It then
hits a NAT concentrator inside of the provider network, before it reaches the CPE.

 

The traceroute to the public IP:

Microsoft Windows [Version 10.0.10586]

(c) 2015 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>tracert 80.71.xxx.xx

Tracing route to xxx_xx.epte.fi [80.71.xxx.xx]

over a maximum of 30 hops:

1 2 ms 1 ms 1 ms 10.108.xx.x

2 2 ms 2 ms 1 ms 192.168.xxx.x

3 10 ms 2 ms 1 ms c1.c1-a11.usrs.rt [172.28.xx.xxx]

4 3 ms 2 ms 1 ms c5.c1-c5.usrs.rt [172.28.x.x]

5 2 ms 1 ms 1 ms fw01.fw01-c5.usrs.rt [172.28.x.x]

6 2 ms 2 ms 2 ms br2.br-fw01.rt.parknet.dk [80.71.xxx.xxx]

7 4 ms 2 ms 11 ms ae3.cr1.taas.gc-net.eu [212.98.xxx.xx]

8 2 ms 2 ms 2 ms ae0-0.taas1cr2dk.gc-net.eu [77.243.xx.xxx]

9 2 ms 2 ms 3 ms 213.242.xxx.xx

10 * * * Request timed out.

11 31 ms 10 ms 10 ms ae-22-3618.ear1.Stockholm1.Level3.net [4.69.xxx.xxx]

12 11 ms 12 ms 17 ms 182.250.xx.xxx.in-addr.arpa [212.73.xxx.xxx]

13 17 ms 17 ms 17 ms 213.192.xxx.xx

14 18 ms 17 ms 17 ms 213.192.xxx.xx

15 17 ms 17 ms 16 ms 139.97.x.xxx

16 139.97.x.xxx reports: Destination host unreachable.

Trace complete.

C:\WINDOWS\system32>

C:\WINDOWS\system32>

The traceroute to the gateway:

C:\WINDOWS\system32>tracert 10.108.xx.x

Tracing route to 10.108.xx.x over a maximum of 30 hops

1 2 ms 1 ms 1 ms 10.108.xx.x

Trace complete.

C:\WINDOWS\system32>tracert 10.108.xx.x

Tracing route to 10.108.xx.x over a maximum of 30 hops

1 2 ms 2 ms 1 ms 10.108.xx.x

Trace complete.

C:\WINDOWS\system32>

When I did a traceroute to the IP that he gave me to enter into the Xbox *10.108.xx.x, almost identical to the gateway), all 30 hops timed out.

 

Yeah I live in an apartment. The router is connected to a really weird switch thing sitting on the wall. It's not a modem. Not sure what it is.

 

Thanks!

You're behind three layers of NAT.

The third hop count, 172.28.xx.xxx, is the NAT concentrator inside of your service provider network.

Beside the NAT concentrator and your D-Link, there's an additional L3 device (router). Not sure why.

There's a simple explanation to why you can't assign the 10.108.xx.x address space to a device on your network, and make it work. In an earlier post you claimed that your WAN IP equals 10.108.xx.x and your LAN IP equals 192.168.x.x. These two don't belong
on the same subnet. For this to work, they have to be on the same subnet.

I think you should reach out to your service provider and ask if they can assign you with a public IP, on an interface which is neighboring with your modem. And why do they use an additional L3 device, part from the NAT concentrator.

Keep us posted.

 

Triple NAT? Holy hell I never even knew that was possible lol. I guess the ISP's support guy is a meathead since he doesn't even know how their own network is set up.

Do you know if it will be possible to only have my Xbox have a public IP, or will all other devices/computers in our home get it too? I'd strongly prefer the Xbox only to, because of security.

 

Well I talked to them today. They said the only way for my Xbox to work is if I buy some sort of ''switch'' and then port forward from there or something, but I couldn't really get a hand of what he meant. Got any idea? He also confirmed they've upgraded
their firewall with another layer to be more secure.

 

You can't buy anything that'll resolve your situation, and why would you need to buy something that is already in your possession. Yes, your D-Link wireless router.

Not sure why they would need to implement this many layers of NAT. The CGN part that I can understand, but creating NAT policies on their firewall towards customers NAT? If one NAT device isn't bad enough.

Is the ISP you're currently using your only option to go with?

I think you should give your ISPs support another try, but this time, try speak to an agent at second, or third line.

I know of a setup that may work, but the problem is that it will probably just work with the first two layers of NAT (not sure about the firewall NAT policy though). I've never seen an ISP do more than one layer of NAT (Carrier-grade NAT/Large Scale NAT).