mIRC Home    About    Download    Register    News    Help

Print Thread
#217420 11/01/10 10:29 AM
R
Rumieus
Rumieus
R
i was able to connect socks4 using this

.bset &bvar 1 4 1 27 88 216 152 78 163 0
.sockwrite $sockname &bvar

the socks connect fine, but if i change it to

.sockwrite $sockname 00110001001000000011010000100000001100010010000000110010001101110010000000111000001110000010000000110010001100010011011000100000001100010011010100110010001000000011011100111000001000000011000100110110001100110010000000110000

the sock fail to connect. Anyone know why?

#217422 11/01/10 10:48 AM
S
s00p
s00p
S
1. This is not a SOCKS4-related forum.
2. The SOCKS4 documentation contains information about the SOCKS4 protocol. To assume that we are here to repeat everything the documentation says for your own benefit is lazy, rude and a sign of stupidity. Please leave and never come back.
3. Your SOCKS4 CONNECT packet in the second example is invalid.

#217428 11/01/10 01:19 PM
Joined: Nov 2006
Posts: 1,552
H
Hoopy frood
Offline
Hoopy frood
H
Joined: Nov 2006
Posts: 1,552
You can't live without that "2.", can you? I start to believe you somehow live for it...

Horstl #217430 11/01/10 01:32 PM
S
s00p
s00p
S
Horstl, though I understand where you are coming from here, a proper understanding of the SOCKS4 protocol is required to understand why that particular "connection string" is an invalid connection string.

#217452 12/01/10 11:27 AM
Joined: Aug 2006
Posts: 182
T
Vogon poet
Offline
Vogon poet
T
Joined: Aug 2006
Posts: 182
Eh, I would have agreed that it was unwarrented until I saw the OP's avatar. Now, I'm ok with it.


Link Copied to Clipboard