Blizzard Patcher

[til2]

I know people have probably ranted about this topic before, but this thing takes enitrely fucking too long

[Monox]

there are about a million and a half mirrirs to the bit torrent application that Blizzard uses. Try looking it up on Google, or check "Fileplanet.com"

[Jan]

Not to mention it takes all of one minute to download it if you undergo the meager effort of opening the bittorrent ports.

[Hkat]

heh, 'meager effort of opening bit torrent ports.'

i get a kick out of that. granted, it's not terrible difficult to open up ports on a router, but what i was chuckling about is back when sony used to have a lot of issues with people getting disconnected crossing just about any zoneline. i called CS, and they actually told me that if i was behind a router, i had to open every port from 1 to 63,000 to ensure EQ would work properly.

i asked to speak to his supervisor.

[Jan]

heh, 'meager effort of opening bit torrent ports.'

iptables -A INPUT --protocol tcp --dport 6881:6889 -j ACCEPT;

[Hkat]

and the very next line

granted, it's not terrible difficult to open up ports on a router

as infinitesimal task that might be to you, it could be more of a challenge to others. A task as simple as changing a light bulb would be come loads more difficult, if say...you only had two fingers and no thumbs. It's all a matter of perspective.


that being said, fine job of finding a jab, and incorporating script as well.

[Camara]

Would one of you more computer literate persons take the time to write out how to open these ports? Please include every step, I become more of a computer illiterate moron every day it seems.

[Jan]

Well that depends on what brand of router you have. Generally, the steps are along the lines of this:

1- Find out router's IP:
Start>Run: cmd

Code: Select all

C:\>ipconfig
Windows IP Configuration

Ethernet adapter Blah blah blah:

        Connection-specific DNS Suffix  . : blah.blah
        IP Address. . . . . . . . . . . . : 192.168.0.4
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 192.168.0.100

The router's IP should be the default gateway, or the same as your computer's IP with the last digit substituted with 1 (YMMV). Note that, and your own IP Address.

2- Connect to router:
Fire up Firefox, or whatever the browser you use if you suck, open up URL http://(router ip)

3- Authenticate:
Unless you've changed it before, the router'll have a default password which varies with the brand of the router... It's often "admin", barring that, look it up google.

4- Open ports:
This is where it gets hazy, since most routers have different configuration schemes... Generally, you'll want to look for the "port forwarding" section, or something along those lines. Once you're there, open and forward ports 3724, 6112, and 6881-6999 (or at the very least, 6881-6889 if you can't specify a range) to the IP address of your computer (noted in step 1).

5- Firewall:
If you have a firewall too, you'll have to open up the aforementioned ports in the firewall. You're on your own for that one sadly, as firewalls (apart from iptables) are the dumbest thing to ever have been spawned on this planet.

Edit: This may come in handy.

[Camara]

Thanks Jan, I'll give it a try.

[Kollar]

Fucking witchcraft if you ask me.