Support Support Downloads Knowledge Base Juniper Support Portal 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

[EX] RIP packets will be ignored by Junos if it they are not from UDP port 520



Article ID: KB22363 KB Last Updated: 05 Mar 2017Version: 2.0
This article describes the issue of RIP packets being ignored by Junos, if they are not from UDP port 520.
Customers may claim that Juniper EX failed to establish RIP connections from the source UDP port, if it is not equal to 520; but Cisco runs normally to the same RIP traffic.

According to the RFC1058 Routing Information Protocol, it provides the following information in section 3.4.2:

3.4.2. Response
Because processing of a response may update the host's routing table, the response must be checked carefully for validity. The response
must be ignored if it is not from port 520.

Juniper complied with the RFC1058 strictly, if a Junos device received RIP packets with the source port other than 520, it will drop the packets and create a log similar to the following message in Syslog:

24 Mar 23 11:04:18.061468 Ignoring RIP packet with source port not 520, source port is 4369
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