Oriolrius.cat Website Review

# USER - remote user of the linux box # HOST - host address of the remote linux box # NETIF - network interface to snif in the remote linux box # FILTER - (optional) rules for filtering traffic to capture Let me present a rare use case of this useful trick. I use a QNAP NAS as a gateway in my home network, where I have 5 NICs. So it’s really useful to snif traffic remotly but I have no tcpdump packet in the system. What I did is use tcpdump as Docker container and finally the # sniffing SIP traffic (port 5060) on interface eth0 # remote linux host (QNAP NAS) use SSH port 55222 When you are playing with Windows Hyper-V and you want to create a completely virtual internal network with private virtual machines inside your Windows 10 machine virtual switch are mandatory. Then it’s the time to connect that virtual switch with the host machine using a virtual network interface. All those steps can be done using Hyper-V manager user interface, but you cannot control 100% of parameters like enable, or not, the NAT of the virtual internal New-VMSwitch -SwitchName NATSwitch -SwitchType Internal New-NetIPAddress -IPAddress 10.46.1.1 -PrefixLength 24 -InterfaceAlias vEthernet (NATSwitch) Of course, change “NATSwitch” for your switch name and “10.46.1.1” for the IP address of the host virtual network card. Remove-VMSwitch -Name NATSwitch Remove-NetIPAddress -InterfaceAlias vEthernet (NATSwitch) In Windows 10 IP forwarding is not enabled and packets between interfaces are not routed. According to the Microsoft forums, you can > Go to Start and search on cmd or command. Right click on either cmd > or command then select Run as administrator. At the command prompt > When your back at the command prompt type services.msc and navigate > to the Routing and Remote Access service. Right click and select > Properties. Change to Automatic and click on Start to start the > service.