RIP Packet Format












2















I am trying to investigate a RIP packet. It clearly states that the packet is RIP v1. But its format does not match with the either RIP v1 or v2. Any ideas what this packet actually is?



enter image description here










share|improve this question







New contributor




Bat is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





















  • You should use the verbose output (-vv) to get more information with the full protocol decode.

    – Ron Maupin
    6 hours ago











  • I don't have further access to the system. Is it possible to decode via only this packet? @RonMaupin

    – Bat
    6 hours ago


















2















I am trying to investigate a RIP packet. It clearly states that the packet is RIP v1. But its format does not match with the either RIP v1 or v2. Any ideas what this packet actually is?



enter image description here










share|improve this question







New contributor




Bat is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





















  • You should use the verbose output (-vv) to get more information with the full protocol decode.

    – Ron Maupin
    6 hours ago











  • I don't have further access to the system. Is it possible to decode via only this packet? @RonMaupin

    – Bat
    6 hours ago
















2












2








2








I am trying to investigate a RIP packet. It clearly states that the packet is RIP v1. But its format does not match with the either RIP v1 or v2. Any ideas what this packet actually is?



enter image description here










share|improve this question







New contributor




Bat is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.












I am trying to investigate a RIP packet. It clearly states that the packet is RIP v1. But its format does not match with the either RIP v1 or v2. Any ideas what this packet actually is?



enter image description here







routing packet-analysis rip






share|improve this question







New contributor




Bat is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











share|improve this question







New contributor




Bat is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









share|improve this question




share|improve this question






New contributor




Bat is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









asked 7 hours ago









BatBat

1133




1133




New contributor




Bat is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





New contributor





Bat is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.






Bat is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.













  • You should use the verbose output (-vv) to get more information with the full protocol decode.

    – Ron Maupin
    6 hours ago











  • I don't have further access to the system. Is it possible to decode via only this packet? @RonMaupin

    – Bat
    6 hours ago





















  • You should use the verbose output (-vv) to get more information with the full protocol decode.

    – Ron Maupin
    6 hours ago











  • I don't have further access to the system. Is it possible to decode via only this packet? @RonMaupin

    – Bat
    6 hours ago



















You should use the verbose output (-vv) to get more information with the full protocol decode.

– Ron Maupin
6 hours ago





You should use the verbose output (-vv) to get more information with the full protocol decode.

– Ron Maupin
6 hours ago













I don't have further access to the system. Is it possible to decode via only this packet? @RonMaupin

– Bat
6 hours ago







I don't have further access to the system. Is it possible to decode via only this packet? @RonMaupin

– Bat
6 hours ago












3 Answers
3






active

oldest

votes


















7














It's a RIPv1 packet. You're looking at the full IP packet. RIP starts at 0x001c.






share|improve this answer


























  • The problem is that IP 128.238.62.2 (80ee 3e02) appears at the end of the first line. According to the rip v1, the previous 2 bytes should be zero but they have a value of f8f5.

    – Bat
    6 hours ago






  • 3





    That's the source IP in the IP header. Then you have the UDP header, then you have the RIP packet starting at 0x0016.

    – Ron Trunk
    6 hours ago











  • @RonTrunk ... IP starts at 0x0, UDP starts at 0x14 (port, port, length, checksum), surely RIP starts at 0x1c with bytes 0x0201: 0x02 = Response, 0x01 = RIP1.

    – jonathanjo
    3 hours ago













  • @jonathanjo Thanks fo catching that. I edited my answer.

    – Ron Trunk
    2 hours ago



















1














One way to solve this kind of problem is to make a PCAP file from the data (with a tool or just a programming language such as python), and then use standard tools to examine it.



Your packet analysed with tshark is:



Internet Protocol Version 4, Src: 128.238.62.2, Dst: 255.255.255.255
0100 .... = Version: 4
.... 0101 = Header Length: 20 bytes (5)
Differentiated Services Field: 0xc0 (DSCP: CS6, ECN: Not-ECT)
1100 00.. = Differentiated Services Codepoint: Class Selector 6 (48)
.... ..00 = Explicit Congestion Notification: Not ECN-Capable Transport (0)
Total Length: 72
Identification: 0x0000 (0)
Flags: 0x0000
0... .... .... .... = Reserved bit: Not set
.0.. .... .... .... = Don't fragment: Not set
..0. .... .... .... = More fragments: Not set
...0 0000 0000 0000 = Fragment offset: 0
Time to live: 2
[Expert Info (Note/Sequence): "Time To Live" only 2]
["Time To Live" only 2]
[Severity level: Note]
[Group: Sequence]
Protocol: UDP (17)
Header checksum: 0xf8f5 [validation disabled]
[Header checksum status: Unverified]
Source: 128.238.62.2
Destination: 255.255.255.255
User Datagram Protocol, Src Port: 520, Dst Port: 520
Source Port: 520
Destination Port: 520
Length: 52
Checksum: 0xb9a0 [unverified]
[Checksum Status: Unverified]
[Stream index: 0]
Routing Information Protocol
Command: Response (2)
Version: RIPv1 (1)
IP Address: 128.238.63.0, Metric: 1
Address Family: IP (2)
IP Address: 128.238.63.0
Metric: 1
IP Address: 128.238.64.0, Metric: 2
Address Family: IP (2)
IP Address: 128.238.64.0
Metric: 2





share|improve this answer































    0














    This is a response header. Response means ' A message containing all or part of the sender's routing table. This message may be sent in response to a request or poll, or it may be an update message generated by the sender.'



    In addition to that you can see sender ip address and subnet.



    If you want to see more details you can use -vv






    share|improve this answer
























      Your Answer








      StackExchange.ready(function() {
      var channelOptions = {
      tags: "".split(" "),
      id: "496"
      };
      initTagRenderer("".split(" "), "".split(" "), channelOptions);

      StackExchange.using("externalEditor", function() {
      // Have to fire editor after snippets, if snippets enabled
      if (StackExchange.settings.snippets.snippetsEnabled) {
      StackExchange.using("snippets", function() {
      createEditor();
      });
      }
      else {
      createEditor();
      }
      });

      function createEditor() {
      StackExchange.prepareEditor({
      heartbeatType: 'answer',
      autoActivateHeartbeat: false,
      convertImagesToLinks: false,
      noModals: true,
      showLowRepImageUploadWarning: true,
      reputationToPostImages: null,
      bindNavPrevention: true,
      postfix: "",
      imageUploader: {
      brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
      contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
      allowUrls: true
      },
      noCode: true, onDemand: true,
      discardSelector: ".discard-answer"
      ,immediatelyShowMarkdownHelp:true
      });


      }
      });






      Bat is a new contributor. Be nice, and check out our Code of Conduct.










      draft saved

      draft discarded


















      StackExchange.ready(
      function () {
      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fnetworkengineering.stackexchange.com%2fquestions%2f58674%2frip-packet-format%23new-answer', 'question_page');
      }
      );

      Post as a guest















      Required, but never shown

























      3 Answers
      3






      active

      oldest

      votes








      3 Answers
      3






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      7














      It's a RIPv1 packet. You're looking at the full IP packet. RIP starts at 0x001c.






      share|improve this answer


























      • The problem is that IP 128.238.62.2 (80ee 3e02) appears at the end of the first line. According to the rip v1, the previous 2 bytes should be zero but they have a value of f8f5.

        – Bat
        6 hours ago






      • 3





        That's the source IP in the IP header. Then you have the UDP header, then you have the RIP packet starting at 0x0016.

        – Ron Trunk
        6 hours ago











      • @RonTrunk ... IP starts at 0x0, UDP starts at 0x14 (port, port, length, checksum), surely RIP starts at 0x1c with bytes 0x0201: 0x02 = Response, 0x01 = RIP1.

        – jonathanjo
        3 hours ago













      • @jonathanjo Thanks fo catching that. I edited my answer.

        – Ron Trunk
        2 hours ago
















      7














      It's a RIPv1 packet. You're looking at the full IP packet. RIP starts at 0x001c.






      share|improve this answer


























      • The problem is that IP 128.238.62.2 (80ee 3e02) appears at the end of the first line. According to the rip v1, the previous 2 bytes should be zero but they have a value of f8f5.

        – Bat
        6 hours ago






      • 3





        That's the source IP in the IP header. Then you have the UDP header, then you have the RIP packet starting at 0x0016.

        – Ron Trunk
        6 hours ago











      • @RonTrunk ... IP starts at 0x0, UDP starts at 0x14 (port, port, length, checksum), surely RIP starts at 0x1c with bytes 0x0201: 0x02 = Response, 0x01 = RIP1.

        – jonathanjo
        3 hours ago













      • @jonathanjo Thanks fo catching that. I edited my answer.

        – Ron Trunk
        2 hours ago














      7












      7








      7







      It's a RIPv1 packet. You're looking at the full IP packet. RIP starts at 0x001c.






      share|improve this answer















      It's a RIPv1 packet. You're looking at the full IP packet. RIP starts at 0x001c.







      share|improve this answer














      share|improve this answer



      share|improve this answer








      edited 2 hours ago

























      answered 6 hours ago









      Ron TrunkRon Trunk

      40.2k33781




      40.2k33781













      • The problem is that IP 128.238.62.2 (80ee 3e02) appears at the end of the first line. According to the rip v1, the previous 2 bytes should be zero but they have a value of f8f5.

        – Bat
        6 hours ago






      • 3





        That's the source IP in the IP header. Then you have the UDP header, then you have the RIP packet starting at 0x0016.

        – Ron Trunk
        6 hours ago











      • @RonTrunk ... IP starts at 0x0, UDP starts at 0x14 (port, port, length, checksum), surely RIP starts at 0x1c with bytes 0x0201: 0x02 = Response, 0x01 = RIP1.

        – jonathanjo
        3 hours ago













      • @jonathanjo Thanks fo catching that. I edited my answer.

        – Ron Trunk
        2 hours ago



















      • The problem is that IP 128.238.62.2 (80ee 3e02) appears at the end of the first line. According to the rip v1, the previous 2 bytes should be zero but they have a value of f8f5.

        – Bat
        6 hours ago






      • 3





        That's the source IP in the IP header. Then you have the UDP header, then you have the RIP packet starting at 0x0016.

        – Ron Trunk
        6 hours ago











      • @RonTrunk ... IP starts at 0x0, UDP starts at 0x14 (port, port, length, checksum), surely RIP starts at 0x1c with bytes 0x0201: 0x02 = Response, 0x01 = RIP1.

        – jonathanjo
        3 hours ago













      • @jonathanjo Thanks fo catching that. I edited my answer.

        – Ron Trunk
        2 hours ago

















      The problem is that IP 128.238.62.2 (80ee 3e02) appears at the end of the first line. According to the rip v1, the previous 2 bytes should be zero but they have a value of f8f5.

      – Bat
      6 hours ago





      The problem is that IP 128.238.62.2 (80ee 3e02) appears at the end of the first line. According to the rip v1, the previous 2 bytes should be zero but they have a value of f8f5.

      – Bat
      6 hours ago




      3




      3





      That's the source IP in the IP header. Then you have the UDP header, then you have the RIP packet starting at 0x0016.

      – Ron Trunk
      6 hours ago





      That's the source IP in the IP header. Then you have the UDP header, then you have the RIP packet starting at 0x0016.

      – Ron Trunk
      6 hours ago













      @RonTrunk ... IP starts at 0x0, UDP starts at 0x14 (port, port, length, checksum), surely RIP starts at 0x1c with bytes 0x0201: 0x02 = Response, 0x01 = RIP1.

      – jonathanjo
      3 hours ago







      @RonTrunk ... IP starts at 0x0, UDP starts at 0x14 (port, port, length, checksum), surely RIP starts at 0x1c with bytes 0x0201: 0x02 = Response, 0x01 = RIP1.

      – jonathanjo
      3 hours ago















      @jonathanjo Thanks fo catching that. I edited my answer.

      – Ron Trunk
      2 hours ago





      @jonathanjo Thanks fo catching that. I edited my answer.

      – Ron Trunk
      2 hours ago











      1














      One way to solve this kind of problem is to make a PCAP file from the data (with a tool or just a programming language such as python), and then use standard tools to examine it.



      Your packet analysed with tshark is:



      Internet Protocol Version 4, Src: 128.238.62.2, Dst: 255.255.255.255
      0100 .... = Version: 4
      .... 0101 = Header Length: 20 bytes (5)
      Differentiated Services Field: 0xc0 (DSCP: CS6, ECN: Not-ECT)
      1100 00.. = Differentiated Services Codepoint: Class Selector 6 (48)
      .... ..00 = Explicit Congestion Notification: Not ECN-Capable Transport (0)
      Total Length: 72
      Identification: 0x0000 (0)
      Flags: 0x0000
      0... .... .... .... = Reserved bit: Not set
      .0.. .... .... .... = Don't fragment: Not set
      ..0. .... .... .... = More fragments: Not set
      ...0 0000 0000 0000 = Fragment offset: 0
      Time to live: 2
      [Expert Info (Note/Sequence): "Time To Live" only 2]
      ["Time To Live" only 2]
      [Severity level: Note]
      [Group: Sequence]
      Protocol: UDP (17)
      Header checksum: 0xf8f5 [validation disabled]
      [Header checksum status: Unverified]
      Source: 128.238.62.2
      Destination: 255.255.255.255
      User Datagram Protocol, Src Port: 520, Dst Port: 520
      Source Port: 520
      Destination Port: 520
      Length: 52
      Checksum: 0xb9a0 [unverified]
      [Checksum Status: Unverified]
      [Stream index: 0]
      Routing Information Protocol
      Command: Response (2)
      Version: RIPv1 (1)
      IP Address: 128.238.63.0, Metric: 1
      Address Family: IP (2)
      IP Address: 128.238.63.0
      Metric: 1
      IP Address: 128.238.64.0, Metric: 2
      Address Family: IP (2)
      IP Address: 128.238.64.0
      Metric: 2





      share|improve this answer




























        1














        One way to solve this kind of problem is to make a PCAP file from the data (with a tool or just a programming language such as python), and then use standard tools to examine it.



        Your packet analysed with tshark is:



        Internet Protocol Version 4, Src: 128.238.62.2, Dst: 255.255.255.255
        0100 .... = Version: 4
        .... 0101 = Header Length: 20 bytes (5)
        Differentiated Services Field: 0xc0 (DSCP: CS6, ECN: Not-ECT)
        1100 00.. = Differentiated Services Codepoint: Class Selector 6 (48)
        .... ..00 = Explicit Congestion Notification: Not ECN-Capable Transport (0)
        Total Length: 72
        Identification: 0x0000 (0)
        Flags: 0x0000
        0... .... .... .... = Reserved bit: Not set
        .0.. .... .... .... = Don't fragment: Not set
        ..0. .... .... .... = More fragments: Not set
        ...0 0000 0000 0000 = Fragment offset: 0
        Time to live: 2
        [Expert Info (Note/Sequence): "Time To Live" only 2]
        ["Time To Live" only 2]
        [Severity level: Note]
        [Group: Sequence]
        Protocol: UDP (17)
        Header checksum: 0xf8f5 [validation disabled]
        [Header checksum status: Unverified]
        Source: 128.238.62.2
        Destination: 255.255.255.255
        User Datagram Protocol, Src Port: 520, Dst Port: 520
        Source Port: 520
        Destination Port: 520
        Length: 52
        Checksum: 0xb9a0 [unverified]
        [Checksum Status: Unverified]
        [Stream index: 0]
        Routing Information Protocol
        Command: Response (2)
        Version: RIPv1 (1)
        IP Address: 128.238.63.0, Metric: 1
        Address Family: IP (2)
        IP Address: 128.238.63.0
        Metric: 1
        IP Address: 128.238.64.0, Metric: 2
        Address Family: IP (2)
        IP Address: 128.238.64.0
        Metric: 2





        share|improve this answer


























          1












          1








          1







          One way to solve this kind of problem is to make a PCAP file from the data (with a tool or just a programming language such as python), and then use standard tools to examine it.



          Your packet analysed with tshark is:



          Internet Protocol Version 4, Src: 128.238.62.2, Dst: 255.255.255.255
          0100 .... = Version: 4
          .... 0101 = Header Length: 20 bytes (5)
          Differentiated Services Field: 0xc0 (DSCP: CS6, ECN: Not-ECT)
          1100 00.. = Differentiated Services Codepoint: Class Selector 6 (48)
          .... ..00 = Explicit Congestion Notification: Not ECN-Capable Transport (0)
          Total Length: 72
          Identification: 0x0000 (0)
          Flags: 0x0000
          0... .... .... .... = Reserved bit: Not set
          .0.. .... .... .... = Don't fragment: Not set
          ..0. .... .... .... = More fragments: Not set
          ...0 0000 0000 0000 = Fragment offset: 0
          Time to live: 2
          [Expert Info (Note/Sequence): "Time To Live" only 2]
          ["Time To Live" only 2]
          [Severity level: Note]
          [Group: Sequence]
          Protocol: UDP (17)
          Header checksum: 0xf8f5 [validation disabled]
          [Header checksum status: Unverified]
          Source: 128.238.62.2
          Destination: 255.255.255.255
          User Datagram Protocol, Src Port: 520, Dst Port: 520
          Source Port: 520
          Destination Port: 520
          Length: 52
          Checksum: 0xb9a0 [unverified]
          [Checksum Status: Unverified]
          [Stream index: 0]
          Routing Information Protocol
          Command: Response (2)
          Version: RIPv1 (1)
          IP Address: 128.238.63.0, Metric: 1
          Address Family: IP (2)
          IP Address: 128.238.63.0
          Metric: 1
          IP Address: 128.238.64.0, Metric: 2
          Address Family: IP (2)
          IP Address: 128.238.64.0
          Metric: 2





          share|improve this answer













          One way to solve this kind of problem is to make a PCAP file from the data (with a tool or just a programming language such as python), and then use standard tools to examine it.



          Your packet analysed with tshark is:



          Internet Protocol Version 4, Src: 128.238.62.2, Dst: 255.255.255.255
          0100 .... = Version: 4
          .... 0101 = Header Length: 20 bytes (5)
          Differentiated Services Field: 0xc0 (DSCP: CS6, ECN: Not-ECT)
          1100 00.. = Differentiated Services Codepoint: Class Selector 6 (48)
          .... ..00 = Explicit Congestion Notification: Not ECN-Capable Transport (0)
          Total Length: 72
          Identification: 0x0000 (0)
          Flags: 0x0000
          0... .... .... .... = Reserved bit: Not set
          .0.. .... .... .... = Don't fragment: Not set
          ..0. .... .... .... = More fragments: Not set
          ...0 0000 0000 0000 = Fragment offset: 0
          Time to live: 2
          [Expert Info (Note/Sequence): "Time To Live" only 2]
          ["Time To Live" only 2]
          [Severity level: Note]
          [Group: Sequence]
          Protocol: UDP (17)
          Header checksum: 0xf8f5 [validation disabled]
          [Header checksum status: Unverified]
          Source: 128.238.62.2
          Destination: 255.255.255.255
          User Datagram Protocol, Src Port: 520, Dst Port: 520
          Source Port: 520
          Destination Port: 520
          Length: 52
          Checksum: 0xb9a0 [unverified]
          [Checksum Status: Unverified]
          [Stream index: 0]
          Routing Information Protocol
          Command: Response (2)
          Version: RIPv1 (1)
          IP Address: 128.238.63.0, Metric: 1
          Address Family: IP (2)
          IP Address: 128.238.63.0
          Metric: 1
          IP Address: 128.238.64.0, Metric: 2
          Address Family: IP (2)
          IP Address: 128.238.64.0
          Metric: 2






          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered 3 hours ago









          jonathanjojonathanjo

          12.4k1938




          12.4k1938























              0














              This is a response header. Response means ' A message containing all or part of the sender's routing table. This message may be sent in response to a request or poll, or it may be an update message generated by the sender.'



              In addition to that you can see sender ip address and subnet.



              If you want to see more details you can use -vv






              share|improve this answer




























                0














                This is a response header. Response means ' A message containing all or part of the sender's routing table. This message may be sent in response to a request or poll, or it may be an update message generated by the sender.'



                In addition to that you can see sender ip address and subnet.



                If you want to see more details you can use -vv






                share|improve this answer


























                  0












                  0








                  0







                  This is a response header. Response means ' A message containing all or part of the sender's routing table. This message may be sent in response to a request or poll, or it may be an update message generated by the sender.'



                  In addition to that you can see sender ip address and subnet.



                  If you want to see more details you can use -vv






                  share|improve this answer













                  This is a response header. Response means ' A message containing all or part of the sender's routing table. This message may be sent in response to a request or poll, or it may be an update message generated by the sender.'



                  In addition to that you can see sender ip address and subnet.



                  If you want to see more details you can use -vv







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered 6 hours ago









                  serverAdmin123serverAdmin123

                  39517




                  39517






















                      Bat is a new contributor. Be nice, and check out our Code of Conduct.










                      draft saved

                      draft discarded


















                      Bat is a new contributor. Be nice, and check out our Code of Conduct.













                      Bat is a new contributor. Be nice, and check out our Code of Conduct.












                      Bat is a new contributor. Be nice, and check out our Code of Conduct.
















                      Thanks for contributing an answer to Network Engineering Stack Exchange!


                      • Please be sure to answer the question. Provide details and share your research!

                      But avoid



                      • Asking for help, clarification, or responding to other answers.

                      • Making statements based on opinion; back them up with references or personal experience.


                      To learn more, see our tips on writing great answers.




                      draft saved


                      draft discarded














                      StackExchange.ready(
                      function () {
                      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fnetworkengineering.stackexchange.com%2fquestions%2f58674%2frip-packet-format%23new-answer', 'question_page');
                      }
                      );

                      Post as a guest















                      Required, but never shown





















































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown

































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown







                      Popular posts from this blog

                      How did Captain America manage to do this?

                      迪纳利

                      南乌拉尔铁路局