On Tue, 12 Mar 2002, Edwin Humphries wrote: > David, > > On 11 Mar 2002 at 20:59, David Kramer wrote: > > > Does it have to be this way, or can each machine have a non-routeable IP > > address like 192.168.X.X that the gateway does IP masquerading for? That > > would certainly make this easier. > > > > Or you can track my MAC address. Assuming the gateway was a Linux box, > > one could put the network card in promiscuous mode and monitor traffic. > > The tcpdump command can display MAC addresses for you. > > That's been suggested. However, without knowing who owns the MAC > address, we still don't know who's responsible for what traffic.
I don't know if the client machines are Linux, but if they arem you can set the MAC address of each machine. Or just go around and map the MAC address to each machine/person once, since that won't change. At some point you need to associate a static unique network identifier to a person, and that's going to take a little legwork, but just once. Here's a cool idea: Set up a web page on an intranet server with a page that prompts for the username. Submit to a CGI script which will record the username and MAC address. Or do the same thing with a mail server: send out an email for them to reply to, and use the From: address for the name. ------------------------------------------------------------------- DDDD David Kramer http://thekramers.net DK KD There is an art, it says, or, rather, a knack to flying. The DKK D knack lies in learning how to throw yourself at the ground DK KD and miss. All it requires is simply the ability to throw DDDD yourself forward with all weight, and the willingness not to mind that it's going to hurt. That is, it's going to hurt if you fail to miss the ground. Douglas Adams, "Hitchhiker's Guide to the Galaxy". _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list