I have following network topology.
LAN clients gets ip’s from main Cisco switch dhcp which have vlan assigned and intervlan ip routing is enabled. all vlan clients can communicate with each other using there dhcp ips because all clients have there default gateway pointed to there local vlan interfaces ip’s.
This switch trunk port is connected with the mikrotik which is acting as pppoe server. As soon as client dials the pppoe dialer (as per policy user must dialer pppoe dialer for tracking/accounting purposes), there local vlan traffic starts to pass/route via mikrotik router which puts high load dueto heavy media sharing used by vlan clients with each other.
How can I force my pppoe clients to use local switch for there local traffic.
Make the Cisco DHCP server provide explicit routes for the local networks (for which there are VLANs), this could be a single
route when they are all contained in a single larger subnet, instead of providing a “default gateway”. Make the PPPoE server
provide the default gateway.
IP routing is enabled on Cisco switch
vlan2 ip 1192.168.2.1
user get ip 192.168.2.2 , gw 192.168.2.1
vlan3 ip 1192.168.3.1
user get ip 192.168.3.2 , gw 192.168.3.1
Vlan 2 & 3 users share heavy media files with each other & they access each other PC using local vlan provided ips like 192.168.2.2 OR 192.168.3.2. Data is passing from the switch direclty. But as soon as they connect PPPoE Dialer to connect with mikrotik in order to get internet access [as per policy] , there local sharing starts routing via mikrotik router.
Example: Before connecting to pppoe server, vlan # 2 user route in windows is as follows
How can I force users to always communicate with each other using there local ips (even if there dialer is connected) & donot use Mikrotik for there local communication.
What I said: make sure the Cisco does NOT provide a default gateway in its DHCP reply, but sends a specific route, in your case this
can be a route for 192.168.2.0/23
This can be done using DHCP options.
Perhaps a practice example might be more feasible.
to further elaborate pe1chl , see following
!
ip dhcp pool vlan2
network 192.168.2.0 255.255.255.0
option 121 ip 24.192.168.3 192.168.2.1
!
ip dhcp pool vlan3
network 192.168.3.0 255.255.255.0
option 121 ip 24.192.168.2 192.168.3.1
!