Support Support Downloads Knowledge Base Case Manager My Juniper Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

DHCP Relay does not work in custom-VR, if the custom-VR is not the default-VR

0

0

Article ID: KB11591 KB Last Updated: 19 Jun 2010Version: 3.0
Summary:
DHCP Relay does not work in custom-VR, but there is a work-around
Symptoms:
By design, DHCP relay does not work in a custom-VR if the custom-VR is not the default-VR. 

'debug dhcp' output reports the following:
## 2008-04-30 02:11:13 : ip dst 172.16.0.11 unreachable in vr trust-vr
## 2008-04-30 02:11:13 : DHCP: Relay request from 10.0.0.1 to 172.16.0.11, ret
= -10994

 
Solution:
This is because all DHCP packets from Juniper firewalls are treated as self packets & self packets will be generated only from the default-VR.

Workaround: If you do not want the custom-vr to be made as the default-vr, then add a route to the DHCP server in the default-vr.
 
Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search