Hi.
When connecting a wireless device to a Capsman AP, its state is first "connected, no internet" and after several seconds it switches to "connected" (with internet).

Is there an advanced Config setting, how i can decrease the time from those two states? On normal APs, this is much faster.
I see no difference in "local forwarding" or not.

Any sugestions and ideas regarding CAPSMAN and advanced tweaks as welcome

thank you, regards,

Joe

My guess is the "connected, no internet" state means that the client hasn't received a DHCP lease yet. Where is your DHCP server? To test this hypothesis you should monitor DHCP traffic.
Does the client appear in registration table instantly?

Thanks for your message. No, "reciving IP" is an state of its own.
I think this has something to do with rstp or anything like that... but changing the bridge doesn't show improvement.

Client devices shouldn't react to BPDUs at all. I can't see how RSTP could cause this. You can turn (R)STP off for testing if you are not using meshing and you don't have wired loops in your network.
You should find out what does the device test to see whether it is connected to the Internet or not. Does it call home? Where? What protocol? Is there a firewall or proxy in the way?

I also think it has something to do with DHCP. That takes some time. But If you change the DHCP lease time from the default value of 10 minutes to 2 days or something like that, the next connect is really fast. After 2 days it has to handle again with the DHCP server and this takes some seconds but then for 2 days the next connects will be much faster. If the reconnect is not fast enough you could increase the "group key update" intervall which should improve re-connecting performance if the group key has not changed.

The second effect is that your device is not disconnecting so fast if it is not used.