VERLUHUB - LINUX STRICT - NMDC. [ ACTIVE ].

[Admin]

Low ram usage and low on CPU.

Fully supported - any version will do just fine.
Get the latest version here:
https://github.com/verlihub

else to avoid exploits:

Verlihub 0.9.8C and older
To determine the hub to ignore wrong CTM's: !set check_ctm 1
To determine the hub to check CTM's and kick the user: !set check_ctm 3
To determine the hub to check active searches: !set check_asearch 1
To determine if the hub is set up correctly: !getconfig
Verlihub 0.9.8D and newer
To determine the hub to check CTM's and kick the user: !set check_ctm 1
To determine the hub to check active searches: !set check_asearch 1
To determine if the hub is set up correctly !getconfig

We will remove all hubs running verlihub versions lower than 0.9.8e-rc2 soon.
So please update!

[Admin]

Looks like Verlihub Version: 2.0.0-RC1 and 2.0.0.0 is somewhere outhere.
Not publically released yet.
Shows up in our stats

[CyberGhost404]

Hi, this software use Verlihub 1.1.0.41 version =)

[Admin]

Hublist support
There are some variables of the hub configuration that are sent to hublist pinger when it enters in the hub. These are:

hub_name: the name of the hub
hub_desc: the description of the hub
hub_category: the category of the hub (this is only used by dchublist pinger)
hub_host: the address and port of the hub (you can omit 411 default port if you want)
min_share: minimum value of share that user must have to join
min_slot: minimum value of slot that user must have to join
max_hubs: maximum number of allowed hubs
hub_owner: the owner if the hub
VerliHub has also a very simple hublist registering support for those hublists that have a registration server. Use the following variables to setup hublist registration:

hublist_host: a list of hublist registering host separated by space (reg.dchublist.org + whatever else you want).
hublist_port: the port of the registration server (port 2501 is the default one)
You can manually register the hub by using the following command:

!hublist
VerliHub is also capable of automatically register the hub every each interval of time. The variable timer_hublist_period specify the time in seconds that VerliHub should wait to between two hublists registrations. For example if you want to register your hub every 10 minutes use:

!set timer_hublist_period 600
Automatic registration is disabled by default. If you would like to disable it again use the value 0.
.......

We have 2 versions of hublist servers here - currently in use ver 1. won't take any verlihubs regs if option hublist_send_minshare =1 . Please set it to 0.

2nd server is in production - it will take verlihub's regs no matter what settings are. Just need to enter dchublist.org:2501 as hublist regserver address and use command !hublist to reg manually (once) or set it to auto !set timer_hublist_period 600

[Admin]

Verlihub 1.2.0.5 and later TLS 1.3 now possible via go-lang programming.

https://github.com/Verlihub/tls-proxy

Expect double of connections while running this stuff.