Menu

#150 Destination IP address is not copied to md_info on TCP-Layer

1.3.2.0
closed
mike
None
2017-06-29
2017-02-27
No

If TCP is used as transport layer, the destination ip address is not copied into md_info on receiver-side.

If UDP is used previously, the destination IP address from the last UDP transmission is listed in md_info even if TCP is used.

Discussion

  • Bernd Löhr

    Bernd Löhr - 2017-02-27
    • assigned_to: mike
     
  • mike

    mike - 2017-06-02

    destIpAddr at the TCP receiver side was left dangling, while srcIpAddr was kept maintained. correction attemot in [r1635],
    going to test it a bit deeper now.
    Users may pull and are invited for feedback.

     

    Related

    Commit: [r1635]

  • mike

    mike - 2017-06-02
    • status: open --> accepted
     
  • mike

    mike - 2017-06-02

    sorry I lost an "s" - please pull [r1636]

     

    Related

    Commit: [r1636]

  • Bernd Löhr

    Bernd Löhr - 2017-06-29

    destIpAddr of the receiver for TCP is own address set on tlc_openSession, which can be 0 for the default interface/IP; for UDP listeners (and incoming packets) it will contain either the interfaces IP address or a multicast group. 0 is only returned if the socket implementation does not provide the destIP.

     
  • Bernd Löhr

    Bernd Löhr - 2017-06-29
    • status: accepted --> closed
     
  • Bernd Löhr

    Bernd Löhr - 2017-06-29

    For TCP, the value provided at tlc_openSession() will be returned. This will be INADDR_ANY (0 for default IP) if not set.

     

Log in to post a comment.

MongoDB Logo MongoDB