Every time I send 0x0c I get IP banned, on every realm (which sucks).  I haven't checked the actual clients yet because I was stupid and IP banned myself from every server trying to make 0x0c not hate me.  Is it just me?

[quote author=rabbit link=topic=16379.msg165548#msg165548 date=1172198359]
Every time I send 0x0c I get IP banned, on every realm (which sucks).  I haven't checked the actual clients yet because I was stupid and IP banned myself from every server trying to make 0x0c not hate me.  Is it just me?
[/quote]

I get on fine, post a packet log.

You're probably sending the packet wrong. Remember that the Flags and Channel fields must both be filled out at all times. When using "First Join" (0x01), the Channel Field is the client name (DRTL/DSHR/STAR/SSHR/JSTR/SEXP/W2BN/WAR3/W3XP), though you can set it to anything, as long as it's not nothing.

[quote author=l2k-Shadow link=topic=16379.msg165550#msg165550 date=1172198696]
I get on fine, post a packet log.
[/quote][quote author=rabbit link=topic=16379.msg165548#msg165548 date=1172198359]I was stupid[/quote]

I'll post a log as soon as I can get on on some server.

[quote author=[RealityRipple] link=topic=16379.msg165551#msg165551 date=1172198818]
You're probably sending the packet wrong. Remember that the Flags and Channel fields must both be filled out at all times. When using "First Join" (0x01), the Channel Field is the client name (DRTL/DSHR/STAR/SSHR/JSTR/SEXP/W2BN/WAR3/W3XP), though you can set it to anything, as long as it's not nothing.
[/quote]I've been writing bots since before you were born (well, not really).  The code worked, I changed nothing, a few minutes later I got IP banned.  Besides, I always use force join.

[quote author=rabbit link=topic=16379.msg165552#msg165552 date=1172198878]
I'll post a log as soon as I can get on on some server.
[/quote]
Socks Proxy, mayhap?

I don't build proxy support into my bots for a reason, especially my bots which can load multiple simultaneous connections.

That's why there's programs that create proxy abilities. Linky

Hrm... I have no idea how to screw up on the 0x0C. It's just the dword, of either 0 1 or 2, (I think anything higher would result in a firstjoin) and the channel name (a null terminated string). You really, should post a packetlog. That would help much. By the way, IPBans for invalid packets only last for 10-15 minutes at the most. However, I'm always wrong and I'm pretty stupid too so don't listen to me.

Yeah, I already know all of this.  I should have mentioned that I wanted input from people who know MORE than I do.  Thanks.

there really is no way to get ipbanned from an 0x0c unless you're sending it wrong. in this case, if you know more then I do, then why don't you do the sensible logical thing of packetlogging! your ipban should be up by now. packetlogs reveal all. -.-

My bot:
[code]0000:  FF 0C 12 00 01 00 00 00 42 72 6F 6F 64 20 57 61  ÿ.
...Brood Wa
0010:  72 00                                            r...............[/code]

Brood War:
[code]0000  00 0d 3a 25 13 a8 00 15 c5 1f 66 95 08 00 45 00  ..:%......f...E.
0010  00 42 07 0d 40 00 80 06 26 6c c0 a8 02 22 3f f0  .B..@...&l..."?.
0020  ca 82 0c e9 17 e0 5e 05 b4 f8 e1 3b 1e 88 50 18  ......^....;..P.
0030  fe b4 cd 71 00 00 ff 0b 08 00 50 58 45 53 ff 0c  ...q......PXES..
0040  12 00 01 00 00 00 42 72 6f 6f 64 20 57 61 72 00  ......Brood War.
0050  [/code]

Now IP bans are intermittent, it's quite annoying.

Anyway, I told you my bot was made properly.

I tried sending the 0x0C with the same exact parameters you do; No ipban at all. And that other packetlog below your bot, what's with the extra data? Did you just not filter out the header in that one? Possibly two packets clumped together? And what server have you been testing this on? It doesn't seem to effect 213.248.106.200:6112.

The bottom bit is an Ethereal dump.  There's BNCS 0x0b and 0x0c in there, as well as the TCP headers.  Packet 0x0c starts at 003e, and is *identical* to the one I send from my bot.

The 2nd packet he posted was a log of SC from wireshark.
It had the TCP/IP header still attached. and it has 0x0b in it as well.
FoFo, Mind posting a full log of you bot.
From connection to 0x0c
I've had some experiences where BNet would ban me for ommiting 0x0b.
~Hdx

I omit 0x0B all the time. Literally NOTHING ever happened to me. rabbit, what server are you trying to send the 0x0C on? maybe blizzard might be doing something...

[quote author=rabbit link=topic=16379.msg165640#msg165640 date=1172272354]
The bottom bit is an Ethereal dump.  There's BNCS 0x0b and 0x0c in there, as well as the TCP headers.  Packet 0x0c starts at 003e, and is *identical* to the one I send from my bot.
[/quote]
it isn't identical. notice the char difference in the first few chars of 0x0c for both cases.
however, the hex seem to be identical...

Ante: They are indeed indentical in data. Apparently, however he used two different packetloggers for those.

[quote author=rabbit link=topic=16379.msg165635#msg165635 date=1172270741]
My bot:
[code]0000:  FF 0C 12 00 01 00 00 00 42 72 6F 6F 64 20 57 61   ÿ.
...Brood Wa
0010:  72 00                                             r...............[/code]

Brood War:
[code]0000   00 0d 3a 25 13 a8 00 15 c5 1f 66 95 08 00 45 00  ..:%......f...E.
0010   00 42 07 0d 40 00 80 06 26 6c c0 a8 02 22 3f f0  .B..@...&l..."?.
0020   ca 82 0c e9 17 e0 5e 05 b4 f8 e1 3b 1e 88 50 18  ......^....;..P.
0030   fe b4 cd 71 00 00 ff 0b 08 00 50 58 45 53 ff 0c  ...q......PXES..
0040   12 00 01 00 00 00 42 72 6f 6f 64 20 57 61 72 00  ......Brood War.
0050  [/code]

Now IP bans are intermittent, it's quite annoying.

Anyway, I told you my bot was made properly.
[/quote]
Hm I think this has happened to me before, but I cant remember 100% what it was.
If you dont send 0x0B, 0x0C do you still get disconnected?
I think the problem I had, was somthing to do with client or server token in or around 0x3A

I forget the numbers, but the Channel List packet must be sent (and for most games, the Friend List packet as well) before joining channels.

[code]BNCS SEND 0x3A
0000:  FF 3A 2A 00 8C 12 0C 80 93 1C F8 4D AC 82 7F 40  ÿ:*.Œ€“øM¬‚@
0010:  2B CA CB 39 4C E5 93 63 2D 93 A8 33 F6 ED F4 82  +ÊË9Lå“c-“¨3öíô‚
0020:  4D 65 42 6F 74 50 6C 75 73 00                    MeBotPlus.......

BNCS RECV 0x3A
0000:  FF 3A 08 00 00 00 00 00                          ÿ:.............

BNCS SEND 0x14
0000:  FF 14 08 00 74 65 6E 62                          ÿ.tenb........

BNCS SEND 0x0A
0000:  FF 0A 0F 00 4D 65 42 6F 74 50 6C 75 73 00 00      ÿ..MeBotPlus...

BNCS SEND 0x0C
0000:  FF 0C 12 00 01 00 00 00 42 72 6F 6F 64 20 57 61  ÿ.
...Brood Wa
0010:  72 00                                            r...............[/code]It seems to not be IP banning me now, though I haven't changed anything.  I'm trying my bot on every realm, which is a little disconcerting.

[quote author=rabbit link=topic=16379.msg165726#msg165726 date=1172320105]
It seems to not be IP banning me now, though I haven't changed anything.  I'm trying my bot on every realm, which is a little disconcerting.
[/quote]
Hm, do you use gettickcount api for the clienttoken when you create the password hash?
If so, do you hold it in a variable and use that in the hash and packet, or use a call to gettickcount for each?
I think the problem I had was useing gettickcount api for the function/packet was somtimes there was a slight delay in the hash being made, causeing the gettickcount used in the packet, to be 15ms ahead of the one used in the passhash.

I call GetTickCount and store it in a variable when my connection control class is instantiated.  It seems Battle.net hates me, because now I'm getting IP banned from 0x51 too :\

wow...
rabbit from what i saw in your other packetlogs it seems as if you're sending the packets perfectly, maybe there might be somthing wrong with your winsock error event sub or disconnect sub.. that's all I can say.

No.

Obviously nothing is wrong with your code and Blizzard just hates you.

Does rabbit have a static ip? Blizzard just might be screwing with him.. never know.

[quote author=Sorc.Polgara link=topic=16379.msg165823#msg165823 date=1172433873]
Obviously nothing is wrong with your code and Blizzard just hates you.
[/quote]It's happened before.  But I haven't changed the way I've been sending 0x51 and I'm starting to get IP banned when I send it.

Hm, if you knock up a packet dump function, it might be worth creating a new txt when connecting, and dump every incoming/outgoing bit of data to it, so when you get ip'ed you can check over it.

Uh.... an hour ago I experienced the same behavior on east server .126. The ipbans were much longer then the norm for invalid packets.

you know whats odd, even though this might not be on-topic but somtimes loggin in client, i get IPed on connect thats on client!! but only for short sessions say 5 min ipban. :| this has only been happening for the past 2-3 days.