[X4U] Airport Express

[Bill Fox]

In the case of a wired internet connection when on travel I always use my MacBook Air to share the internet connection via WiFi with my other devices. This method actually creates a new network but produces no double-NAT errors.

However, in my apartment, I have AT&T Uverse internet (and phone and TV) which is basically high speed DSL with a slow b/g WiFi access point that barely feeds three HD TVs. I need an AirPort network using faster "n" WiFi for the computers, iPhones, iPads and security devices. I cannot get any of my three Airport devices (Time Capsule, Airport Extreme or AirPort Express) to be the primary wired internet connection in Bridge Mode--no internet is the result just like your experience. When I had Cox Cable, I used Bridge Mode with no problem. With AT&T I have to set the AirPort device (I use the Time Capsule) connected to the DSL "modem" to "Create a wireless network " in order to get wireless internet through it--no double-NAT errors, though. The other two devices are set up in Bridge Mode around the apartment as wireless "n" repeaters off the Time Capsule.

I do not know why this problem exists and neither do the AT&T techs. This may not be much help to you but it may give a better expert a hint. Maybe certain DSL modem/routers have an issue with AirPorts.

Bill

On Jul 30, 2013, at 2:31 PM, David Ledger <david.ledger at ivdcs.co.uk> wrote:

> On holiday recently we were in an apartment that has a free wired Internet connection. Because it's on a small island traffic is expensive and there are some things are filtered to try to keep the traffic down.
> 
> I wanted my wife's iPhone, my SIMless iPhone and my HP mini NetBook to be able to use the connection so I took my Airport Express with me. Before going I set it up in Bridge Mode, but when I arrived I could make a connection *to* it but not connect to the Internet *through* it. The Windows 7 in the NetBook acknowledged it was 'Connected' but had 'No Internet access'. This may be due to those local restrictions, but I don't know Windows well enough to be sure what that message really means. Any further information on why I should not be able to connect through an Airport Express would be welcome.
> 
> I then re-configured the Airport Express using the Windows version of the Utility. By setting it to create a new network I could make it work as required, but I kept getting errors from the Airport Utility complaining of double NAT. The error meant that the Utility would not save the configuration file so I left it like that for the duration. Before leaving I allowed Airport Utility to 'fix' the problem. It did so by setting the Airport Express to Bridge Mode, which, as before, didn't work.
> 
> Any thoughts would be welcome.
> 
> Also, why is double NAT seen to be a problem? I've worked in a financial institution where to implement the required security some routes were NATed at least six times.
> 
> I've been running and involved with industrial networks since 1984 so I do understand how things *can* work if allowed to.
> 
> David
> 
> 
> -- 
> David Ledger - Freelance Unix Sysadmin in the UK.
> david.ledger at ivdcs.co.uk
> www.ivdcs.co.uk
> _______________________________________________
> X4U mailing list
> X4U at listserver.themacintoshguy.com
> http://listserver.themacintoshguy.com/mailman/listinfo/x4u