Re: [dhcwg] Any documentation for handling /32 IPv4 assignments from DHCP?

Hello Matthew,

I see no other answer, but I have some thoughts.

First, I am not sure why this script is written that way.  When a router 
address is allocated by DHCP ('option routers') it is typically a 
default router, and hence it must have that 'default' qualifier in the 
subsequent route add command.  The first lines of the script would be 
nonsense.

On another hand, one may allocate a prefix (instead of an address), and 
hence it would need that prefix to be reachable through that router.

Le 05/12/2013 19:18, Matthew Dempsky a écrit :
> In dhcp-4.2.5-P1/client/scripts/linux, there's this code for adding
> routes based on the Router (3) and Subnet Mask (1) options:
>
>      for router in $new_routers; do
>        if [ "x$new_subnet_mask" = "x255.255.255.255" ] ; then
>          route add -host $router dev $interface

I wonder whether those two lines above have anything to do with IPv4 
Subnet Allocation RFC6656 "Description of Cisco Systems' Subnet 
Allocation Option for DHCPv4" INFORMATIONAL.

>        fi
>        route add default gw $router $metric_arg dev $interface
>      done
>
> Is this special case logic for subnet_mask==255.255.255.255 codified
> anywhere?

I dont know.

>  I'm working on adding similar logic to OpenBSD's DHCP
> client (so OpenBSD can connect to a network currently supported by ISC
> DHCP on Linux),

That is a very good goal.

> but I'm having trouble finding any authoritative
> documentation explaining the correct behavior here.

Maybe one would ask the author of that script why did s/he write it that 
way?  Does the script have a author name in the head.

> In particular, ISC DHCP 4.2.5-P1 only adds the "dev" route for Router
> (3), but I'm wondering if they should be added for Static Route (33)
> and/or Classless Static Route Option (121) too?

I dont know.

Alex

>
> Thanks
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg
>
>