If, on the other hand, also main office requires DHCP services, it's necessary to change the existing pools to ranges x.x.x.0/25, and create new pools in ranges x.x.x.128/25 for the branch use. All addresses in x.x.x.0/25 are then available in the main office, and devices in the branch office will receive IPs starting (for example) from x.x.x.130/25. This method of interVLAN communication is called router on a stick (ROAS) and enables all VLANs to communicate through a single physical interface.
If all devices in the main office use static IP addressing, the existing DCHP pools and reservations can just be changed to provide IPs in range x.x.x.128/25. To allow interVLAN communication, you can divide a single physical interface on a router into logical interfaces that will be configured as trunk interfaces. Using the current devices and IP ranges it means splitting the networks. Devices in the main office VLAN 30 will receive the DHCP Offer, but since they didn't request it they will drop the packetĪs Ron says, changing the IP addressing on one side is the solution.On the G0/1 port I use this as TRUNK to the ROUTER. The configuration is as follow : On the router I have some unconfigured ports (4,5,6,7,8) (vlan 1) on this port I connect directly the WAN (INTERNET) from my provider.
The only problem now is the pc on the Branch side is not getting the ip address. Gateway pc uses static ip address while Branch pc acquired their ip address through dhcp server which is the Gateway router. I don't know what i did wrong because i have configured the dhcp pool, subinterfaces and dhcp relay agent.