DDOS protection is broken in 0.4.0.0c
 

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

DDOS protection is broken in 0.4.0.0c

Started by eagle00789, 22 March, 2008, 01:47:56

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

eagle00789

When setting the DDos protection to OFF and save the settings, it is saved. when you close ptokax and restart ptokax, the setting is back to ON.i have posted a videoproof of this bug: YouTube

PPK

That is not bug, it is not saved. This change was forced by stupid hub owner of public PtokaX hub who disable that and team elite used his users to attack me.
"Most of you are familiar with the virtues of a programmer. There are three, of course: laziness, impatience, and hubris." - Larry Wall

eagle00789

#2
so how to fix this, because this setting is enabled, i can't connect to my own hub anymore.
[edit] i run the server on the same machine as the client. connecting to the server-address doesn't work for me [/edit]

eagle00789

#3
Quote from: Mutor on 22 March, 2008, 02:25:29
There are a number of options for you.
I run multiple hubs and clients on the same box, I can connect
from any to any using LAN or WAN addresses

  • Configure your connection properly [if loop back allowed
  • Upgrade your router [if loop back is not allowed
  • Disable the check IP in commands profile permission
check ip is already disabled for my userprofile. this worked before. but since this new option, i'm not allowed anymore. (if i disable this setting, i have to exit the hub, as ptokax runs as a service here)
how to configure my connection to allow loopback. my router and modem doesn't support loopback and upgrade is not possible as they both run the latetst versions of the software

PPK

Checked and enabling "Don't check IP in DC commands" for profile working for me ::)
"Most of you are familiar with the virtues of a programmer. There are three, of course: laziness, impatience, and hubris." - Larry Wall

eagle00789


SMF spam blocked by CleanTalk