• nymnympseudonym@piefed.social
      link
      fedilink
      English
      arrow-up
      9
      ·
      vor 7 Stunden

      Still doesn’t help with things like understanding routing and subnet masks and frame sizes and jfc how does any of this work

      • floquant@lemmy.dbzer0.com
        link
        fedilink
        arrow-up
        2
        ·
        edit-2
        vor 5 Stunden

        Of course not, but I’ve found that seeing the protocols in action and looking at real headers can be very helpful in making them click. Understanding DHCP or ARP or mDNS or BGP or whatever is much easier by inspecting a pcap than it is by reading RFCs

    • ohshit604@lemmy.halstead.host
      link
      fedilink
      arrow-up
      2
      ·
      edit-2
      vor 6 Stunden

      As someone who understands the concept of network but has never professionally entered the field, i assume this just dumps a TCP packet to be inspected, correct?

      • floquant@lemmy.dbzer0.com
        link
        fedilink
        arrow-up
        1
        ·
        vor 5 Stunden

        Yes, but before I used it I assumed that its scope was pretty much limited to what you just mentioned. Instead it can operate on most protocols both above and below layer 4, and it is incredibly useful as a traffic capture tool to produce a .pcap on a remote headless machine which you can then load into Wireshark. The “dump” part is the interesting one, not the “tcp” ;)

        • ohshit604@lemmy.halstead.host
          link
          fedilink
          arrow-up
          1
          ·
          vor 6 Stunden

          Thank you for the affirmation, I got reverse proxies and certificates relatively down, however I am struggling to understand headers and their purposes, I know Mozilla has great documentation regarding headers but lately I’ve gotten lazy, haha.

          • floquant@lemmy.dbzer0.com
            link
            fedilink
            arrow-up
            3
            ·
            edit-2
            vor 5 Stunden

            HTTP headers or headers in general? For the former I suggest Burp Suite to inspect and manipulate headers to see how things change, for the latter tcpdump/wireshark, to supplement your theory reading :)

    • printf("%s", name);@piefed.blahaj.zoneOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      vor 7 Stunden

      Thanks! I started with Wireshark, settled on tcpdump for a while and now I’m too busy learning electrical engineering to give any fucks at all. 🤣 Nah but seriously, tcpdump gave me lots of insight! :)