hi everyone,

i having some problem routing from cmd to linux, i typed all command i i followed the step on first pages,

under CMD - route -p ADD 12.129.233.22 MASK 255.255.255.255 192.168.1.3 < i typed this command but when i try to login it doesnt allow me to go character screen and if i delete the route then i can login and the latency is still same

any advice? 12.129.233.22 < is my server ip i get from tcpview

have you checked and confirmed that ur VM linux is on 192.168.1.3?

(if you delete the route obviously you can login as ur using local login and latency is obviously not affected)

yeap, i checked under ifconfig on new console eth0 addr is 192.168.1.3

ok the first line you type in the vm linux console got any msg come out after you press enter? same goes for 2nd line. can you provide a screen capture of the vmlinux console after you enter the 2 commands so we can check if you have any typos/errors etc

also, are you able to surf the internet from vmlinux? if you cant then most likely you'll have problems with the routing too

yea, i able to surf web using linux and there is no msg come out on the command i typed

you can see the screen

ok i can barely find any errors... but you seriously typed in "Yarre's fix"?
ok close the console, try typing the 2 commands WITHOUT "Yarre's fix"

see if it works then (a guess could be the "Yarre's fix" you typed in messed it)

ok Quazacolt , sorry for late reply, i went to sleep cause that time just come back from work >.<

hi, i just tested and i got this screen out, it that mean ok or not?



This post has been edited by gofey: Jun 6 2008, 07:46 PM

According to your screenie should be no problem, try login and see whether the ping is lower or not.

finally you got the right output, try to login and see if the console is spammed with text. if it is then ur good to go

yea thank alot i able to login but actually it seem like my ping never lowered >.< i been playing for 400 to 500 ms all the while but only happened for recently my connection 700 to 1k ms cause they cut my line last week =X

hi i have read through every page and cant work this out, i have set up VM on my main comp, and connected to wow, all worked beautifully, and i have a spare comp laying around, so what im trying to do, is have that spare comp run VM, and then my main comp just connect to that, and thats where all the fail starts, if anyone has any noob friendly guides on how to run VM on a seperate comp to your comp running wow, it would be much appreciated


so far set up is, both comps connected to my router, if that helps you guys determin my problem

This post has been edited by lufkin: Jun 10 2008, 04:11 PM

so basically, vm on ur main pc working ok no prob, but when you use another pc to vm problem starts?

should be easy, change the route to the ip of the other pc ur using. (from the command prompt of the main pc)
then on the other pc, modify the ip accordingly too.

Also another thing to note is that try to assign static DHCP on your router so your ip wont change when the lease time expires.

ok i think i have bigger problems now, VM is working on my main pc fine which is on vista, now the second comp i want VM to actually be on is using xp and i just put wow on it then to test, and nothing happens, is there something different i need to do for xp?

its the same be it XP or vista. and you dont need WoW on the 2nd comp to run vm

As of Patch 2.3.2 I believe this method is no longer needed as Nagle's Algorithm is disabled in WoW traffic.

Can someone verify?

/shrug.

its on server side and doesnt help much at all for client side. so yes this still helps

Ahhhh so it's just a server side fix!

can i use ubuntu instead of debian or other linux system? cos ubuntu is the only linux installation that i own? any tips guys?

yeah you can IINM, just gotta get socat/iptables thingies (which im not sure if ur ubuntu installation already includes em)

if it isnt included, go download

Well i tried this on ubuntu, do note mine was Fiesty Fawn, not the latest version of ubuntu. Socat was not installed by default, you will have to download it. As for iptables, i am not sure.

For those whom can login into to WoW after setting up the VM linux fix, but stuck in character screen. Please check that you specify the correct IP of the server you are playing. Often times, it is due to, your iptables and socat IP specify is wrong.

I was having the same problem until i found out that WoW has changed the IP of the server i am playing on. It used to be xxx.xxx.xxx.27, but suddenly it did not work, and after some poking around i found out it was changed to xxx.xxx.xxx.2. My socat was redirecting to 27, which resulted me stuck in retrieving character screen.

This post has been edited by Madgeiser: Jul 23 2008, 04:59 PM