Re: DHCP clients; where does the preffered routes come from?



Your DHCP clients in the 192.168.1 subnet will be getting a default
gateway from DHCP. That default gateway must be a 192.168.1.x address. The
default gateway must be "reachable" - ie it must be on the same segment and
in the same IP subnet as the host machine.

The problem you are seeing will be caused by the default gateway
settings on the machines in the 192.168.2 subnet. The traffic from a
machine in the 192.168.1 subnet will go to the router which is defined as
the default gateway for the subnet. This router will deliver the packet to
the target machine in the 192.168.2 subnet.

The problem is then how does that machine send a reply back to the
192.168.1 subnet? As you say, if you give them a default gateway of
192.168.2.5 it will work. It will also work if you add a route to the target
machine to send traffic for 192.168.1 to that address.

I presume you want to leave the machines in 192.168.2 pointing to
192.168.2.10 as their default gateway but still be able to "see" the
machines in 192.168.1 ? The simplest way to achieve this is to add a static
route to the router at 192.168.2.10 . All traffic goes to that router by
default. Add a static route to it to "bounce" the local traffic to the
router at 192.168.2.5 . eg

192.168.1.0 255.255.255.0 192.168.2.5


vidro wrote:
> Where do my DHCP clients pick up the gate way to point to the
> 192.168.2.5?
>
> Is the default gateway that is configure in the IP address of the DNS
> server passed on to the DHCP clients?
>
> I have 3 router on a network some clients have configured different IP
> address for their Default gateway.
>
> Scenario:
> Subnet 1: 192.168.1.x has DHCP server and clients
> subnet 2: 192.168.2.x has DNS server
> Two routers on subnet two 192.168.2.5 and 192.168.2.10.
> The DHCP clients on subnet 1 can attach to shared resource of those
> clients on subnet 2 that have been configured with a default gateway
> of 192.168.2.5 but the DHCP clients can not access client on subnet 2
> with default gateway of 192.168.2.10.
> If the clients with Gateways of 192.168.2.10 are reconfigured with a
> GW of 192.168.2.5 the DHCP clients can access the resources.
> If the clients with a GW of 192.168.2.10 have a "Route add" pointing
> to the gate way ( not shown in this scenario) to get to the
> 192.168.1.x network. Than the DHCP clients on 192.168.1.x can access
> the resources.
>
> My question than is it looks like my DHCP clients are picking up a
> preferred gateway of 192.168.2.5 where is this value coming from, if
> my DHCP clients are on a subnet 192.168.1.X?


.



Relevant Pages

  • Re: gateway IP address
    ... An Ethernet network is a 'local' environment, ... a gateway IP address can ... send the Ethernet frame to the router, so that it can pass it to the device ... Device A on Subnet 1, needs to talk to Device B on Subnet 2. ...
    (comp.dcom.sys.cisco)
  • Re: RRAS server separating two subnets - one subnet cannot reach the Internet and computers cant
    ... I have a small lab with a bunch of servers setup on two different subnets, 192.168.1.1 is the gateway for one and 172.16.1.1 is the gateway for the other. ... The RRAS server can reach the Internet as well as the computers in the 192.168.1.0/24 subnet. ... You will need to add some extra routing to your gateway router to get it running. ...
    (microsoft.public.windows.server.networking)
  • Re: DHCP clients; where does the preffered routes come from?
    ... The gateway to get to the 192.168.1.x subnet from 192.168.2x subnet is ... to be access by the DHCP clients on 192.168.1.x subnet and those computer ... This router will deliver the packet to ...
    (microsoft.public.windows.server.networking)
  • Re: route trafic from external to internal adapter
    ... I am remoting into networks through PPTP and RDP and am on a subnet not ... behind o f SBS Server. ... gateway and proxy server for 192.168.30.x client computers. ... If the default gateway for 192.168.30.11 is to the RRAS router and the ...
    (microsoft.public.windows.server.networking)
  • Re: ntpq no longer working -
    ... what it shows the router is addressing 70.41.189.188 at wildblue, ... Where I've used the term "gateway", throughout this email, I'm ... Internet Port ... The subnet mask is used against the IP address to determine what else is ...
    (Fedora)