Port Forwarding Non-Preconfigured Ports on Airport Extreme

Question

Level 1

0 points

Port Forwarding Non-Preconfigured Ports on Airport Extreme

1. Opened up Airport Utility.
2. Under Internet/DHCP, reserved a static IP - 172.16.1.201 for a VoIP unit that is wired to one of the AEBS ports.
2. Under Internet/NAT, checked "Enable NAT Port Mapping Protocol" then clicked on "Configure Port Mappings..." button (which transfers me to Advanced/Port Mapping).
3. Added a pre-configured "Personal Web Sharing" port (80) to 172.16.1.201.
4. Updated and restarted AEBS.
5. Using http://www.canyouseeme.org/ as well as opening a browser referencing my global IP:80, I was able to verify that port 80 is indeed open.
6. Went back to step #3 and added a non-pre-configured port going to the same private address 172.16.1.201. Port is UDP 5060 for SIP.
7. Updated and restarted AEBS.
8. Verified port 80 is still open, but 5060 is not.

Is there anything wrong with my setup? Any help / advise would be GREATLY appreciated!

Thanks!

iMac G4, Mac OS X (10.4.3)

Posted on May 27, 2010 1:04 PM

Reply

Answer 1

ize_man_74 Author

Level 1

0 points

May 29, 2010 9:53 AM in response to ize_man_74

Ok, I still have not opened up port 5060, but I was able to resolve the issue behind it (i.e. enabling SIP for my SPA-3000). For anyone having the same problems I had, these are the things I did:
1. Reserved a static IP (e.g. 172.16.1.201) outside the DHCP pool via MAC address. Although this step is optional, this would prevent you from always having to update the IP on #2 everytime the unit gets assigned to a different IP.
2. Checked box 'Enable default host at: 172.16.1.201.

Reply

Answer 2

Jun 11, 2010 8:03 PM in response to ize_man_74

This is the exact same problem I'm having. Strangely, some of my non-standard ports are being forwarded just fine.

Specifically, I need to forward ports to enable ftp clients to browse in passive mode. In order to do this they must be able to communicate with the ftp server on ports other than 21, with each client receiving its own additional port. I've been using the range 3000-3008 for this purpose and until recently it seemed to be working, but now all probe scans report closed, regardless of what port range I use them for.

I mention ftp because I know the Airport Extreme discriminates between certain types of traffic and handles them according to whatever programming they stick in there. I don't know how the Airport Extreme router could be discriminating between the different ports I'm reassigning and forwarding, but I know it's causing them to become closed. In a range previously undefined in the port forwarding, probe scans report "stealth". After forwarding, the probes report "closed".

Can anyone tell me what's going on here?

Enabling default host is not an option (and it shouldn't need to be). I have reasons for not wanting to let all ranges of ports automatically be forwarded to this computer.

Reply