$ForceMove BugorNOT?
 

News:

29 December 2022 - PtokaX 0.5.3.0 (20th anniversary edition) released...
11 April 2017 - PtokaX 0.5.2.2 released...
8 April 2015 Anti child and anti pedo pr0n scripts are not allowed anymore on this board!
28 September 2015 - PtokaX 0.5.2.1 for Windows 10 IoT released...
3 September 2015 - PtokaX 0.5.2.1 released...
16 August 2015 - PtokaX 0.5.2.0 released...
1 August 2015 - Crowdfunding for ADC protocol support in PtokaX ended. Clearly nobody want ADC support...
30 June 2015 - PtokaX 0.5.1.0 released...
30 April 2015 Crowdfunding for ADC protocol support in PtokaX
26 April 2015 New support hub!
20 February 2015 - PtokaX 0.5.0.3 released...
13 April 2014 - PtokaX 0.5.0.2 released...
23 March 2014 - PtokaX testing version 0.5.0.1 build 454 is available.
04 March 2014 - PtokaX.org sites were temporary down because of DDOS attacks and issues with hosting service provider.

Main Menu

$ForceMove BugorNOT?

Started by [NL]Pur, 21 February, 2004, 22:19:15

Previous topic - Next topic

0 Members and 2 Guests are viewing this topic.

[NL]Pur

Whould be nice if i could redirect users from my first hub
running on port 411 too my second hub running on port 1200 with a script.

I tried using $ForceMove in the script but i get the message: *** Redirect request received to a hub that's already connected

greets,

Pur

tezlo

well did you specify the port? as in.. address:1200

[NL]Pur

yes

did you get this too work then ?

pHaTTy

seems to be redirect on port 411 (from) to another port then it has that error, else if u redirect say from port 111 to port 411 then its fine
Resistance is futile!

tezlo


[NL]Pur


tezlo

user:SendData("$ForceMove 127.0.0.1:444")

and this is what i get..
[20:39] *** Press the follow redirect button to connect to 127.0.0.1:444
[20:39] *** Disconnected
[20:39] *** Connecting to 127.0.0.1:444...
[20:39] *** Connected

[NL]Pur

did you also tested with your real IP ?

tezlo


[NL]Pur

which ptokax version ?

tezlo

#10
any ptokax version

[NL]Pur

seems i was testing with a old client again,

:(

so it isn't a ptokax bug :D

Skrollster

The problem is that you can't redirect someone from

myip.no-ip.com:411 ---> myip.no-ip.com:1000

because most clients handle this as you are trying to connect to a hub that you already are connected to... this means that

yoursip.no-ip.com:411 ---> myip.no-ip.com:1000

will work as long as you are not connected to myip.no-ip.com already...

did i make any sense?

[NL]Pur

it's clear too mee now

SMF spam blocked by CleanTalk