static route vs directly connected network

bikrambikram Posts: 8Member ■□□□□□□□□□
Hello everyone,

One DHCP server is connected with my router. The interface of this router has an ip (172.17.4.1) of the range of dhcp (172.17.4.1-172.17.7.254).

I want send every packet whose destination ip is in the range (172.17.4.1-172.17.7.254) to another hop (192.168.103.34). How can I do that? Should I add one static route, if the destination is in the range then send it to 192.168.103.34. The router will follow which one? Will it forward all packet according to the static route (which I want) or it will forward all packet to the interface 172.17.4.1 as this is directly connected.

Please help me.
Thanks.

Bik.

Comments

  • wastedtimewastedtime Posts: 586Member
    Well, since a direct connection has a AD of 0 and a static of 1, I would say it would go directly connected. Although why would you want to try to route packets the wrong way? Also if you plan to use the dhcp server through the router you need to setup dhcp relaying as far as I know.
  • mikej412mikej412 Posts: 10,090Member
    bikram wrote:
    I want send every packet whose destination ip is in the range (172.17.4.1-172.17.7.254) to another hop (192.168.103.34).
    What is it that you REALLY want to do?

    If you want traffic coming from outside this router to redirect traffic for that 172.17.4.0/22 range to a HOST 192.168.103.34, then it sounds like a NAT issue.

    If the 172.17.4.0/22 interface is a slow serial link (for backup? for security for certain data/traffic?) and you have a multi-hop path through a 100Mbps Metro Ethernet through a router at 192.168.103.34, than that is another issue.

    And, of course, traffic from within that 172.17.4.0/22 range will stay within that network range -- so I couldn't even guess any way to get that traffic to a 192.168.103.34 address...... unless you're talking about broadcast traffic for DHCP server address requests....

    I don't see the significance of the DHCP server to the way you have phrased your question. Is the DHCP server 192.168.103.34? Do you want that DHCP server to supply DHCP addresses to the clients on the 172.17.4.0/22 network? If so, then the ip helper-address 192.168.103.34 command applied on the 172.17.4.1 router interface may be what you want. (in which case, wastedtime figured out what you were asking long before I did)
    :mike: Cisco Certifications -- Collect the Entire Set!
  • bikrambikram Posts: 8Member ■□□□□□□□□□
    Hello,

    Actually the dhcp is 172.17.4.1 (not 192.168.103.34) connected with my router (172.17.4.2). I want to forward all the packet whose destination is in the range of 172.17.4.1- 172.17.7.254 to another routing device whose ip is 192.168.103.34. The end devices are connected to the routing device and end devices are geting ip from the DHCP.

    But I confuse when any packet enter to my router with destination 172.17.4.200 (lets assume dhcp provided this ip), router will check the routing table, and find the destination network is directly connected and it will forward all the traffic to 172.17.4.2 (but to make my work successful the traffic must be forwarded to 192.168.103.34).


    Any suggestion plz.....

    Thanks.
  • YankeeYankee Posts: 157Member
    Don't make your dhcp range part of the same network where the server lives. Make the network (172.17.4.0) live where the users do.

    Yankee
  • SVSV Posts: 166Member
    Hi Bikram,

    Is there a design error in the network layout.

    Is 192.168.103.34 address of an other interface of the same router?

    Might be if you could make a sketch of the NW diagram it will make things more clearer.
    Life is a journey...
Sign In or Register to comment.