|
|||||||
This is a discussion on "Burly socket modifications?" in the Top Mud Sites MUD Coding forum : Was wondering if anyone out there has done anything with their socket command (or anything similar) to work with MAC addresses, or has it configured some way to make multi-play tracking (for places which do not allow it) easier... Email me or post something on here if you do...thanks... |
|
You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is fast, simple and absolutely free so please, join our MUD community today! If you have any problems with the registration process or your account login, please contact us. If you are a registered member of the old TMS forums, please click here
|
![]() |
|
|
LinkBack | Thread Tools |
|
|
#1 |
|
Member
Join Date: Apr 2002
Location: Chicago, Illinois
Posts: 152
![]() |
Was wondering if anyone out there has done anything with their socket command (or anything similar) to work with MAC addresses, or has it configured some way to make multi-play tracking (for places which do not allow it) easier...
Email me or post something on here if you do...thanks |
|
|
|
|
|
#2 |
|
Senior Member
|
You wouldn't be able to do anything useful with the MAC address, because you're not guarunteed consistency unless you're on a local network. It's also very easy to spoof (most unix systems can use "ifconfig hwaddr=new mac" to change it), unlike an IP. There is (was) an interesting discussion about it on TMC here.
As for multiplay tracking, I haven't implemented anything like this for muds, but I've found that these reports works pretty well for other adminstration areas: Log all IPs and/or hostnames to a database along with the user they logged in under. Then simply cross-reference host and user with two reports. These reports detail which hosts logged on as which user, and which users logged on as which host. I have a summary of this output sent to an email address daily. Probably the easiest way to prevent multiplaying is to simply check the existing connected addresses when a player connects. Although that doesn't really stop proxy-users =). |
|
|
|
![]() |
| Thread Tools | |
Burly socket modifications? - Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| C++ socket code available | Teelf | MUD Announcements | 2 | 06-23-2003 11:06 AM |
| Expanded socket/IP/NIC tracking anyone? | Terloch | MUD Coding | 7 | 02-11-2003 03:12 PM |
|
|