Can't extend Guest Network in roaming mode

Sorry, typo mistake.

DHCP Range should read 10.0.1.2 to 10.0.1.200.

There is part of the problem.

The "guest" network has to be on a different subnet than the "main" network.

Apple's defaults are 10.0.1.2 to 10.0.1.200 for the main network and 172.16.42.2 to 172.16.42.200. This is what I am using for the "test" and everything works perfectly.

So, once again, I am suggesting that you start simple first, and use Apple's default settings, and get things working that way.

Then.....you can start to change things around if you want to see if the changes will still allow things to work.

However....if you want to try to introduce custom settings first.....then I don't think that I will be able to help you much at all.

Before you spend a lot of time on this.......I need to let you know that I have only tested this with a "main" AirPort and an "extending" AirPort.

I do not know if multiple "extending" AirPorts will work, because I have not tested that.

OK, thanks. I am going to try to locate another AirPort so that I can test with one "main" and two "extending" AirPorts....both connected to the "main" AirPort by Ethernet.

Update.......two extenders works perfectly when I test here using Apple's default settings. Devices can connect to the main or guest networks on all AirPorts and get a good Internet connection.

The "main" network is named TWND and the "guest" network is simply named Guests.

Both of the extenders, an AirPort Express and a 3rd Gen AirPort Extreme, connect back to the "main" AirPort Extreme using Ethernet cable connections.

I'm sorry, but I cannot explain why this works perfectly for me, but not for you.

Hopefully, another user will be able to help.

Thanks.......Good Luck!

leonidchursin wrote:

Hi, Bob. Almost for 2 days tried agreed configuration together with other possible variants, but unfortunately had no success. No guest network for ethernet. Only for wireless bridging.

I am not at all sure it is worth wasting more time..

But to get to the bottom of the issue.. I think you need to look deeper into your network. vlans get tricky. I have run into issues before where a vlan is already allocated and hence getting a guest network to run turned out to be impossible..

I would set this up in total isolation to the existing network.. ensure it works with the current hardware.. it should.. but you want to be double sure otherwise you are wasting your time.

Then put it back into the main network with a simple connection.. even using double NAT to start with.. if it immediately fails, the second vlan has been allocated somewhere else.. or a switch etc is not compatible with running multiple vlans.

If it works.. put more of it back into the network.. avoid switches and other complexities.. keep as much of it tied together with simple direct cables as you can.

Certainly if you use a managed switch check the vlan setup. Depending on the management software you might be blocking vlan or it might be routing incorrectly.

I've a problem with extending an Extreme network with an Express:

airport express extending extreme network causes printer access problem

Basically the pair are not entirely "transparent". Hardware:

Extreme: MC340LL, A1354; 4th generation

Express: MC414LL/A, A1392; current generation

But a reasonable solution for me would be to simply extend the Guest network with the Express, it's only used to get coverage into the bedroom for iPads and I don't mind changing the network source.

I did try this but it fails, the recent airport utility doesn't offer the Guest network as a candidate for extending during configuration even tho the hardware and firmware are recent enough.

Could it be that I just need to do as Bob suggests: factory reset of the Extreme (and Express)? Any particular Extreme settings I need to set like "extendable"? Seems a bit odd but I'm ok with it if it works. Has it worked for others of us?

BTW: I've also tried giving the Express its own SSID but that apparently is not possible either. And just getting the Express transparently extending the Extreme, non-Guest, SSID doesn't work for the printer for some obscure reason. Sigh!