Ugh. I don't know why my luck with Wireless N routers is so bad, but man, it is. My latest let down is Apple's Airport Extreme (Gigabit version). The setup was clean and slick as one would expect from Apple, but after many hours of configuring, reconfiguring, resetting, rebooting, and googling, I was getting pissed. It seems as though the AEBS cannot and will not forward UDP packets (most notably of which, DNS (Port 53 UDP) packets). While this is not a problem for 99.8% of the world, those of us that run our own internal DNS server are fucked. I've been a professional IT / Network / Programmer guy for a number of years and no matter what I tried, this thing was not budging. Most home networks use their ISP's DNS servers, but I have an internal DNS server that I need to use in order to use my home-hosted domains. So if you need to port forward *any* UDP ports from your router to a local computer, the Airport Extreme is not the router for you.
Airport Not-So-Extreme
Posted by Matt
on September 18, 2007
That being said, I finally gave up and am now using the AEBS in bridge mode along with my old WRT54G serving as the front-line router, handling port forwarding. I'll post more in the days to come to illustrate the outcome.
Trackbacks
Use this link to trackback from your own site.
