adventures in xp64

(1) WoW FPS is decent without tweaks – not quite XP32 FPS though; not sure why.
(2) Registry modifications to disable Nagle et al work.
(3) Dual monitors work flawlessly.
(4) 1GB RAM still free running WoW and a VM with 1GB RAM.
(5) 3com card doesn’t have drivers and I have no idea what model it is (finding out involves crawling around with a torchlight).

Verdict: A+++ (Although I’m wondering why XP64 seems to put most of the load on CPU3 and not balance it among the 4 like XP32/Vista)

P.S. OpenVZ setup is making me stab people. Please help.


the adventures of biatch0 in modem/router/wifi-land

D-Link 2542B – Modem, 4-port router. Crashed on first night of download tests… 20% into the first file in queue. Punched random babies in face. Possibly the most messy UI and configuration interface I’ve ever seen (this includes the shit UIs that I code sometimes). On the bright side I saved 1 plug point vs my old setup of SDSL modem + 3Com router. EDIT: Forgot to mention that accessing the router web UI felt similar to accessing a poorly coded and very resource intensive website… running on a 386 SX 16MHz. Everything just felt like it was running on something with 30+ load averages.

Linksys AM300 – Modem. Nothing horrible… just impossible to configure. Nothing to do with Linksys though… apparently TIME engineers thought it would be funny to plug in an Aztech DSL605E somewhere on their switch configured to Modem also refuses to allow configuration without DSL link plugged in (which leads to above problem). Stabbed random babies.

SMC Barricade (long model number that nobody bothers to remember) – Modem, 4-port router. A possible challenger to most horrible to configure UI… right after the previously mentioned D-Link. Couldn’t even get this bugger to activate the DSL connection. Dropped random babies from 16th floor lift shaft.

Aztech DSL605E+Buffalo WHR-HP-G54 (DD-WRT) – Standalone Modem, WiFi+4-port router. Most recent setup… and appears to be going to stay. Seems stable after about 12 hours of testing, DD-WRT only gave me problems initially with DHCP (apparently someone else used the router before and decided my box quadbiatch0 would be called subashini-PC). Buffalo AP/router refuses to clock at 250MHz, not an issue though, at least it didn’t hit 10.0 load and cause latency to to reach almost 100ms when I was loading up the router admin page like the D-Link. Obviously stuff like that pisses me off because I hate having high WoW ping.

Moral of the story: Cheap thing no good, good thing no cheap.

Side note: Average of 260ms to WoW server. Average of 43ms latency to the TIME gateway. Anything above 10ms to the first hop outside the internal network is not acceptable IMHO… it’s plain ridiculous. On my pre-NetLynx connection, 43ms would have gotten me half-way to fucking Hong Kong. Verbal Molotov cocktails are incoming to a TIME engineer near you within the next few days if something doesn’t go right.


more nagle+delayed acks

Been doing some “work” on getting around these 2 problems in relation to WoW. My initial intent was to connect to my proxy in Jaring via stunnel/dante-sockd… and having iptables reroute the traffic through socat which would disable Nagle’s and set tcp-nodelay to true. For some strange reason (or maybe I just suck at writing iptables rules), I was unable to get iptables to pick up anything to route to socat. So after more research, I decided to take the SS5 SOCKS Server (or SS5) source code any modify it slightly to mangle ALL packets that came through (which should be only WoW traffic unless you are trying to abuse my machine).

Simple workaround:
(1) Grab the SS5 source.
(2) Open SS5Server.c
#include “netinet/tcp.h”; (Line 26)
setsockopt(S5SocksSocket, IPPROTO_TCP, TCP_NODELAY, &reuseAddrFlag, sizeof(int)); (Line 197)
(3) ./configure && make && make install

(4) proxify all WoW traffic to ipaddress:port that you configured.

You now have WoW minus Nagle+delayed ACKs. Congratulations.



After immense (read: stupid) amounts of grinding, I have now reached level 67. I now consider myself ground… and feel that familiar couldn’t be f*cked feeling that i get when too much grinding has occured. I blame myself for spending illogical amounts of time playing during closed beta… but bite me anyhow. Fortunately though, level 70 is an eventuality… not a possibility (albeit an excruciating and mind numbingly painful eventuality on my warrior).

That’s all OK though, because I have the proverbial pocket healer/windfury totem with me all the time in direct violation of Blizzard’s EULA.