Currently Being ModeratedDec 15, 2012 2:54 PM (in response to davidmenges)
I've proven to myself that this is an Airport Express bug:
- I configured my Airport Express as above, then exported the configuration and looked at it (it's XML). The port forwarding information is missing.
- Then I configured my Airport Express using a predefined Description (Personal Web Sharing), exported the configuration and looked at it again. The port forwarding information is present.
- I even did #2 and changed the port number from 80 to my port numbers. That also worked.
I'm not out of the woods yet, because also saved in the configuration file is a "serviceType", set to "_http.tcp". I have to figure out what to set this to...
Currently Being ModeratedDec 15, 2012 7:25 PM (in response to davidmenges)
Hi - see this post which includes tips from forum guru Tesserax - https://discussions.apple.com/message/17117646#17117646
Your problem could be that you are entering the name in the Description box before you enter the port numbers - try leaving the name blank - as you enter the ports, the name field will change to custom - you can then fill it in
Currently Being ModeratedDec 16, 2012 2:44 PM (in response to CRMDVM)
Thanks for the suggestion, but it didn't help. The name field did not change to "Custom", and the results were the same as before. The local Genius Bar suggested calling Apple support, which I'll do in the morning.
Currently Being ModeratedDec 17, 2012 3:27 PM (in response to davidmenges)
I called Apple, described the problem, was passed to "the expert", and I can't believe what he told me:
Me: ... and I exported the config and my custom port forwarding wasn't there.
Expert: That's because it's custom - it won't appear in the config file.
Me: Even though the Airport Utility GUI allows setting custom port forwarding?
Expert: Look, if it doesn't work, it doesn't work, and if it doesn't work Apple doesn't support it. The Airport Express is a very simple device; it doesn't support everything.
I suspect his first comment, about the config file, is BS. I can accept his last comment, about the Express being a simple device, but sheesh, what a way to present it...
I need port forwarding, so I guess I'm returning the Express, a shame: it was otherwise super-slick to install.
Currently Being ModeratedDec 20, 2012 10:23 AM (in response to davidmenges)
It's finally working! I changed quite a few things, including getting a different cable modem from Comcast (a Cisco - and apparently all but one Comcast device do NOT include routers), but what made the difference is reading an Apple wireless manual (http://manuals.info.apple.com/en/Designing_AirPort_Networks_10.5-Windows.pdf). Following its (subtle) advice, I:
- Changed the Airport's DHCP range to 10.0.1.2 to 10.0.1.200.
- Moved my Unix box's IP back to 10.0.1.202 (a printer has 10.0.1.201), and removed the DHCP reservation for it.
- Made related changes on my Unix box and Mac (/etc/hosts, etc.) using Webmin, etc.
- Created my "custom" port forwarding by using "Personal Web Service", changing the ports to 4280 and 4282.
From the beginning I didn't know if my Unix box's IP should be inside the DHCP range with a DHCP reservation, or outside it without one. Now it is clear that the latter is correct - I should have gone with my gut feeling. Why it makes such a difference, I don't know, and I don't know if the .200 cutoff for DHCP is an Apple convention or part of a standard.
Currently Being ModeratedDec 20, 2012 5:20 PM (in response to davidmenges)
Thanks for the update - I am glad you were able to get it working - the 2-200 range is an Apple default - the standard is an upper limit of 254 - you could use the AU to set it at 2-254 if you wanted to.
Currently Being ModeratedDec 22, 2012 5:21 PM (in response to davidmenges)
It briefly worked, and now it doesn't again - including a simple SSH port forward. I had an expert look at it, and he couldn't find anything wrong with my efforts. Meanwhile, I searched for "port forward stick" in all of Apple's forums (not just Airport's) and found several reports of port numbers not sticking - on Expresses and Extremes.
At this point I believe Airports have more than one blatant bugs, and I need to see if I can return mine...
Currently Being ModeratedDec 26, 2012 12:39 PM (in response to davidmenges)
I can't return them (14 day return policy), so I've decide to turn off the router functions of both my Airport Expresses (I have two to cover our house), use them just for wireless, and buy this wired router to provide routing:
It gets good reviews and is dirt cheap (also comes in an 8 port model for just a few dollars more, and is available from Newegg too).
Maybe some day Apple will fix the bugs and I won't need this separate router.
In case it wasn't obvious in my previous postings, I contend that the new Airport Express (and probably the Extreme) not only mishandles custom port forwarding, but doesn't handle port forwarding correctly AT ALL. Apparently some of you have succeeded, but after many hours of trying everything, including hard resets, I've gotten nowhere. Even the predefined port forwarding choices, like SSH, don't work (for me).
Currently Being ModeratedJan 13, 2013 7:12 PM (in response to davidmenges)
- Custom port forwarding on Airports doesn't work - the port numbers don't "stick" if you type in a custom name. If you select a predefined protocol and then change the port numbers, it may work.
- Port forwarding may - probably does - work in all other respects.
When I installed the wired router, as described above, port forwarding still didn't work. Long story short, I had to clean up routing issues on my Ubuntu box, the target of my port forwarding. The routing information on it was garbled with remnants of 10.0.x.x addresses (the new router defaults to 192.168.0.x addresses), and I'm not so sure Webmin configures Ubuntu networking correctly.
I'm not about to spend more time removing my new router to see if my Airport can handle port forwarding, but I do apologize to you and to Apple for misleading statements above.
Currently Being ModeratedFeb 2, 2013 7:37 PM (in response to davidmenges)
I had this same problem and was able to get it to work with the following steps:
- In the "Network" tab, click the "Network Options..." button
- Uncheck "Enable NAT Port Mapping Protocol"
- Add your port mapping, making sure to fill out ALL fields
- Verify that the port mapping settings were persisted properly
- Go back into Network > Network Options... and re-check Enable NAT Port Mapping Protocol
Hope that helps.