This problem is elementary, but I can’t seem to find an answer.
I have a network controlled by an RB493G that has its DHCP server configured to serve up addresses on the 192.168.0.0/24 network. That works. Workstations are assigned an IP address from the 192.168.0.0/24 address pool.
I have several RB411AR RouterBoards that each has the ether1 interface assigned a static IP address on the 192.168.0.0/24 network and the wlan1 interface assigned an address on a separate 10.0.x.0/24 network, i.e. the first RB411AR is assigned 10.0.1.1, the second RB411AR is assigned 10.0.2.1, etc. On each RB411AR, ether1 and wlan1 are bridged together. Each RB411AR has its own address pool on an 10.0.x.0/24 network. Each RB411AR is configured as a DHCP server with the interface assigned to bridge1.
Each RB411AR is configured with its own DHCP pool and DHCP server so that a salesman who connected to the first RB411AR would be assigned an address from the 10.0.1.0/24 address pool. A salesman who connected to the second RB411AR would be assigned an address from the 10.0.2.0/24 address pool, etc.
Everyone can connect, but DHCP is not working as expected. All DHCP connections are coming from the RB493G’s address pool. i.e., if a salesman connects to the first RB411AR, he has full access, but he is assigned an IP address by the RB493G on the 192.168.0.0/24 network instead of being assigned an address on the 10.0.1.0/24 network.
What do I need to do so that each RB411AR can serve up DHCP connections from its own 10.0.x.0/24 address pool for those who use wireless and still allow the RB493G to serve up DHCP connections to workstations that are physically connected to the 192.168.0.0/24 network?
It sounds like the 493 is answering faster since at the moment the DHCP servers all seem to be in the same broadcast domain.
There are various ways to fix this but the best will depend on how the system is being used.
Does the 493 provide internet access? Are the WiFi clients connecting to internet, to the local network or both?
Would you prefer to manage all IP allocations on the 493?
Everyone can log in perfectly. All have access to the Internet and to the private networks (192.168.0.0/24 and 10.0.x.0/24).
The only problem is that the RB493G handles all DHCP chores and I want the RB411AR to handle the DHCP chores for any wireless connections that originate (connect) through that RB411AR. The RB493G still has to handle the DHCP chores for any wired connection to the private network.
OK - well at the moment you have multiple DHCP servers in the same broadcast domain so you have no control over which one a client uses.
Also, unless you have 10.0.x.x addresses on the 493 the wireless clients would have internet access problems if they did get a 10.0.x.x address.
To get the DHCP servers into different broadcast domains I suggest putting a VLAN interface on the 411s and brdiging that to the WLAN rather than the raw ethernet connection. At the 493 you would also have to add corresponding VLAN interfaces to provide the gateway from each 10.0.x network.
This will mean that more traffic is going via the 493 but since it is a G it can probably handle it. It has the advantage that some broadcast traffic will disappear from the WiFi networks.
Personally I would probably pull the DHCP allocation back to the 493 (DHCP server on each VLAN interface) and make sure that there is a spare one and a valid config backup in the cupboard…
The routing tables and masquerading are set up so that all traffic flows properly, i.e. to get to 10.0.1.0/24, traffic is routed through 192.168.0.253, to get to 10.0.2.0/24 traffic is routed through 192.168.0.252, etc.
(One of the reasons that we need multiple class C subnets is the lack of address space on the 192.168.0.0/24 network. Because of proprietary programs that are in place, changing the 192.168.0.0/24 network cannot be done easily.)
I’ve never used VLANS. I’ll study up on that.
Thanks.