How to efficiently organize network rebuilding on vlan?

Question

Network administration

I want to divide the network into vlans, but when an unmanaged switch (sw2) is connected to a managed switch (sw1), it will not be possible to distribute devices connected to this sw2 itself by vlans. Is there nothing that can be done here? What if I assign trunk port to which sw2 is connected? Then I will need network cards that can tag 802.1q (you can buy them, but what about IP phones?).
It seems like a subnet-based vlan can help (although it still doesn’t exist on my d-links), but it’s also not clear: can the switch determine the port to a specific vlan by looking at the IP address of the network from which the frame came? How long? And the next packet will come from another network, and what will happen?
And what is the most efficient way to make a MAC-based vlan? It's necessary to collect all-all poppy addresses from all devices (computers, servers, IP phones).

Answer 1

I want to divide the network into vlans, but when an unmanaged switch (sw2) is connected to a managed switch (sw1), it will not be possible to distribute devices connected to this sw2 itself by vlans. Is there nothing that can be done here?

For some unmanaged switches on certain chipsets, there is a similar solution: link . I think there is no need to explain that this is difficult to maintain and this should not be allowed into the industrial network.

And what is the most efficient way to make a MAC-based vlan?

I think it's best not to. This scheme also appears to be difficult to scale and difficult to maintain.
If I were you, I would use L3 switches (or a Linux/*BSD server as a router) and managed L2 switches.

Answer 2

I want to divide the network into vlans,

What for?
Formulate what you want to get from this, how much money and time you are willing to spend.