RIP Packet Format Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30 pm...

What is ls Largest Number Formed by only moving two sticks in 508?

Feather, the Redeemed and Dire Fleet Daredevil

How to compute a Jacobian using polar coordinates?

Putting Ant-Man on house arrest

What to do with someone that cheated their way though university and a PhD program?

France's Public Holidays' Puzzle

Why is water being consumed when my shutoff valve is closed?

Is it appropriate to mention a relatable company blog post when you're asked about the company?

My admission is revoked after accepting the admission offer

How to keep bees out of canned beverages?

What does こした mean?

Is there a possibility to generate a list dynamically in Latex?

Arriving in Atlanta (after US Preclearance in Dublin). Will I go through TSA security in Atlanta to transfer to a connecting flight?

Not within Jobscope - Aggravated injury

Why isn't everyone flabbergasted about Bran's "gift"?

What helicopter has the most rotor blades?

What is a 'Key' in computer science?

What were wait-states, and why was it only an issue for PCs?

How can I wire a 9-position switch so that each position turns on one more LED than the one before?

TV series episode where humans nuke aliens before decrypting their message that states they come in peace

Raising a bilingual kid. When should we introduce the majority language?

A journey... into the MIND

false 'Security alert' from Google - every login generates mails from 'no-reply@accounts.google.com'

What is /etc/mtab in Linux?



RIP Packet Format



Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30 pm US/Eastern)
Announcing the arrival of Valued Associate #679: Cesar Manara
Unicorn Meta Zoo #1: Why another podcast?RIP routing is broken between two routersWhy is RIP not scalable?Why we can not ping to multicast address 224.0.0.9 of RIPRouters are not learning routes when using RIPHow does OSPF understand its directly connected networks if you're configuring interfaces?How do you define cost in Quagga for BGP and RIP?Does RIP stores information about entire AS?Why is RIP sending classless updates?Clarifications about RIP and OSPFthe difference between RIP and OSPF












1















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
    4 hours ago











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

    – Bat
    4 hours ago


















1















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
    4 hours ago











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

    – Bat
    4 hours ago
















1












1








1








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 4 hours ago









BatBat

1083




1083




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
    4 hours ago











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

    – Bat
    4 hours ago





















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

    – Ron Maupin
    4 hours ago











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

    – Bat
    4 hours ago



















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

– Ron Maupin
4 hours ago





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

– Ron Maupin
4 hours ago













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

– Bat
4 hours ago







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

– Bat
4 hours ago












3 Answers
3






active

oldest

votes


















4














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






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
    4 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
    4 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
    36 mins ago





















1














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














    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
























      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









      4














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






      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
        4 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
        4 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
        36 mins ago


















      4














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






      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
        4 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
        4 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
        36 mins ago
















      4












      4








      4







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






      share|improve this answer













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







      share|improve this answer












      share|improve this answer



      share|improve this answer










      answered 4 hours ago









      Ron TrunkRon Trunk

      40.1k33781




      40.1k33781













      • 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
        4 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
        4 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
        36 mins 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
        4 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
        4 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
        36 mins 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
      4 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
      4 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
      4 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
      4 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
      36 mins 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
      36 mins ago













      1














      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




























        1














        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


























          1












          1








          1







          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 4 hours ago









          serverAdmin123serverAdmin123

          39717




          39717























              0














              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














                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












                  0








                  0







                  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 40 mins ago









                  jonathanjojonathanjo

                  12.4k1938




                  12.4k1938






















                      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

                      El tren de la libertad Índice Antecedentes "Porque yo decido" Desarrollo de la...

                      Castillo d'Acher Características Menú de navegación

                      Puerta de Hutt Referencias Enlaces externos Menú de navegación15°58′00″S 5°42′00″O /...