What's new
By:
  • Visit Rebornbuddy
  • Visit Resources
  • Visit API Documentation
  • Visit Downloads
  • Visit Portal
  • Visit Panda Profiles
  • Visit LLamamMagic

Concerned about 'Players Near You' ?

steev87

steev87

New Member
Joined
Nov 21, 2012
Messages
46
Reaction score
0
2c1c2e01cffa45ba9874c20.webp

Doesn't feel good as all of my bots are seeing each other on the same local network... Even when you disable it, it still shows some engage monsters blsht messages from your 'network' friends :confused:
 
yeah. I also came back to my bot, that I run for shits and giggles, to find someone else in my game. Game was not open to public, nor do I have quick join on....

/boggle
 
I was just about to post this same topic, I run my bots on multiple v.p.n. networks, but this will allow the game clients to see each other including my main over my LAN. Perhaps some way to firewall them off?
 
just saw this when i opened my 4th bot, meaning blizz can see this as well (take that however you want, ill leave it at that)

turned it off regardless
 
Last edited:
Well, right now I can say for sure that this is possible due to Blizz accesing ARP cache table in Windows.
That cache can be see by going : cmd > arp -a , and here you see all your LAN devices.
And they can access it. Not sure if they store such info on their servers but this is real sh*t.
You can't just block it that easily but I guess there is some kind of solution for it.
 
I think DB bot itself or plugin can block that d3 function. I request such thingie :)
 
Block UDP 255.255.255.255 on port 6120
Or block incoming 6120 port UDP
 
I don't see how this would be new information for blizzard, if you are on a public DNS (like college dorm) i could see it is bad that randoms can join you but if your bots see each other? I am sure blizzard has always been able to match bots by IP they just never choose to use it as reason for bans.
 
Gniller said:
I don't see how this would be new information for blizzard, if you are on a public DNS (like college dorm) i could see it is bad that randoms can join you but if your bots see each other? I am sure blizzard has always been able to match bots by IP they just never choose to use it as reason for bans.
Click to expand...

Each bot - unique private IP. Unique MAC. Different subnets.
Don't want to dig into tech details. If they wish they could end botting right now, and there is much more otherways doing in. Not related to network and stuff.

Yet, this. I just don't like it, maybe it was ages ago and its just us didn't know that. But my paranoia helps me bot since summer, and I had only small percent of bans on december, where a lot were hit. And me not exception too.

From what I can see, D3 sends UDP broadcast on 6120 port, (its just one packet) and receives replies.
There is some data in it, use wireshark who interested, not sure if it is sensitive but im 100% sure that its results, lets bnet service give you near players list, so per say, its server sided feature. Yet again, dont like it.
 
Last edited:
So it is sending and receiving from that same (6120) port? Easy enough to block. Also D3 seems to be connected to other computers on LAN on port 445, for what purpose who knows :confused:
 
Although I have disabled it under 'Social', everytime my BOT renew and runs the game profile, it automatically allows quick join? So can anyone from the public just pop into my game and BAM... there goes my account!
 
BlowMeDry said:
Although I have disabled it under 'Social', everytime my BOT renew and runs the game profile, it automatically allows quick join? So can anyone from the public just pop into my game and BAM... there goes my account!
Click to expand...

I think this is an error in D3 atm... I can't seem to turn off quick join even manually. It's getting real annoying having random friends join 24/7. I had to stop botting my main account until this is fixed.
 
You must log in or register to reply here.
Back
Top