Port Mapping with No DHCP??

Is there a way to setup AEBS to allow port mapping without enabling DHCP?? I would really like to enable DHCP on Mac OS X Tiger Server instead but I need to maintain port mapping capabilities in my AEBS. I'm currently running Apple Base Station V5.6 software on the AEBS.
Any ideas??

While a workaround has been described (in the user contributed answers area) to allow NAT to continue functioning on the AEBS while a separate device performs the function of a DHCP server, I haven't given any thought to what effect this would have on being able to use the port mapping function.
Since you are running Tiger server, don't you think it might make more sense to connect the server directly to the internet, use the server to perform the functions of both router and DHCP server for your network, and reduce the AEBS to the simple role of being a wireless network access point?

Similar Messages

Port mapping with source ip filtering?

did quite a bit of searching, and could find anything on the topic.
is there any way to restrict a port map to amspecific ip or subnet? basically getting access to basic firewall rules?
thanks in advance.

sorry for the typo... i meant to say that i could *not* find anything on the topic.

Port Mapping problem with a Snow Base Station

I wish to enable port mapping with my Airport Snow Base Station. (SBS) I am using an Earthlink Efficient Stream 5667 DSL modem to my SBS. I am running firmware version 4.0.9 and connecting with 10.4.3.
So -- enabling port mapping requires that the IP address on my 10.4.3 computer doesn't change, and that I then map the ports. However, I can not manually assign an IP (say 10.0.1.201) as my 10.4.3 can not connect using either "DHCP with manual address" or "manually" (where the router and subnet mask match the DHCP assignment)
What should I do?

Do not use the "DHCP with manual IP address" - that is a mode not supported by most networking devices on the market.
What you should do: on your Mac, open System Preferences->Network->Show Airport->TCP/IP tab. Select to "configure manually". Then enter the following parameters:
- IP address: 10.0.1.201
- subnet mask: 255.255.255.0
- router/gateway IP: 10.0.1.1
- DNS IP: use either 10.0.1.1, or enter the actual IP address(es) of your ISP's domain name servers

Port mapping question - I need clarification

I have posted a question about port mapping previously but - although I thought I understood - it is still not working for me. I was hoping there was a kind soul out there who could humor me and explain port mapping with AEBS 802.11n as if there where talking to a 5 year old.
Thanks for the help and it's ok to laugh.

{quote:}This address MUST be outside of the range of IP addresses that your 802.11n AirPort Extreme Base Station's (AEBS) DHCP service is providing.{quote}
This actually is incorrect.
The statement that the mapped internal address must be static is correct; otherwise the AEBS will not, if the Mac is assigned a different dynamic (DHCP) IP address by the AEBS some time in the future, be able to forward packets to the Mac. However it is very straightforward to have the Mac computer be assigned an address dynamically by the AEBS and to have the AEBS always assign the same IP address to the same Mac computer. Thereby giving the Mac a static address inside the DHCP range.
In the AirPort utility go to Internet | DHCP | DHCP Reservations. Click "+" then enter the MAC (what Apple calls Ethernet ID if you are using wired or AirPort ID if wireless) hardware address of the Mac computer, give it an IP address, save it. Then that Mac computer will always receive that (static) IP address from the AEBS.
Why do this? Well by continuing to use DHCP (while having though a static IP address) you keep all the other benefits of DHCP such as automatically having the gateway address, the DNS server addresses given to the Mac. Otherwise you have to enter all this information manually on the computer if you put it outside the DHCP address range. This is very desirable, especially for most home users, as their DNS server entries are provided by their ASP and picked up by the AEBS. If the ASP changes DNS addresses the manually configured Mac machine will not know.
So in summary - for port forwarding it is NOT necessary for the Mac machine to be outside the DHCP range, in fact _it is desirable to keep it in the DHCP range_ *as long as* the Mac utilises DHCP reservation on the AEBS.
I have tested this and it works fine.

Port Mapping Problem with AEX

I have a new Airport Extreme and a problem that did not exist with the Airport. I connect a Toshiba network camera to an Airport Express, set as a WDS remote, with the netcam connected to the wired ethernet port of the Express. I can see the netcam, which also functions as a web server, on the internal 10.x.x.x address, and have reserved a discrete 10.x.x.x address via the MAC/DHCP reservation function of the Extreme. Just like the older Airport which did this without a hiccup, I should be able to map a port (e.g. 1200) on the public IP to port 80 of the internal 10.x.x.x address, then access the netcam on the internal network from any browser (http://67.x.x.x:1200). My cable modem is just that: no router involved other than the Airport Extreme. I'm using the latest Extreme and Express firmware, and am either missing something with the new Leopard firewall, overlooking something else, or dealing with a product flaw. Any help is appreciated and Happy Holidays.

I have forwarded the port (have tried several different ports actually) in what I think it the correct way: using the Airport Utility, connected to the Airport Extreme, and, under advanced options, selected port mapping, entered the public TCP port of 1200, then the private 10.x.x.x IP address of the netcam (which I can access from the internal network with no problem), coupled with the private TCP port of 80. I then attempt to access the netcam from the Internet by entering http://my cable modem IP address:1200 (or another port to which I've attempted to map). This method worked for two years with the Airport, but, with the Extreme and Leopard (simultaneous transition), I'm stumped. After reading other about other port mapping problems, I reserved an IP address for the netcam based on its MAC with no positive results. I also set the firewall through the Security icon in System Preferences to allow all incoming connections. Thanks for taking the time to respond.

Need help with port mapping on Airport Utility 6.1

Ive been trying to port map on my TC with Airport Utility 6.1 and failing miserably. Port still closed. Can anyone advise where Im going wrong? Am trying to set up my home camera to be viewed outside.
I managed to key in the ports etc under Network and Port Settings. But nothing works. I'm tearing my hair out.
Any suggestions to try would be helpful.
Thanks

Use the 5.6 utility.. it is much easier and I think works better.. although you cannot load 5.6 directly into 10.8 the version for Lion actually works fine.
Download 5.6.
http://support.apple.com/kb/DL1482
Download unpkg
http://www.macupdate.com/app/mac/16357/unpkg
Open the AU 5.6 dmg and drag the pkg over the open unpkg.. it will create the directory on the desktop. You can either run it from there or drag the utility to your utilties directory.
Take screen shots of each step. Post them here.
That way we can tell you where it has gone wrong.
What port exactly does the camera need open?
How are you connecting remotely?
ie do you have a fixed public IP?? If not how are you getting IP?
Is the TC the only router in the network.. it is irrelevant unless the TC is the one and only router.

Port mapping not working with 7.5.1

I am having trouble getting Port mapping working with the new 7.5.1 firmware. Port mapping is not working. Port mapping was working fine before update, now all attempts to connect from WAN on ports are rejected. Tested with: telnet <wan-ip> <port>
I have removed and re-added all port mapping entries - no luck. Power cycled several times - no luck.
Other info:
I have an: Airport Extreme (Simultaneous Dual-Band II) running Version: 7.5.1.
It is setup to "Allow this network to be extended"
Network is being extended with an Airport Express with 802.11n running 7.4.2

yeah. I noticed the same thing. now the splash screen comes on without the flashing green squares and just hangs. i tried unintalling and then reinstalling and still no go. kind of annoying but they will probably come out with an update pretty soon

Is Time Capsule vulnarable with Upnp aka Port Mapping vulnerability?

As you also might have already heard about this quite huge upnp vulnerablity, I tried and failed to find out if Time Capsule or other Apple's network products are using this bugged libupnp library or not.
As a backup device it would be quite nasty if someone could hack in to the device and wipe all backups. US-CERT's list of manufacturers does not include Apple, so this is not helping much.
http://www.kb.cert.org/vuls/byvendor?searchview&query=FIELD+reference=922681&sea rchorder=4
So what to do, should we turn port mapping protocols off until Apple fixes this problem, or are we already safe with the Time Capsule's latest 7.6.1 version?

Apple do not use upnp.. they use their own entirely different protocol.. NAT-PMP so whatever the upnp vulnerability is, I doubt apple has it.

Port Mapping and DHCP...

Really sorry if this has been asked.. I feel kinda stupid actually but;
I have port mapping set up... working fine... all incoming traffic to my public IP goes to my iBook on 192.168.1.2
but now... the iBook's IP is 192.168.1.3 so I had to update the port mapping to suit this IP
Is there anyway I can make the Airport hand out 192.168.1.2 to the iBook everytime based on it's MAC address ? My old router used to be able to do this.

You should configure the iBook to use a manual IP address outside the range used by the AEBS's DHCP server. The default range used by the AEBS's DHCP server is x.y.z.2 to x.y.z.200. So you would want to configure your iBook to use a manual IP address of 192.168.1.202 (for example).
Configure the port mapping to map to that address.

HT1552 Im setting up a server with the port 25565 and im doing it with Port Map but the problwem is i cant seem to get it to work with my router. it goes through my macmini to the router and the expansion hardrive

Im setting up a server with the port 25565 and im doing it with Port Map but the problwem is i cant seem to get it to work with my router. it goes through my macmini to the router and the expansion hardrive

Im setting up a server with the port 25565 and im doing it with Port Map but the problwem is i cant seem to get it to work with my router. it goes through my macmini to the router and the expansion hardrive

Linksys App bug with port mapping

So I have the Linksys app installed on my Android phone. My router, WRT1900AC, is set up using port mapping. The port mapping is for an ssh app to control my 3 web servers. Each servers internal port is 22 and each servers external port is 20, 22, and 23 each one mapped to port 22. When signed in the the routher itself, not through the app, I can configuer these ports fine. However when I attempt to configuer these ports or the ip appress through the app, I get an error saying the port is in use. It seems the app is seeing the three servers using the same internal port and throwing an error.
Has anyone else experienced this?

I recommend you not use ports in the first 1000 unless they are for the standard server they are specified for. This is a good IT policy.
Example:
Port 22 External to internal IP Address of SSH server port
Port 21 External to internal IP Address of FTP server port
Instead use undefined ports in the higher end of the range.
Example:
Port 10001 External to internal IP Address of SSH server port
Port 10002 External to internal IP Address of SSH server port
The Linksys stock firmware will only do DNS proxing which isn't great for server networks.
For this application I recommend OpenWRT McWRT v1.0.5:
https://github.com/Chadster766/McWRT/releases
Install luci-ssl to enable SSL access and open router port 443 for standard secure remote access.
FYI:
Unless you have a USB to TTL cable for firmware recovery I recommend always flashing OpenWRT using the Linksys stock UI. This will put the Linksys stock firmware into the alternate boot image in case manual recovery is needed.
Do not delete the LAN, WAN and WAN6 interfaces. Pay attention to OpenWRT notices that say things are not reversible. OpenWRT can be unforgiving in those circumstances. If you have the $9.00 USB to TTL cable it won't matter because you can always load firmware through the boot loader.
OpenWRT McWRT has some issues:
https://github.com/Chadster766/McWRT/issues
Please remember to Kudo those that help you.
Linksys
Communities Technical Support

Time Capsule: Port Forwarding Issue and DHCP with Westell 6100g Modem

Ok two issues as of right now, but more down the road i think... Anyways, number one, i would like to be able to backup my computer using time machine and my time capsule.. Right now it works properly when inside the local network, was wondering if there was a way to backup when outside the network... i travel a lot and always have my macbook pro with me.. Also, i have a USB hard drive connected to the usb port on back of time capsule but its not showing up anywhere... is that only for printers??? that's not such a big deal, but would be nice to have access to that hard drive from multiple computers... OK so part two of my issues is, i have a WESTELL 6100g modem for DSL verizon service, which is crappy, but that's besides the point, it is a modem/router, so i have the time capsule connected directly to that westell.. the westell only has one Ethernet port, so that's wired to time capsule and then my computers are connected wirelessly and wired through the capsule. It seems that the westell is distributing the IP's and is controlling the port forwarding and what not.. I have tried a few things to give control to the time capsule but that didnt work.. i followed these directions on the web page http://www.dslreports.com/faq/vz/4._Hardware#13600 but it didnt work properly, i couldn't log onto the web at all.. Maybe im doing something wrong.... Anyways, what i really want to do is control everything that the westell is controlling right now with the time capsule... i want to give out IP's and also control port forwarding with the capsule.. Any way of getting that accomplished would be AWESOME... I'm somewhat intelligent when it comes to computers so i should understand everything you are talking about... please help!!!

wattabing wrote:
Ok two issues as of right now, but more down the road i think... Anyways, number one, i would like to be able to backup my computer using time machine and my time capsule.. Right now it works properly when inside the local network, was wondering if there was a way to backup when outside the network... i travel a lot and always have my macbook pro with me.
If you have Back to my Mac (available online service from Apple's MobileMe), then you can perform the following actions with your Time Capsule remotely,
1. Remote disk access to both the Time Capsule disk and a compatible disk connected via the Time Capsule's USB ports.
2. Remote configuration.
Also, i have a USB hard drive connected to the usb port on back of time capsule but its not showing up anywhere... is that only for printers???
Printer, hub, or compatible disk.
http://support.apple.com/kb/HT2421
Anyway, it could be a setup issue for you, assuming you have Back to my Mac (MobileMe) then the procedure for Time Capsule services is shown in the following Apple support kb
http://support.apple.com/kb/HT3486
and for USB disk please see the following Apple support kb
http://support.apple.com/kb/ht2426

How do I use Port Mapping?

b How do I use Port Mapping?
(This document will assume that you are using and ABS/AEBS/AX as an internet router and have DHCP & NAT turned on.)
Sometime you may want to offer access to a computer on your AirPort network to users on the internet, whether it be a web site, or for file sharing, or just remote access for yourself when traveling. If any of these sound like something you want to do, then you need to understand how Port Mapping works.
b AirPort as Firewall
Most of the time your AirPort base station will not let any traffic into your network which did not originate from your network. It will let everything out and replies to your traffic back in, but it will not let sessions initiated on the internet side of the base station in to your network. This is what is referred to as the "NAT firewall" capability of the base station and it provides effective protection for your network from the internet. What Port Mapping does is poke a hole in this wall to allow certain type(s) of traffic into the network and direct this traffic to a specific computer on the network. In the firewall world this is commonly referred to as an "inbound proxy" or "inbound translation" rule or "PAT" (Port Address Translation) in the router world.
b The Need for Manual Addressing
Since a Port Mapping entry in the base station configuration requires an inside private IP address to be specified, the computer to which to mapping entry applies should always have the IP address specified in the mapping entry. Thus, DHCP should not be used for a computer offering services on the internet as the Port Mapping entry will no longer work if the target computer's IP address changes. In general, an Apple base station's DHCP server will try to assign IP addresses in the 10.0.1.2 to 10.0.1.200 range. IP addresses above 10.0.1.200 can be Manually assigned to computers and other devices on the network up to 10.0.1.254. 10.0.1.255 is reserved (it is the broadcast address for the 10.0.1 subnet). To Manually set up the TCP/IP information for a Macintosh running Mac OS X, go to System Preferences -> Network and "Show" the appropriate interface (Ethernet or AirPort) and click on the TCP/IP tab. Select "Configure Manually" and enter the following information:
IP address : 10.0.1.201 (or whatever address you decide to use)
Subnet mask : 255.255.255.0
Router IP : 10.0.1.1 (the AirPort base station LAN IP)
DNS server : 10.0.1.1, or whatever DNS server IP your ISP uses
After making these changes verify that your computer can still access the internet and local resources on the LAN before continuing.
b Port Mapping a service
In our example we will be hosting a web site on a computer which we have given an IP address of 10.0.1.201. Basic web sites are accessed using the HyperText Transport Protocol (HTTP) and this protocol typically uses port 80 to communicate. In order for others to see the web site, we must configure a Port Mapping entry in the base station configuration to not only allow the web browsers in, but to tell the base station what IP address the web server is using. The Port Mapping entry has three parts: Public Port, Private IP, and Private Port. In this case you would use the following values:
Public Port : 80
Private IP : 10.0.1.201 (this is the computer hosting the web site)
Private Port : 80
In order to access the web site from the internet, users must reference the base station's WAN port public IP (determined by looking at the base station configuration summary page in the AirPort Admin Utility). Since this address may change over time, you might want to use a Dynamic DNS service to simplify connecting for your users.
Sometimes the port you wish to use may be blocked by the ISP. In this case, use a different non-standard Public Port number for the service, but keep the Private Port standard. In the above example, if the ISP was blocking port 80, you could potentially use 8080 instead, so:
Public Port :

Public Port : 8080
Private IP : 10.0.1.201
Private Port : 80
Your users would then have to enter "http://<publicIP>:8080/" (where <publicIP> is the public IP address of the AirPort base station) to access the web site.
b Internal Access
It should be noted that when accessing these services from within the network you cannot reference the Public IP/Public Port, but rather you must use the Private IP/Private Port. Thus, "http://10.0.1.201:80/" in the above example.
b Limits and Options
There is a maximum of 20 Port Mapping entries that can be made in an Apple base station configuration. If you use an AirPort Extreme or AirPort Express base station there is an option which can be helpful in the case where you need many ports opened to a single computer. This is the "Default Host" option. When using this it is not necessary to use Port Mapping at all as all ports will be opened to the specified "Default Host". This is found in "Base Station Options". The default IP address for the "Default Host" is 10.0.1.253. You may change this IP address. The target computer must be Manually configured as specified above with the same IP address. Since all ports are now open to this computer, you should enable and configure the Mac OS X firewall on the default host computer to protect it from intruders.
b Useful Related Links
<a href="http://docs.info.apple.com/article.html?artnum=52002>"Designing AirPort Extreme Networks: Manuals</a>
"Well Known" TCP and UDP Ports Used By Apple Software Products
IANA Port Number Assignments

AEBS Gigabit 802.11n FW 7.2.1 - OS X 10.5.1 Port Mapping HELP!!!!

Hi
I have a AEBS with Gigabit Ethernet upgraded to Firmware 7.2.1. I am running OS X Leopard 10.5.1 and I am unable to successfully forward ports. Every time I query a port that I believe to have mapped successfully it appears closed using canyouseeme.org.
I have followed numerous instructions, but they all seem to be instructions for Tiger, I'm wondering if a setting has been missed. I have successfully assigned a static IP address to my machine but still the port appears to be closed. I do run the Leopard firewall using specific applications option (the third one), but I have also tried it with the firewall off and it still hasn't changed anything, the ports are always closed.
So now I'm pretty much stumped. Has any one actually managed to get a setup similar to mine working, with the ports being open? All advice appreciated.
Thanks
Message was edited by: dalyboy

Hello dalyboy. Welcome to the Apple Discussions!
Try the following to see if it will help ...
To setup port mapping on an 802.11n AirPort Extreme Base Station (AEBSn), either connect to the AEBSn's wireless network or temporarily connect directly, using an Ethernet cable, to one of the LAN port of the AEBSn, and then use the AirPort Utility, in Manual Setup, to make these settings:
1. Reserve a DHCP-provided IP address for the host device.
Internet > DHCP tab
o On the DHCP tab, click the "+" (Add) button to enter DHCP Reservations.
o Description: <enter the desired description of the host device>
o Reserve address by: MAC Address
o Click Continue.
o MAC Address: <enter the MAC (what Apple calls Ethernet ID if you are using wired or AirPort ID if wireless) hardware address of the host computer>
o IPv4 Address: <enter the desired IP address>
o Click Done.
2. Setup Port Mapping on the AEBSn.
Advanced > Port Mapping tab
o Click the "+" (Add) button
o Service: <choose the appropriate service from the Service pop-up menu>
o Public UDP Port(s): <enter the appropriate UDP port values>
o Public TCP Port(s): <enter the appropriate TCP port values>
o Private IP Address: <enter the IP address of the host server>
o Private UDP Port(s): <enter the same as Public UDP Ports or your choice>
o Private TCP Port(s): <enter the same as Public TCP Ports or your choice>
o Click "Continue"
(ref: "Well Known" TCP and UDP ports used by Apple software products)

NAT configuration and Port Mapping for xBox

I'm looking for help with port mapping to open up the NAT for an xBox One. I'm working with the following network devices:
xBox One
DSL Modem: Embarq (ZyXEL) 660R series
Airport Extreme version 7.7.3
I understand the following from researching the issue:
The default settings for both devices block the ports needed for xBox Live.
Airport Extremes are not on the compatible list for xBox.
Port Mapping is better then creating a DMZ for the xBox.
The xBox needs its own manually set IP address.
I switched my Network>Router Mode from Off (Bridge Mode) to DHCP and NAT. I then created a DHCP Reservation and the Port Settings for that IP.
After doing this, the Airport would restart and display a warning - Double NAT. I figured this was because the 660 settings showed the NAT Mode to be SUA Only. The Edit Details link displayed an empty table where you edited the SUA/NAT Server Set. I switched from NAT Mode>SUA Only to None. So there was my Double NAT and I would have thought that would have removed one.
I also disabled the Firewall and Enabled the UPnP.
After restarts the Airport continued to display the Double NAT error. However, with the 660's NAT Mode set to None, the Internet was not there. Web browsers and email accounts replied with server not found.
Only with the 660 set to SUA Only and the Airport in Bridge Mode is the Internet accessible. I now have the details for the SUA filled out for the xBox's IP address and ports.
Hypothesis
Since both devices are acting as DHCP servers the port mapping is not working. Rather then have the 660 distribute IP addresses and then having the Airport distribute another range of numbers, I need to have both devices bridge and distribute one range of numbers. Currently the 660 is using the 192.168 range and the Airport is using the 10.0 range.
Am I correct? Any thoughts and suggestions are welcome.

Port forwarding through a double NAT.. is near impossible.. !!
And the xbox is so attuned to using UPNP it is very hard not to.. even port mapping is not a great fix. Since apple decided gamers did not count as users for Airports.. I think honestly it is best to bypass the airport and stick to upnp from the modem router.
What method of authentication does your ISP use? Because it is really better to use one router.
And in fact the router should be the Zyxel. If you plug the Xbox to the Zyxel running in full router mode, with the airport removed from the network does it work and open NAT??
If not replace the Zyxel with a modern listed router that is xbox compatible and bridge the airport to it.

Port Mapping with No DHCP??

Similar Messages

Maybe you are looking for