Welcome to the MacNN Forums.

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

You are here: MacNN Forums > Enthusiast Zone > Networking > How do I connect my Mac from the internet when having a local number (10.0.1.x) ?

How do I connect my Mac from the internet when having a local number (10.0.1.x) ?
Thread Tools
Mac Elite
Join Date: Feb 2001
Location: France
Status: Offline
Reply With Quote
Jan 6, 2003, 05:57 PM
 
having a ABS with my TiBook running on a IP address like 10.0.1.x, how do I get connected to this Mac from the outside internet like looking at my local website f.i.?

Thanks.
     
Junior Member
Join Date: Aug 2002
Status: Offline
Reply With Quote
Jan 6, 2003, 06:32 PM
 
In short you have to set-up port-forwarding. This will obviously depend on what you want to do. If it is just website hosting I think you only need to forward port 80 to the tibook, maybe 427 (looking at the OSX firewall - I am sure someone else can confirm).

To do this, you will have to assign an IP address to your TiBook rather than just getting one with DHCP. There is an option under Network preferences to use DHCP with Manual IP but I have never got it to work. Set the configure tab to manually, IP address to 10.0.1.201, Subnet Mask to 255.255.255.0, Router to 10.0.1.1 and DNS servers to 10.0.1.1.

To set up port-forwarding, open the Airport admin utility, click configure and type in your password. Click the port mapping tab and click the add button. Enter the public and private port numbers, 80 for web hosting (don't worry that they are the same), and make sure the Private address box has 201 so that the private address is 10.0.1.201.

Once you have done this, find out your public IP address and try it. If you are going through a router you are in for a lot more fun. Write here and I will post a follow-up if necessary. Hope this helps!!!

Rohan
     
Mac Elite
Join Date: Feb 2001
Location: France
Status: Offline
Reply With Quote
Jan 6, 2003, 06:45 PM
 
Originally posted by Putta:
In short you have to set-up port-forwarding. This will obviously depend on what you want to do. If it is just website hosting I think you only need to forward port 80 to the tibook, maybe 427 (looking at the OSX firewall - I am sure someone else can confirm).

To do this, you will have to assign an IP address to your TiBook rather than just getting one with DHCP. There is an option under Network preferences to use DHCP with Manual IP but I have never got it to work. Set the configure tab to manually, IP address to 10.0.1.201, Subnet Mask to 255.255.255.0, Router to 10.0.1.1 and DNS servers to 10.0.1.1.

To set up port-forwarding, open the Airport admin utility, click configure and type in your password. Click the port mapping tab and click the add button. Enter the public and private port numbers, 80 for web hosting (don't worry that they are the same), and make sure the Private address box has 201 so that the private address is 10.0.1.201.

Once you have done this, find out your public IP address and try it. If you are going through a router you are in for a lot more fun. Write here and I will post a follow-up if necessary. Hope this helps!!!

Rohan
As soon as I do DHCP on manual, there's no internet anymore.

I understood Port Mapping has to be done in the Airport Admin Utility but do not understand why it comes up with this 10.0.1.201 as I have, indeed, a DHCP so get addresses like 10.0.1.2 to 10.0.1.9 or so.

Why does webbrowsing stops as soon as I do this manual DHCP stuff?
Do I have to do something with NAT etc? As I'm using the ABS also for ethernet bridging to the iMac.

Thanks.
     
Junior Member
Join Date: Aug 2002
Status: Offline
Reply With Quote
Jan 6, 2003, 07:07 PM
 
OK, the most likely reason that you have lost internet connectivity is just a DNS server problem. Make sure the umber in the DNS server box is the same as the airport basestation which will then handle that for you. DHCP assigns you an IP address but can assign you one of 200 or thereabouts. You need to have a static address for port forwarding to work or it will be forwarding packets to another IP address. The basestation assigns numbers automatically using DHCP up to 10.0.1.201. After that, it leaves some blank for you to assign yourself.

Check your network preferences when set to DHCP. When you set them to manual, make sure the only difference is in the DNS server box and obviously in your IP address. If this doesn't work, find out the IP address of your ISP's DS server and enter that directly into the DNS server box.

Let me know...
     
Mac Elite
Join Date: Feb 2001
Location: France
Status: Offline
Reply With Quote
Jan 6, 2003, 07:25 PM
 
Originally posted by Putta:
OK, the most likely reason that you have lost internet connectivity is just a DNS server problem. Make sure the umber in the DNS server box is the same as the airport basestation which will then handle that for you. DHCP assigns you an IP address but can assign you one of 200 or thereabouts. You need to have a static address for port forwarding to work or it will be forwarding packets to another IP address. The basestation assigns numbers automatically using DHCP up to 10.0.1.201. After that, it leaves some blank for you to assign yourself.

Check your network preferences when set to DHCP. When you set them to manual, make sure the only difference is in the DNS server box and obviously in your IP address. If this doesn't work, find out the IP address of your ISP's DS server and enter that directly into the DNS server box.

Let me know...
Doesn't work. As soon as I give it the DHCP with manual, it doesn't get a Router number. neither after waiting some time (as it does when going back to DHCP) or even a restart. I did give the DNS numbers in the System Preferences->Network->Airport the same value as in the Airport Admin Utitlity->Internet, but as stated, no connection.

Have to sleep now, it's late here (2.30 pm...). Thanks anyway. Any more help is welcome!
     
Junior Member
Join Date: Aug 2002
Status: Offline
Reply With Quote
Jan 7, 2003, 06:01 AM
 
I think I've figured it out.

Instead of using DHCP with manual IP address, use the "Manually" option. With this scenario, keep Subnet mask to 255.255.255.0 and Router as 10.0.1.1 and set IP address to 10.0.1.201. Under DNS Servers, enter 10.0.1.1

I think that the IP address you are setting is outside the DHCP range (so that it doesn't change). Therefore you must configure manually. It is worth noting that any other computers can still connect to your basestation and have internet connectivity if set to DHCP.

Hope this works....
     
Junior Member
Join Date: Jan 2002
Location: Sewanee, TN
Status: Offline
Reply With Quote
Feb 23, 2003, 09:57 AM
 
This solution seems to work fine without a router, but it fails when I have a router between my cable modem and Airport.

What other changes do I need to make because of the router?

Also, if you have time, what specific ports need to be mapped? What do they do? Does it make a difference if they are mapped public, private, or both?

Thanks a lot!
     
Mac Elite
Join Date: May 1999
Location: San Jose, CA
Status: Offline
Reply With Quote
Feb 23, 2003, 02:27 PM
 
Originally posted by bjresta:
This solution seems to work fine without a router, but it fails when I have a router between my cable modem and Airport.

What other changes do I need to make because of the router?
Hang on, you're running a router AND a Airport Base Station?

You should check that only ONE of them is running NAT.

If your router is configured to handle NAT and port forwarding, you should change your base station so that it is in 'bridging' mode (turn off the 'distribute IP address' option (or whatever it's called) in the AirPort admin.

It sounds like your router has the real-world IP address and is using NAT and DHCP to assign addresses to internal hosts, including the base station. The base station takes this address and performs an additional NAT translation before passing it on to the DHCP clients that got their address from the base station.

That's overly complex and will lead to all kinds of issues when trying to debug network issues.

In general, either the base station or the router should perform NAT, but not both of them.
Gods don't kill people - people with Gods kill people.
     
   
Thread Tools
Forum Links
Forum Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On
Top
Privacy Policy
All times are GMT -5. The time now is 09:13 PM.
All contents of these forums © 1995-2011 MacNN. All rights reserved.
Branding + Design: www.gesamtbild.com
vBulletin v.3.8.7 © 2000-2011, Jelsoft Enterprises Ltd., Content Relevant URLs by vBSEO 3.3.2