• nymnympseudonym@piefed.social
      link
      fedilink
      English
      arrow-up
      11
      ·
      25 days 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
        3
        ·
        edit-2
        24 days 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

    • printf("%s", name);@piefed.blahaj.zoneOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      25 days 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! :)

    • ohshit604@lemmy.halstead.host
      link
      fedilink
      arrow-up
      2
      arrow-down
      1
      ·
      25 days 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?

      • floquant@lemmy.dbzer0.com
        link
        fedilink
        arrow-up
        3
        ·
        24 days ago

        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” ;)