How can I use the Option 82 IP assignment with this configuration?
Is a routing/firewall rule at the RV320 a solution (to forward DHCP requests from subnet specific IP - eg 192.168.3.1 - to exactly one IP, eg 192.168.1.1)?
RV320, configured as a DHCP server with IP 192.168.1.1, can provide IP addresses only in this subnet range 192.168.1.0/24. The same is for the configuration of Option 82
If you are thinking to configure VLANs on the switch and all VLANs to have the same DHCP server 192.168.1.1, this means that all users will receive an IP from that subnet - 192.168.1.0/24.
If you want to use different subnet ranges (192.168.2.0/24; 192.168.3.0/24) for the different VLANs you should be able to configure different DHCP servers IPs on the switch.
I want to ensure, that each client on each switch port gets a specific IP address. That is what DHCP Option 82 was invented for: http://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3550/software/release/12-1_13_ea1/configuration/guide/3550scg/swdhcp82.html#wp1058138
Two steps should be necessary:
How can I achieve that? This should be the "standard" case of option 82.
Do you have a trunk port or access port configured between the switch and router? A trunk port should carry traffic for all VLANs so DHCP Relay is not necessary.
both is possible in switch configuration. Should the uplink port from switch to router be "trunk" or "no trunk" to achieve the needed configuration? If I understand you right, I should bring the uplink port of the switch into "no trunk" mode, so that DHCP relay functionality and therefore DHCP option 82 is working. Am I right?
The port that connects the switch to the router should be a trunk. Include VLAN 1 Untagged, all other VLANs Tagged.
Create the exact same VLANs on the RV320 and got to Port Management-> VLAN Membership. In the table, change it to match the above settings. Now when a device connected to VLAN 2 on the switch sends a DHCP request, it will pass through the trunk to the RV320 and the RV320 will respond with a VLAN 2 IP address. This eliminates the need for DHCP Relay.
seems not to work as the RV320 is restricted to 6 custom VLANs (+ 1 Management VLAN with ID 1).
Maybe I should describe the whole scenario, which should be implemented:
The problem is currently the link IP<->Switch Port. I thought DHCP option 82 is the way to go, but VLANs (one VLAN for each room) may be also a solution. Unfortunately none of the two ways work.
What can be a solution? Was the RV320 the wrong decision (not enough flexibility)?
The RV320 is restricted to 6 subnets as well, so it is not possible to serve DHCP for more than 6 networks. Usually when we are talking about DHCP Relay it is relaying to a Windows Server which provides DHCP for multiple scopes.
The RV220W supports up to 16 VLANs but I have never seen anyone use more than 5 VLANs on any of our routers. That might be worth a shot if you can live without Dual-WAN.
(I need dual WAN, because traffic is spread over two uplink connections.)
But then I wonder for what use cases the RV320 was designed:
Browse to DHCP-> IP & MAC Binding and click on Help in the upper right. This describes how to ensure that devices use the correct IP based on the MAC address.