@MR.S 

In fact, I don't understand...

If it isn't a bug. It's something on my side for sure, but I cannot get what it is...

My physical connection is:

ER605 -- SG3428X (Port 1)

                     |                        |                           |

         EAP653 (Port 2)     OC300 (Port 3)     EAP653 (Port 23)

I have other things connected for the wired part, but this is sufficient for the wireless description, I guess.

Port 1, 2, 23 are set to Profile ALL.

Port 3 is set to Profile System.

The ACL in Switch and EAP don't limit System network at all, so Casa network can see System network.

I'm really puzzled.

Thank you,

Fra

  @nicolati 

your setup seems correct so there can't be much wrong. try to put vlan2 on one of the swtich ports and connect a pc with a cable to this port, do you get ip then?

  @nicolati 

and when we try to fix this, disable ACL on everything, when everything work enable again.

  @MR.S 

I have already a PC connected to Port 22, which is the only Ethernet port with Profile Casa, and it gets the IP from the correct DHCP range. It's 192.168.10.2, precisely.

I have some advanced 802.11 features enabled for wireless, like fast switching between APs and Mesh disabled, because the 2 APs are connected by LAN.

Can this influence the thing?

Thank you,

Fra

  @nicolati 

No this settings have nothing with vlan. try disable acl on EAP and Switch to be sure that this not make truble.

and if this dont work we have to start from the begining again..

  @MR.S 

Ok, done, I don't think ACL plays a role, but I disabled them anyway and put VLAN 2 on my WLAN.

The situation is this one:

The clients with an IP on subnet 10 are ok. There others are not. Or because they maintain an IP under the main VLAN (the 0 subnet) either because they don't have an IP at all.

Pay attention to the MBP: it says it has an IP under 0 subnet, but the mac says no IP given from DHCP...

So, the situation is even more weird, since some clients are ok and other are not.

The 2 Samsungs are TVs.

Thank you,

Fra

  @nicolati 

I have a smaal lab with a EAP653 on.. 

and I have made a 1-2-3 step by step config for vlan2

1

2

3 portprofile all on access point and switch port connection.

and thats it

  @nicolati 

how do you get different ip on same ssid? do you use ppsk?

  @MR.S 

You said '3 portprofile all on access point and switch port connection.'

But I set Profile ALL only on EAP ports on the switch. Did you set Management VLAN on the EAP ? I didn't.

Apart this detail, the rest of the config is the same as yours.

Then, I have installed other 3 WLANs to make some experiments, but they are not the one used here:

1) One WLAN dedicated to IoT, but configured in the same way. The only difference is that it uses VLAN 6

2) One WLAN for Public, which uses VLAN 5, same config

3) One WLAN based on RADIUS. The RADIUS server is the one built in inside the OC300 and the RADIUS profile is the default, where I added 2 MAC addresses, in order to use them as MAC Address Authentication method, since the RADIUS WLAN has no password

All these ones are tests and not used so far.

So, they should not be the culprit.

Regarding the different IPs, that's the weird part. I don't understand why this is happening...

I have now turned on my printer to get an additional device and it gets 169.254.22.221 !!! :D

Thank you,

Fra

  @nicolati 

sorry I didn't see that the MBP is ok. I have problems with my eyes and will have surgery on both eyes on Wednesday (true) :-) so I hope I look better after that.. 

any how. 

I use vlan1 to all my switch and EAP no management vlan.

then i use switch port profile all on switch port to this device

router

eap

and other swtich

so link to router profile all

link to eap profile all

link to other switch profile all

then it should work..

how is your layout? can you take a picture with link label on