If you want to access some local resources like the release website from the remote server when you are connecting to the remoter server using ssh over VPN, then possibly reverse ssh tunnelling is the best option. So, basically when you are connecting to the remote server, you tell the server your intent to do so and which local resource you want to connect to and on which port.So, here I want to connnet to google.com and tunnel the data to 192.168.131.921:9090 tthough the tunnel, then the command to use will be ::
ssh google.com -R 8010:172.16.131.92:9090
Now, on the remote server whenever you want to connect to 172.16.131.92:9090, you can do wget http://localhost:8010….
For installation :
sudo yum install dnstop
And now some description:
dnstop is a libpcap application (ala tcpdump) that displays various
tables of DNS traffic on your network.
dnstop supports both IPv4 and IPv6 addresses.
To help find especially undesirable DNS queries, dnstop provides a
number of filters.
dnstop can either read packets from the live capture device, or from a
Couple of days back, I realized there was too much network activity on my
system, although I was not doing anything. Fired up wireshark and to my
astonishment, there was too much of DNS traffic on the network. But the
problem was analyzing the data in wireshark and this is where dnstop came
into light. It helped me narrow down the issue within minutes and problems
And how to run it :
sudo dnstop eth1
If you are setting up the snmpd server and have added your own mibs and do not really know if the mibs are loaded or not then simply go to the directory:
This can save you a lot of time, if you are not getting results with snmpwalk. You can even use snmpwalk as :
snmpwalk -v -c
Well, these little things can save you a lot of time 🙂