What's new
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

Software Routing

metalhk47

Member
Joined
Jun 11, 2010
Messages
46
Reaction score
2
Hi All,

I was reading through Bossland's guides about IPs and MAC Addys in relation to Warden and I have one question.

MAC Spoofing won't work because your MAC that you connect on is the point of reference used to ban the 'active' accounts at the time the check is done correct?

So... I actually have 2 internet connections that run to my server; so two individual NICs, my question was for techies out there is there a program I can use that can 'with user intervention' route my WoWs through the connection I choose Ie I have 5 Bots running on the NIC that connects to my Cable Internet and then 2 Bots that run on the ADSL NIC. If a ban were to happen to say one of the accounts the the 5 bots were online and botting... all 5 would get banned? or all 7?

So to sum up is there a Software Routing Program?

Virtualizing is not a viable option;
Setting up a Linux box as a Firewall with multiple NICs is kinda costly.
 
Hi All,

I was reading through Bossland's guides about IPs and MAC Addys in relation to Warden and I have one question.

MAC Spoofing won't work because your MAC that you connect on is the point of reference used to ban the 'active' accounts at the time the check is done correct?

So... I actually have 2 internet connections that run to my server; so two individual NICs, my question was for techies out there is there a program I can use that can 'with user intervention' route my WoWs through the connection I choose Ie I have 5 Bots running on the NIC that connects to my Cable Internet and then 2 Bots that run on the ADSL NIC. If a ban were to happen to say one of the accounts the the 5 bots were online and botting... all 5 would get banned? or all 7?

So to sum up is there a Software Routing Program?

Virtualizing is not a viable option;
Setting up a Linux box as a Firewall with multiple NICs is kinda costly.
don'tim pretty sure there isnt, i mean you could run one in a Virtual Machine, and just bind it to one of your network cards. but you need a pretty beefy machine to do that.
 
i mean you could run one in a Virtual Machine, and just bind it to one of your network cards. but you need a pretty beefy machine to do that.

I do have a beefy server running its just that the M/B does't have the option to enable VT (Virtual Technology), which will greatly increase the performance of 'particular' virtual machine to run bots on. Might give it a go see how we go; i'll let you know.
 
I'm not sure if i'm interpreting your question properly, but this may be what you're looking for.

Say you've got two network interfaces coming into your windows box. Normally windows just picks one of the adapters and all network traffic goes through there. If you want to send traffic through the second connection you have to use some 3rd party software.

That software is called ForceBindIP ForceBindIP - Bind any Windows application to a specific interface

So you could run 1 wow window normally it will go to the interface windows has decided is the one everything is going to use.

Then the second wow instance you can launch via a batch script that looks like this:

cd "C:\Games\WoW2\"
ForceBindIP -i [ip address of 2nd nic] "C:\Games\WoW2\WoW.exe"

This should get you connected to wow twice, both connections with a different IP and different mac address.

Hope that helps.

J
 
I'm not sure if i'm interpreting your question properly, but this may be what you're looking for.

Say you've got two network interfaces coming into your windows box. Normally windows just picks one of the adapters and all network traffic goes through there. If you want to send traffic through the second connection you have to use some 3rd party software.

That software is called ForceBindIP ForceBindIP - Bind any Windows application to a specific interface

So you could run 1 wow window normally it will go to the interface windows has decided is the one everything is going to use.

Then the second wow instance you can launch via a batch script that looks like this:

cd "C:\Games\WoW2\"
ForceBindIP -i [ip address of 2nd nic] "C:\Games\WoW2\WoW.exe"

This should get you connected to wow twice, both connections with a different IP and different mac address.

Hope that helps.

J
idk, it seems like it would work, except i would be worried when it isnt. theres no way of knowing if your instance of wow is actually hooked to it. and even if it did, i can see you making the mistake of accidentally forgetting what wow window goes to what connection. and that would be bad.
 
"ForceBindIP works in two stages - the loader, ForceBindIP.exe will load the target application in a suspended state. It will then inject a DLL (BindIP.dll) which loads WS2_32.DLL into memory and intercepts the bind(), connect(), sendto(), WSAConnect() and WSASendTo() functions, redirecting them to code in the DLL which verifies which interface they will be bound to and if not the one specified, (re)binds the socket. Once the function intercepts are complete, the target application is resumed. Note that some applications with anti-debugger / injection techniques may not work correctly when an injected DLL is present; for the vast majority of applications though this technique should work fine."

Dunno, it seams to me that it might have problem with WoW - have you tested it jrox?
 
I've only tested it with Everquest on a emulated server where I was able to log in two accounts on a server that did not allow two connections from the same IP.

Edit: But actually you bring up a good point deusx, WoW/Warden may not be happy about a dll injection. This program may not be safe to use with WoW, so try it at your own risk.
 
Last edited:
if you can get a list of the WoW authentication server IPs, you can bulid specific static routes in windows:

Code:
    route ADD xxx.xxx.xxx.xxx MASK xxx.xxx.xxx.xxx  xxx.xxx.xxx.xxx

    Means:

    route ADD ?network? MASK ?subnet mask?  ?gateway ip?

So for example, if the WoW auth server was 1.2.3.4 and the GATEWAY of ISP2 was, 6.7.8.9, you would do

Code:
route ADD 1.2.3.4 MASK 255.255.255.255 6.7.8.9

Take note of the reboot clause, if you want the routes to be persistent through reboots, do it with route -p
 
Am not a 100% sure it's only the MAC that is sent I personally think Cpu id it sent as well which is a lot harder to change
 
Thanks all for your replies if indeed CPU ID is also checked then Virtual Machine is the only real option. :( That software will come in handy with my IT Job.
 
Last edited:
Last edited:
If you have a proxy server you could ssh into it and do a local port forward on a specific interface then use freecap or proxifier to send wow's data to that local port.
 
Back
Top