Bugzilla – Bug 10217
Need method to track potential Dupe MACs
Last modified: 2009-11-18 06:45:18 UTC
Currently we have code in place to find *potential* duplicate MAC addresses in our players. A customer gets a warning email and they contact support in confusion or frustration. Maybe instead, we should *not* send that email to the customer until we've confirmed there's a problem. Can we: * Add code that when a potential dupe is found it adds it to a watch list * Any MAC on the watch list is watched to see if it hops from IP address to IP address, indicating it's being moved from user to user. * If we find a hopping MAC, then we alert Support who can contact the customer to facilitate an RMA Thoughts? What can we do?
Digest of email conversation on this: [DanE} We are seeing a BIG surge in emails going out to customers right now. Example: * In all of November, we had 7 customers email us about this. * In December so far, we have had 38 customers email us about this. * Also, customers are getting multiples of these emails ... Note from a customer: "The problem is that its extremely annoying getting these messages every few hours. They are still coming. If there isn't really a problem then why can't you make them stop?" I propose we disable this email notification until we implement a better method of detecting and tracking dupe MACs. [Andy] They're off now. [Dean] How many were going out? What were the root causes? [Andy] The root cause is the thing they were designed to catch... players moving between accounts. Don't know how many. The reason there were more is because the email was fixed in Falco to be sent for automated moves by UUID. If 2 users have a duplicate UUID they will flap between accounts, generating a lot of emails. I need to come up with a better way to find these players without the user having to see an email. [Dean] Why is it different for UUIDs and MAC addresses? [Andy] Because UUID = auto-registration. MAC is only manual using the PIN. I guess our whole plan with the UUID was flawed if the damn factory can't solve this problem. [Dean] Are you checking the UUIDs against the list? [Andy] No, but I don't think that matters here. That would mean 2 players had the same (wrong) UUID. I just need to add some more data tracking that counts the number of times a player changes accounts or something.