Potential issue in RIP: missing handing rtes in rip_receive_request

Mingwei Zheng zmw12306 at gmail.com
Mon Apr 24 01:37:02 CEST 2023


Hi,    
 I am doing testing work on network protocols and there is one possible issue I noticed in RIP:
  When packet command is RIP_CMD_UPDATE_REQUEST, the protocol will call function rip_receive_request to respond to request called from rip_rx_hook. 

   In RFC2453: https://datatracker.ietf.org/doc/html/rfc2453#section-3.9.1

Examine the list of RTEs in the Request one by one. For
each entry, look up the destination in the router's routing database
and, if there is a route, put that route's metric in the metric field
of the RTE. If there is no explicit route to the specified
destination, put infinity in the metric field. Once all the entries
have been filled in, change the command from Request to Response and
send the datagram back to the requestor.

   However in the function rip_receive_request, it seems that only one rte is examined. Could you please take a look at this part? I would really appreciate it. Thank you!

Best,
Mingwei




















More information about the Bird-users mailing list