The wireshark bit runs Wireshark on your host platform. I'll try to walk through the various components in turn in case you need to change any of these pieces to work with your system. Wireshark -k -i <(vagrant ssh -c "sudo dumpcap -P -i any -w -f 'not tcp port 22'" -ntt) Then we’ll direct the output of that command directly into wireshark, which can read from an interface even if it isn’t literally a network card. What we’re actually going to do is SSH into the guest, run dumpcap, and ask it to write its output to stdout. For vagrant setups, you can usually just type vagrant ssh. A working SSH connection to the guest.Wireshark installed on both host and guest (this is an easy way to get dumpcap installed on the guest even if it’s headless).To get an insight into the traffic going around the place, I’ve been using Wireshark and it’s ability to capture remotely, it’s really simple so I thought I’d write down my “recipe” on how to do this in case it’s useful. you get the picture :) This is great but having everything on the VM can make it a bit trickier to debug what’s going on – and with a website that talks to an API that talks to MySQL, that all lives on a VM with port forwards, you can see the problem :)
The joind.in project uses a really nice vagrant setup for its dev platform – which is much needed these days as we move away from a single LAMP stack install to a website plus another website, which talks to an API and caches in redis and deploys with ….
0 kommentar(er)
