RVL200 DHCP option 66 or DHCP relay

Unanswered Question
Apr 1st, 2010
User Badges:

There is any possibility to setup TFTP server Name (DHCP option 66) on the RVL200 DHCP server or to setup DHCP relay - forwarding let's say via the IPsec tunnel to a configured DHCP server ?

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Alejandro Gallego Thu, 04/01/2010 - 04:48
User Badges:
  • Cisco Employee,

not near a RVL currently but you should be able to create a firewall rule to allow DHCP accross the tunnel. i do not beleive the RVL has a DHCP realy option, but you should be able to get around that via the firewall rule... OH, no the DHCP server built into the small business routers are just simple and no options can be defined for a scope.

szjozsef Thu, 04/01/2010 - 06:20
User Badges:

Do You think  that the DHCP request can be "forwarded" using firewall rules via the IPSEC VPN tunnel ? If Yes the how ? This should be something like dhcp relay (IP helper in Cisco terms)

Alejandro Gallego Thu, 04/01/2010 - 09:49
User Badges:
  • Cisco Employee,

I see what you mean but we are not using the DHCP protocol in any way so I dont think it would be accurate to say it is similar to DHCP relay or  IP helper. Because we are allowing the broadcast packet and will be sent as such not as an unicast as with relay.  All we are going to do is define what interesting traffic is allowed to pass and what is not.

For example:

Single DHCP server with Multiple scopes:

local scope: ==> .20 - .100 (80 addresses)

remote scope: ==> same as above (just for clarification, the GW defined in this scope would be the LAN IP of the remote gateway router)


allow port 67 and 68 UDP from to subnet

allow port 53 UDP from to subnet

for TFTP you should not have to create a rule as the client would technically be on the LAN at that point.

and then the reverse for the remote site. if you cant set this please post a screenshot of the access rule web page for the router.


This Discussion

Related Content