Hot answers tagged networking
Shortly after posting, I found the problem: [jadavis6@ditirlns01 ~]$ host ditirldv02.ncat.edu ditirldv02.ncat.edu has address 220.127.116.11 ditirldv02.ncat.edu has address 18.104.22.168 [jadavis6@ditirlns01 ~]$ So it appears that nc will cycle through all A records for a given host and test each one individually. The first failure was for the incorrect IP ...
udev doesn't create any /dev files for network cards because network cards don't have device files. Network interfaces are one of the exceptions to everything is a file. You can, however, look in /sys/class/net. That's maintained by the kernel directly, and should show you all the network interfaces on the system. You can also get the list out of /proc ...
Most likely, the TUN/TAP driver is the only thing that uses that directory. Grepping the 3.11 kernel source Documentation/ directory, tuntap.txt is the only real reference to it, and that was written 12+ years ago. I notice /dev/net does not exist on a system here where I've configured TUN/TAP out of the kernel.
Method #1 - disable password logins If you don't require allowing password logins, then simply disallowing them will give you the desired effect. Simply add this line to /etc/ssh/sshd_config: PasswordAuthentication no Additionally you can limit password use to certain users using the Match operator in sshd_config: Match User root,foo,bar ...
Wireshark might be what you're looking for. To analyse packet loss you should isolate the session/stream and append "and tcp.analysis.lost_segment" to the automatically generated filter. If you see packets there then it's likely there's packet loss.
I have not had a chance to full vet this yet but I did find this guide which sounds like what you're asking to do. It discusses the application of static IPs that can be applied through NetworkManager, which would in theory, have access to the network information when your laptop moves from one network to another. The guide is titled: Roaming Profiles with ...
I wrote something awhile back that keeps an eye on your IPs using a couple of different methods and gives some options for notification and such. It was written for CentOS but it wouldn't take much to adapt it to Debian flavours. Feedback is welcome. http://code.google.com/p/ipcheck/source/browse/ipcheck.sh
Only top voted, non community-wiki answers of a minimum length are eligible