Hot answers tagged networking
The 2 methods I've seen used predominately are to use ethtool or to manually parse the contents of /sys. ethtool For example if your interface is eth0 you can query it using ethtool and then parse for the line, "Link detected". Example $ sudo ethtool eth0 Settings for eth0: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full ...
I believe you could use nmap to get such information. The below command lists me all the machines/devices connected in my network. It is a home network and it lists me all the machines in my home. nmap -sP 192.168.1.0/24 I believe you need to modify the subnet mask and IP range that you are in to suit your requirements.
Use mii-tool (man page): # mii-tool em1 em1: negotiated 100baseTx-FD flow-control, link ok There is also nmcli from NetworkManager: $ nmcli -f capabilities.carrier-detect,capabilities.speed device show em1 CAPABILITIES.CARRIER-DETECT: yes CAPABILITIES.SPEED: 100 Mb/s * device can be shorten to d
First, I'll note that the invocation of ntop in the process tree you shared, doesn't seem to have the -n flag: /usr/sbin/ntop -d -L -u ntop -P /var/lib/ntop --access-log-file /var/log/ntop/access.log -i venet0:0 -p /etc/ntop/protocol.list -O /var/log/ntop but I assume given your statements about the queries continuing even with ntop killed, that it is not ...
You can check if your MAC address really changed by using ifconfig and look the HWAddr value behind the appropriate device name. What has worked for me on Mint, without any additional programs to install is using ifconfig: sudo ifconfig eth0 down sudo ifconfig eth0 hw ether 00:01:02:03:04:05 sudo ifconfig eth0 up or in more permanent fashion by adding ...
The guidance on the Wireshark documentation suggests capturing the entire contents of the packet using this command: $ tcpdump -i <interface> -s 65535 -w <some-file> Looking at the man page for tcpdump the guidance there suggests that -s0 should be equivalent: -s Snarf snaplen bytes of data from each packet rather than the default ...
It's a bit tricky. You can isolate only traffic that passes through your gateway. For instance you can use that rules: iptables -I FORWARD -s 192.168.1.0/24 -d 192.168.2.0/24 -j DROP iptables -I FORWARD -d 192.168.1.0/24 -s 192.168.2.0/24 -j DROP or: iptables -I FORWARD -i eth0.1 -o eth0.2 -j DROP iptables -I FORWARD -o eth0.1 -i eth0.2 -j DROP Both ...
Even with latest firmware and driver updates the server didn't make a TCP connection, but the problem was solved changing the motherboard. An IBM technician changed the motherboard and it started to work properly. Really weird problem.
Only top voted, non community-wiki answers of a minimum length are eligible