Why not running a dynamic routing protocol between Main, A, B, and C. ? Static routes = manual maintenance.
Selon Deric Kwok <deric.kwok2...@gmail.com>: > Hi all > > I have network question and hope you can help > > main router- 3 static routes > ip route 192.168.0.0/24 10.0.0.1 (routerA) ---- > ip route 192.168.1.0/24 10.0.0.2 (routerB) ----same switch ---telecom > company---client request > ip route 192.168.2.0/24 10.0.0.3 (routerC) ---- > > Diagram > ======= > ---routerA--- > main router ---switch ---routerB--- switch ---telecom company > ---routerC--- > dyname ip clients ip 192.168.0.0/24 and 192.168.1.0/24 > static ip clients ip 192.168.2.0/24 > This setting is fine when any dynamic ip clients sent from telcom company. > But When telecom company sent request from static ip client > (any ip in 192.168.2.0/24) but this client is sent to in routerA, > how this work out? > I really don't want to have 192.168.2.0 in routerC to routerB then routerA > in loop > as there will have big admin work if there is more than 3 routers and have > increase > new static ip client for the future > Thank you for your help > _______________________________________________ > cisco-nsp mailing list cisco-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ > _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/