Configure routing (with netmask)

Vitor Flausino vflausino at
Thu May 10 12:43:19 UTC 2007

What about if the routing was: ->

What was the configuration?
Best regards,

-----Original Message-----
From: dhcp-users-bounce at [mailto:dhcp-users-bounce at] On Behalf Of Tim Peiffer
Sent: Thursday, May 10, 2007 11:54 AM
To: dhcp-users at
Subject: Re: Configure routing (with netmask)

    I agree with Simon's sentiment that it should be done by the router
so that it is transparent to the client, but that approach doesn't work
for the corner cases such as VRF unaware multi-homing in an MPLS

The options are described by RFC3442 option-121 and a Microsoft specific
option-249.  Both do the same things, but Microsoft had their own
reasons for embracing and changing the standards.  Option-121 (and 249)
are both typed as arrays of IP address and come in pairs. ->   is expressed in option-121 as, ->   is expressed in opiton-121 as,

Tim Peiffer
Networking and Telecommunications Services
University of Minnesota

Simon Hobson wrote:
> Vitor Flausino wrote:
>> What is configured there is the default gateway.
>> What is want is also to provide some specific routing.
>> Example:
>> Default gateway ->
>> For IP/Netmask ->
>> For IP/Network ->
> There is an option for this - try the archives for previous discussions.
> HOWEVER - I don't think any of the common clients will do anything
> with it (they don't ask for it, and if you force it on them they will
> probably just ignore it).
> I respectfully suggest that the best way to do this is to configure
> all your routers with the correct routing and it becomes transparent
> to your clients. Apart from the hassle of configuring clients with
> routing tables (and of course changing them whenever your network
> alters), there is also the minor issue that many clients simply don't
> have support for anything more than a default router.

More information about the dhcp-users mailing list