Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
The (old) mail from my ISP states this:
IP address: xx.xxx.1.10
Betnask: 255.255.255.0
Gateway: xx.xxx.x.x
DNS: xx.xx.xxx.xx, xx.xx.xxx.xx

With the old router I was able to let the Synology software do the work for me - including port forwarding. And it worked fine.

With DCHP + NAT i get the right IP, when using www.whatsmyip.com - in bridge mode I get the common/Shared IP used by the building.

The internet IP´s are in the range 192.168.1.1-192.168.1.50

Thansk for all you efforts to get me going strong again :confused:
 
This is my first Apple Wi-Fi device, and, so far, I´m not that impressed :)

Neither of the IP addresses you posted in the picture is routable on the internet , they are private address space.

You'll have the same issues with another network vendor.

The Internet Assigned Numbers Authority (IANA) has reserved the following three blocks of the IP address space for private internets:

10.0.0.0 - 10.255.255.255 (10/8 prefix)
172.16.0.0 - 172.31.255.255 (172.16/12 prefix)
192.168.0.0 - 192.168.255.255 (192.168/16 prefix)
 
From your speed test earlier it looks like your Internet IP address is 80.71.134.118. I can actually ping that address. That should be the static address the IP gave you yes? Did you enter that in the static IP section in the TC setup screen? From your Airport Utility screenshot it looks like you did not.

That 192 is an internal address and not your Internet IP address.

Well, no. The instructions from my ISP told me to enter what you see in the screenshot. Did the same with the old router.

----------

Neither of the IP addresses you posted in the picture is routable on the internet , they are private address space.

You'll have the same issues with another network vendor.

The Internet Assigned Numbers Authority (IANA) has reserved the following three blocks of the IP address space for private internets:

10.0.0.0 - 10.255.255.255 (10/8 prefix)
172.16.0.0 - 172.31.255.255 (172.16/12 prefix)
192.168.0.0 - 192.168.255.255 (192.168/16 prefix)

I´m aware of that. But it makes other see my IP as 80.xx.xxx.xxx. Don´t know how, but it worked fine with the non-Apple router´s.
 
It goes directly to the TC. No modem, and it´s fast...

If your ISP assigned a static IP for you this is it.

The previous poster is correct. The reason you are getting the double NAT is because you are trying to use two local assigned IP's.

I suspect what your ISP has done is assign you a "static" link local IP in the 10.*.* range rather than the static range of 80.71.*.*

The true IP of that TC is what you see in your speediest .

attachment.php
 
192.168.1.20 is manually assigned to the NAS.

I think I see the problem. Your TC is assigning DHCP addresses in the range 192.168.1.2 through 192.168.1.100 and you cannot assign a fixed IP inside that range. Get on the NAS and give it 192.168.1.102 (outside the DHCP range) as a fixed IP and I bet your problems go away.

The double NAT issue may or may not cause you problems still. I would go to bridge node and that will clear the double NAT error message.

Edit: On second thought, it you go to bridge mode it will break this because the ISP router is apparently not going to let you use the 192... IP range. Just manually enter the 192.168.1.102 address in the NAS and leave everything else alone and see if that fixes things.
 
Last edited:
Type in 80.71.134.118 as the static IP then use DHCP in the 192.* range to serve up local IP's to devices connecting to your TC.

If I do that, I don´t know what to type as the routers address...:mad:
 

Attachments

  • Skærmbillede 2014-08-10 kl. 20.21.52.png
    Skærmbillede 2014-08-10 kl. 20.21.52.png
    63 KB · Views: 127
Here's how you find out.

Open the Airport utility. It should look like this :

There you will see the router address.
 

Attachments

  • address1.png
    address1.png
    77.8 KB · Views: 164
  • address.png
    address.png
    64.3 KB · Views: 168
When you say that did not help, does that fixed IP I gave you allow the NAS to get on the network? It looks like your other devices are working fine.

How is this screen setup under Airport Util in the Network tab then Network Options at the bottom?

mcGmfaK.png


----------

If I do that, I don´t know what to type as the routers address...:mad:

That would normally be 80.71.134.1
 
We are baffled because what I think his ISP has done is assign a reserved IP address from their router's DHCP server in the building not a true static IP.

The internet enters the building and goes to an ISP owned router that probably has several extenders all using the 10.* range which is a local IP address. It is already using NAT. Then when the OP tries to use a 192.* range it produces the double NAT problem.

I'd call my ISP and ask for a real Static IP rather than a reserved DHCP IP.

My guess is thats going to cost him more money. ISP's don't just give away a static IP. Especially since the normal IP numbers have all been given out and are moving to IPv6.
 
When you say that did not help, does that fixed IP I gave you allow the NAS to get on the network? It looks like your other devices are working fine.

How is this screen setup under Airport Util in the Network tab then Network Options at the bottom?

Image

----------



That would normally be 80.71.134.1
My NAS is on the network, but I can´t access it from the internet. I share pic´s with my oldest daughter and my father on it´s PhotoStation.

What do I typer under "routers address"??
 

Attachments

  • Skærmbillede 2014-08-10 kl. 20.46.03.png
    Skærmbillede 2014-08-10 kl. 20.46.03.png
    94.6 KB · Views: 143
Type in 80.71.134.118 as the static IP then use DHCP in the 192.* range to serve up local IP's to devices connecting to your TC.

Peace>>> OP was saying if he uses Internet in other apartments etc. everybody in the building shows the same 80.71.134.118. I'm wondering if they just gave OP a DHCP reservation on his port at 10.103.1.10 and called it a static IP. What do you think? When he sets up with 10.103.1.10 as static he is able to get on the Internet. It sounds like the ISP has a router on 80.71.134.118 that serves the whole building with DHCP addresses.
 
We are baffled because what I think his ISP has done is assign a reserved IP address from their router's DHCP server in the building not a true static IP.

The internet enters the building and goes to an ISP owned router that probably has several extenders all using the 10.* range which is a local IP address. It is already using NAT. Then when the OP tries to use a 192.* range it produces the double NAT problem.

I'd call my ISP and ask for a real Static IP rather than a reserved DHCP IP.

My guess is thats going to cost him more money. ISP's don't just give away a static IP. Especially since the normal IP numbers have all been given out and are moving to IPv6.

Peace>>> OP was saying if he uses Internet in other apartments etc. everybody in the building shows the same 80.71.134.118. I'm wondering if they just gave OP a DHCP reservation on his port at 10.103.1.10 and called it a static IP. What do you think? When he sets up with 10.103.1.10 as static he is able to get on the Internet. It sounds like the ISP has a router on 80.71.134.118 that serves the whole building with DHCP addresses.

We are on the same page my man !!

They may all see the same 80.71.134.118 number as the router but I'd bet ya they all have a 10.*.*.* IP addresses.

That 80.71.134.118 IP number will change from time to time depending on the load balancing of the ISP.
 
Last edited:
My NAS is on the network, but I can´t access it from the internet. I share pic´s with my oldest daughter and my father on it´s PhotoStation.

What do I typer under "routers address"??

Okay... don't change anything there it is fine. I think the NAS is on the Internet. Can you get on the NAS and from the NAS confirm the NAS can see the Internet (not the other way around).

I think your NAS is on the Internet and the issue is with the dynamic DNS service you are using on the NAS. You need to update the dynamic DNS service/settings on the NAS so it knows the IP has moved. Then you should be able to come into the NAS from outside on the Internet.
 
We are on the same page my man !!

They may all see the same 80.71.134.118 number as the router but I'd bet ya they all have a 10.*.*.* IP addresses.

That 80.71.134.118 IP number will change from time to time depending on the load balancing of the ISP.[/QUOTE
I don´t think so. It has been running flawlessly since i bought my first NAS.
If I don´t use the 10.103.1.10 my IP shows as 80.71.135.xxx - exactly the same as my neighbor.

Okay... don't change anything there it is fine. I think the NAS is on the Internet. Can you get on the NAS and from the NAS confirm the NAS can see the Internet (not the other way around).

I think your NAS is on the Internet and the issue is with the dynamic DNS service you are using on the NAS. You need to update the dynamic DNS service/settings on the NAS so it knows the IP has moved. Then you should be able to come into the NAS from outside on the Internet.

I think you are right. I´ll look into it.
Thanks again for all your help. I´m really sure if I had you all confused, but, as mentioned, I´m not that good when it comes to network.
 
I think you are right. I´ll look into it.
Thanks again for all your help. I´m really sure if I had you all confused, but, as mentioned, I´m not that good when it comes to network.

Glad to help. What made this very confusing (not your fault) is your ISP is using a very odd method of giving you a static IP and it threw us all off. :)
 
All that effort from you guys, and it still not works.
If I use 80.71.134.118 both as IP and router address, I can´t go on-line...
That's because you're telling your router to connect to itself to route data, and that won't work.
 
When you connect in another persons room there how are you connecting ? Ethernet cable or WiFi ?

Do all apartments/rooms etc. in your building use ethernet ports ?
 
When you connect in another persons room there how are you connecting ? Ethernet cable of WiFi ?
WiFi on all devices. Just found out the NAS might be blocked by the TC. Can´t even update timezone or look for updates....
This might be the issue - how to allow the NAS through the TC!!
 
WiFi on all devices. Just found out the NAS might be blocked by the TC. Can´t even update timezone or look for updates....
This might be the issue - how to allow the NAS through the TC!!

You might want to read this :

http://en.wikipedia.org/wiki/NAT_Port_Mapping_Protocol

Also is your NAS connected to your TC via ethernet ?

If all fails restart the TC. Then start over.

Also make sure you have all the latest updates installed on both the TC and the NAS.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.