• ohshit604@lemmy.halstead.host
      link
      fedilink
      arrow-up
      0
      ·
      5 hours ago

      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?

        • ohshit604@lemmy.halstead.host
          link
          fedilink
          arrow-up
          0
          ·
          4 hours ago

          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
            0
            ·
            3 hours ago

            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
      0
      ·
      5 hours ago

      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! :)

    • nymnympseudonym@piefed.social
      link
      fedilink
      English
      arrow-up
      0
      ·
      6 hours ago

      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
        0
        ·
        edit-2
        3 hours ago

        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