Basically, this is a very old post. Originally it was posted in my old Russian blog in early 2012. Nevertheless, I hope it might be useful.

When I was working in the University we used PPTP VPN servers to let our staff access Internet. Computers got default gateway from VPN server and it was a real problem due to the fact that we had a lot of internal servers and different subnets so that gateway was unique for each building. To address this problem our system administrators had to add routes on every computer manually.

Possible solutions were to distribute routes thought DHCP-server.
At that time we used Cisco 4503E as a default gateway and DHCP server.

Routes are controlled by 249 DHCP option, for example, option 249 ip (network) (mask) (gateway).

There is RFC http://www.ietf.org/proceedings/52/I-D/draft-ietf-dhc-csr-06.txt

Unfortunately, it didn’t work /23 and /8 networks…windows computers just ignored them.

Lately, I realized, that it was possible to send option 249 in HEX format.

For instance:

route 172.172.0.0/21 168.168.168.168
write hex:
N byte: 1 2 3 4 5 6 7 8
hex: 15 AC AC 00 A8 A8 A8 A8

description:
byte 1 – mask in hex (21dec -> 15 hex)
byte from 2 to 4 – our network
bytes from 5 to 8 – gateway

in configuration:
!
ip dhcp pool POOL
….
option 249 hex 15ACAC00A8A8A8A8
….
!

Actually, I found the script below to calculate HEX format for 249 option: