Duplicate IP Control

[Questman]

Yeah Mud Magic needs a lot of work. Thinking of other handy things a utility that writes the IP (say into the company slot and can't be editted) and then an option only to allow 3 of the same IP's to connect at a time....some thing like the Control module. (for WG2.0)

i have one that allows X amount of connections per IP and also utilities to list clients, etc.....

i think Rick has something similiar to that too as did adventurecomm.

Adventurecomm didn't, but I wrote one custom... for someone on here, I think.. but it's ELWDIPC now.

WHAT IS DUPLICATE IP CONTROL?

Duplicate IP Control is a simple but powerful utility that lets you specify
how many connections can come from a single IP address. Once the threshold
is reached, Duplicate IP Control can disconnect one of the sessions. It
also can warn users who repeatedly offend, and optionally, ban them once
they reach an abuse threshold. Some users can be exempted from the limits.

CONFIGURATION

There are a few things you'll want to configure before starting.

1. Security

Duplicate IP Control allows you to specify a key that a user may possess to
exempt him/her from the connection threshold. Users with this key can login
from the same IP as many times as they wish. If you want to set this key,
set DIPCXKEY.

The module also allows you to specify a ban-op that can access the module's
menu, run reports, and work with the ban lists. Sysops will always have
access to the module's menu. If you'd like to specify a key to let non-Sysop
users access the module, set DIPCMKEY.

2. Duplicate IP Control

One thing you must check before starting is the WHICHTCP setting. This
setting specifies which TCP/IP product you are using - Galacticomm's ICO or
Vircom's Major TCP/IP. Set this correctly.

NUMSESS allows you to specify how many duplicate sessions may exist. Set
this value between 0 and 10. Setting this to zero effectively disables
the module's duplication checks, although it will continue to check against
banned IP address lists.

SESS2KIL lets you specify which session gets killed when the limit is
reached. This would either be the first (oldest) or last (current/newest)
session. You can also set it to None and not automatically disconnect users.

STOREVIO allows you to choose whether or not to store offending IP addresses.
If you say YES, you can then choose to set auto-ban thresholds.

If STOREVIO is YES, you can set AUTOBAN to YES to have the module ban
IP addresses that exceed BANLIMIT, which can be set to 0 through 100. Like
NUMSESS, if you set BANLIMIT to 0, it will never ban, but it will continue
to log the offending IP addresses.

VIOLIFE lets you choose how long to store a record of a duplicate IP. If
low, you will 'forget' about the violation sooner, leading to a reduced
likelihood of an autoban. Set it higher to increase likelihood of a ban.
Similarly, BANLIFE sets how long a ban will last. Each allow a setting of
0 which will never expire a violation/ban until you remove it.

There are other logging, auditing, and notification settings as well.

COMMANDS

The module's main menu allows a few options to the sysop and ban-op.

You can view reports on violating IPs, users, and banned IPs. You can
remove an IP or user from the violation list, and you can delete a ban.

You may also manually ban an IP address.

[Stoneslinger76]

WHAT IS DUPLICATE IP CONTROL?

Duplicate IP Control is a simple but powerful utility that lets you specify
how many connections can come from a single IP address. Once the threshold
is reached, Duplicate IP Control can disconnect one of the sessions. It
also can warn users who repeatedly offend, and optionally, ban them once
they reach an abuse threshold. Some users can be exempted from the limits.

CONFIGURATION

There are a few things you'll want to configure before starting.

1. Security

Duplicate IP Control allows you to specify a key that a user may possess to
exempt him/her from the connection threshold. Users with this key can login
from the same IP as many times as they wish. If you want to set this key,
set DIPCXKEY.

The module also allows you to specify a ban-op that can access the module's
menu, run reports, and work with the ban lists. Sysops will always have
access to the module's menu. If you'd like to specify a key to let non-Sysop
users access the module, set DIPCMKEY.

2. Duplicate IP Control

One thing you must check before starting is the WHICHTCP setting. This
setting specifies which TCP/IP product you are using - Galacticomm's ICO or
Vircom's Major TCP/IP. Set this correctly.

NUMSESS allows you to specify how many duplicate sessions may exist. Set
this value between 0 and 10. Setting this to zero effectively disables
the module's duplication checks, although it will continue to check against
banned IP address lists.

SESS2KIL lets you specify which session gets killed when the limit is
reached. This would either be the first (oldest) or last (current/newest)
session. You can also set it to None and not automatically disconnect users.

STOREVIO allows you to choose whether or not to store offending IP addresses.
If you say YES, you can then choose to set auto-ban thresholds.

If STOREVIO is YES, you can set AUTOBAN to YES to have the module ban
IP addresses that exceed BANLIMIT, which can be set to 0 through 100. Like
NUMSESS, if you set BANLIMIT to 0, it will never ban, but it will continue
to log the offending IP addresses.

VIOLIFE lets you choose how long to store a record of a duplicate IP. If
low, you will 'forget' about the violation sooner, leading to a reduced
likelihood of an autoban. Set it higher to increase likelihood of a ban.
Similarly, BANLIFE sets how long a ban will last. Each allow a setting of
0 which will never expire a violation/ban until you remove it.

There are other logging, auditing, and notification settings as well.

COMMANDS

The module's main menu allows a few options to the sysop and ban-op.

You can view reports on violating IPs, users, and banned IPs. You can
remove an IP or user from the violation list, and you can delete a ban.

You may also manually ban an IP address.

Works great and well worth the registration

[Drex]

Yeah Mud Magic needs a lot of work. Thinking of other handy things a utility that writes the IP (say into the company slot and can't be editted) and then an option only to allow 3 of the same IP's to connect at a time....some thing like the Control module. (for WG2.0)

I have a module like that - Duplicate IP Control.

Great program Rick, the only problem (a user mentioned to me) is that if they have 3 accounts online and freeze up they can no longer log in and us the Kill Ghost Account module. Any way around this problem?

[Questman]

Yeah Mud Magic needs a lot of work. Thinking of other handy things a utility that writes the IP (say into the company slot and can't be editted) and then an option only to allow 3 of the same IP's to connect at a time....some thing like the Control module. (for WG2.0)

I have a module like that - Duplicate IP Control.

Great program Rick, the only problem (a user mentioned to me) is that if they have 3 accounts online and freeze up they can no longer log in and us the Kill Ghost Account module. Any way around this problem?

I'm not sure I follow - can you describe what you mean by "freeze up" (is this the system freezing for some reason, like an error in a module?) and use the Kill Ghost Account module (what is that module? who/what kind of users want to use it?)

[dspain]

Yeah Mud Magic needs a lot of work. Thinking of other handy things a utility that writes the IP (say into the company slot and can't be editted) and then an option only to allow 3 of the same IP's to connect at a time....some thing like the Control module. (for WG2.0)

I have a module like that - Duplicate IP Control.

Great program Rick, the only problem (a user mentioned to me) is that if they have 3 accounts online and freeze up they can no longer log in and us the Kill Ghost Account module. Any way around this problem?

i have a wg 2.0 majorbbs.exe with the method 3.20 uses compiled within.
when ya logon if the user is already online it prompts for PW.
that would probably be the best way around it.

although i do have the old ghost kill source code, ill browse through it see why it wouldnt recognize a user.

[Drex]

I'm not sure I follow - can you describe what you mean by "freeze up" (is this the system freezing for some reason, like an error in a module?) and use the Kill Ghost Account module (what is that module? who/what kind of users want to use it?)

Some get timeouts tcp/ip errors and they can't do anything (now) before they could login with another account and kill thier own account online with the correct account password.

although i do have the old ghost kill source code, ill browse through it see why it wouldnt recognize a user.

Thanks, but Im thinking the DUP IP is overiding it....did check with a users tonightand he said he had problems getting back on with a 4TH account to kill other accounts. I allow 5 but onlt 3 on at a time and set that up in the dup ip module.

[Drex]

I found a work around for this problem, I created an account called Ghost and it has the bypass 3rd account IP block key, and has a time limit of 2 minutes online, so they should be able to kill thier ghosted account in that time limit.

[Questman]

Some get timeouts tcp/ip errors and they can't do anything (now) before they could login with another account and kill thier own account online with the correct account password.

So something unrelated to DIPC occurs; normally, the user comes back on and uses the Ghost Kill tooling to kill their prior login. But DIPC overrides, and is more strict.

Perhaps I should add an option to allow the session coming on to kill the previous session? Would that help? Obviously it would only let you kill your OWN logins; if you had > max sessions from an IP but multiple users, you can't boot someone else...

[dspain]

Some get timeouts tcp/ip errors and they can't do anything (now) before they could login with another account and kill thier own account online with the correct account password.

So something unrelated to DIPC occurs; normally, the user comes back on and uses the Ghost Kill tooling to kill their prior login. But DIPC overrides, and is more strict.

Perhaps I should add an option to allow the session coming on to kill the previous session? Would that help? Obviously it would only let you kill your OWN logins; if you had > max sessions from an IP but multiple users, you can't boot someone else...

i think compiling a catch in majorbbs.exe to do like NT does and if you logon with a userid already online prompt for password to disconnect, that way it never leaves the logon state which is where your IP control will pick up.


Login: Sysop

Sorry, But That User-ID Is Currently Connected, Please Type The
Password To End The Ghosted Connection.

Password: ********

Disconnecting %s .....

Welcome Back %s .....

[Drex]

Well no need for extrawork on my part, I am satisfied with the work around and the module itself.

[dspain]

Well no need for extrawork on my part, I am satisfied with the work around and the module itself.

you didnt get the memo? im a glutton for punishment.

i want all flavors of this product kicking good usage

wg 2.0 is still highly popular cause of module availability.

i got quite a few of my own im about to port down.

[Questman]

We have to get folks off the DOS version eventually.

[frcorey]

We have to get folks off the DOS version eventually.

hell no, we wont go...

[dspain]

We have to get folks off the DOS version eventually.

i try to push it on customers but they feel its more stable than any of the others.

[Questman]

That is more the fault of the add-ons than the system itself.

[Questman]

i think compiling a catch in majorbbs.exe to do like NT does and if you logon with a userid already online prompt for password to disconnect, that way it never leaves the logon state which is where your IP control will pick up.


Login: Sysop

Sorry, But That User-ID Is Currently Connected, Please Type The
Password To End The Ghosted Connection.

Password: ********

Disconnecting %s .....

Welcome Back %s .....

I recommend against patching the existing majorbbs.exe, even though it's the obvious easy low-hanging fruit. Simply because once we open that box it's difficult to close it, and then you have a nightmare of various exes...

I wrote this into DIPC last night. It works the same way NT's does; it actually works on NT too, but it's not very helpful since NT does it natively, but so what. Once I clean it up a bit more I'll push out a new version of DIPC with this feature.

I also will add Dan's request for a global that lists IPs - I already have the struct array holding this info so it's quite simple to implement.

I have a few other features long planned. Once all are implemented we'll make it v1.00.

I haven't been keeping the codebase compatible with BBSV6 or WG1. If there's interest in that I'd have to revert. v0.9.0 I think works with BBSV6... Frankly, though, I think anyone on BBSV6 or WG1 should upgrade to WG2. Its the same basic system but there are some enhancements to the API that are worthwhile.

[Questman]

Duplicate IP Control has a new version coming out.

So far, the following features were added:

- A "showips" global command that shows channel #, username, ip address, # of current violations for the IP, and last violation date. The global can be turned off, restricted by class, and its character configured (defaults to =showips).

- A Duplicate IP Control menu option that shows the same as the showips.

- The ability for users who are currently logged in but 'ghosted' to enter their password to end the previous login session. This will not cause them to be caught by the IP rules, as those will be applied after the previous session was knocked off. This works in Worldgroup 2 DOS, as well as the 3.2/3.3 version (although this functionality is built into those versions).

Currently considering adding:

- Option to log all sign-ups w/ date, time, username, IP, e-mail to the audit trail and/or a log (text) file
- Option to log all logins w/ date, time, username, IP to the audit trail and/or a log (text) file
- Option to switch the user's class once their IP is banned (or once their userid is banned) so that they can not log back in from another IP once they've reached a ban point. This would revert to the previous class once their ban is remove or expires.

Are any of these three options useful or interesting to any users or prospective users of Duplicate IP Control?

Are there any bugs that you are aware of with the operation of the module, or the Sysop menu?

[Drex]

Duplicate IP Control has a new version coming out.

So far, the following features were added:

- A "showips" global command that shows channel #, username, ip address, # of current violations for the IP, and last violation date. The global can be turned off, restricted by class, and its character configured (defaults to =showips).

- A Duplicate IP Control menu option that shows the same as the showips.

- The ability for users who are currently logged in but 'ghosted' to enter their password to end the previous login session. This will not cause them to be caught by the IP rules, as those will be applied after the previous session was knocked off. This works in Worldgroup 2 DOS, as well as the 3.2/3.3 version (although this functionality is built into those versions).

Currently considering adding:

- Option to log all sign-ups w/ date, time, username, IP, e-mail to the audit trail and/or a log (text) file
- Option to log all logins w/ date, time, username, IP to the audit trail and/or a log (text) file
- Option to switch the user's class once their IP is banned (or once their userid is banned) so that they can not log back in from another IP once they've reached a ban point. This would revert to the previous class once their ban is remove or expires.

Are any of these three options useful or interesting to any users or prospective users of Duplicate IP Control?

Are there any bugs that you are aware of with the operation of the module, or the Sysop menu?

Possibly option one to a log file, but then again before this module I would have to backtrack the audit trail to check out user's IP's as thier was no way of a search lookup, but not sure if that is needed anymore as the DUPIP catch's and locks any over your set limit. The other options you have added sound great.

[Stoneslinger76]

Duplicate IP Control has a new version coming out.

So far, the following features were added:

- A "showips" global command that shows channel #, username, ip address, # of current violations for the IP, and last violation date. The global can be turned off, restricted by class, and its character configured (defaults to =showips).

- A Duplicate IP Control menu option that shows the same as the showips.

- The ability for users who are currently logged in but 'ghosted' to enter their password to end the previous login session. This will not cause them to be caught by the IP rules, as those will be applied after the previous session was knocked off. This works in Worldgroup 2 DOS, as well as the 3.2/3.3 version (although this functionality is built into those versions).

Currently considering adding:

- Option to log all sign-ups w/ date, time, username, IP, e-mail to the audit trail and/or a log (text) file
- Option to log all logins w/ date, time, username, IP to the audit trail and/or a log (text) file
- Option to switch the user's class once their IP is banned (or once their userid is banned) so that they can not log back in from another IP once they've reached a ban point. This would revert to the previous class once their ban is remove or expires.

Are any of these three options useful or interesting to any users or prospective users of Duplicate IP Control?

Are there any bugs that you are aware of with the operation of the module, or the Sysop menu?

Cool, I was going to ask if you could add a "show ips" with username, channel and IP, similar to who's on. The option for change user class on first exceed max IP # would allow users to still login as demo and reply to sysop messages, ban on 2nd exceed ip max #.. The additional log feature would likely come in handy saveing the auditrail searches.

As far as bugs I havent found any.

[Stoneslinger76]

We have to get folks off the DOS version eventually.

i try to push it on customers but they feel its more stable than any of the others.

I have both running, WG 3.2NT is far more stable. Wg NT has not crashed or locked up yet this year, last August was the last time. Damm kreepy crawly spyders.

Wg 2 dos has crashed twice so far this year without anything writen to catastophy.txt I believe its related to Swath's interogation mode for tw2002, this doesnt happen in the nt version.

[dspain]

i think compiling a catch in majorbbs.exe to do like NT does and if you logon with a userid already online prompt for password to disconnect, that way it never leaves the logon state which is where your IP control will pick up.


Login: Sysop

Sorry, But That User-ID Is Currently Connected, Please Type The
Password To End The Ghosted Connection.

Password: ********

Disconnecting %s .....

Welcome Back %s .....

I recommend against patching the existing majorbbs.exe, even though it's the obvious easy low-hanging fruit. Simply because once we open that box it's difficult to close it, and then you have a nightmare of various exes...

I wrote this into DIPC last night. It works the same way NT's does; it actually works on NT too, but it's not very helpful since NT does it natively, but so what. Once I clean it up a bit more I'll push out a new version of DIPC with this feature.

I also will add Dan's request for a global that lists IPs - I already have the struct array holding this info so it's quite simple to implement.

I have a few other features long planned. Once all are implemented we'll make it v1.00.

I haven't been keeping the codebase compatible with BBSV6 or WG1. If there's interest in that I'd have to revert. v0.9.0 I think works with BBSV6... Frankly, though, I think anyone on BBSV6 or WG1 should upgrade to WG2. Its the same basic system but there are some enhancements to the API that are worthwhile.

yeah that was a last stand option i think ill just re-release my old ghosting program, question, does the IP check kick in after logon? or does it also count if in classes SUPIPG, SUPLON, and SUPLOF?

cause if it counts after logon i can intercept a logon by a particular userid and do the enter password ghost kill before passing to ACTUSR.

[Questman]

No, the password-to-logoff feature does not wait until login; it intercepts the login handler. It does exactly what the Ghost Kill module does.

It doesn't count until the user is logged in for DIP purposes.

[Stoneslinger76]

Would it be possible in the next version to add max ip by user class?

eg
demo 1 IP
normal 2 IP
PAY 4 IP

Also a who's on by IP and uid.

[dspain]

Would it be possible in the next version to add max ip by user class?

eg
demo 1 IP
normal 2 IP
PAY 4 IP

Also a who's on by IP and uid.

theres a text var to show client IP

[Stoneslinger76]

Would it be possible in the next version to add max ip by user class?

eg
demo 1 IP
normal 2 IP
PAY 4 IP

Also a who's on by IP and uid.

theres a text var to show client IP

I know the varaible, what I mean is DupeIP allow for users in higher class levels to be possible to have 3 or 4 similtaneous conections before being banned and demo user has 1 IP maximum.

[dspain]

Would it be possible in the next version to add max ip by user class?

eg
demo 1 IP
normal 2 IP
PAY 4 IP

Also a who's on by IP and uid.

theres a text var to show client IP

I know the varaible, what I mean is DupeIP allow for users in higher class levels to be possible to have 3 or 4 similtaneous conections before being banned and demo user has 1 IP maximum.

yeah i was just referring to the listing uid and ip i wrote a utility like that for someone on here a while back.

CH# User-ID IP Address Duration

003 Sysop 192.168.1.104 3m

[ccs]

No, the password-to-logoff feature does not wait until login; it intercepts the login handler. It does exactly what the Ghost Kill module does.

It doesn't count until the user is logged in for DIP purposes.

My ver of this program stopped working. Do you have an updated release?

Joe

[Ragtop]

Think I am going to need this app soon. Starting to get a few dupe accounts on. I have looked around some boards but haven't been able to find it. Where can I get it and how much is registration?

[Drex]

You can check with Rick on the current price.

questman(AT)themajorbbs.com

[Stoneslinger76]

Think I am going to need this app soon. Starting to get a few dupe accounts on. I have looked around some boards but haven't been able to find it. Where can I get it and how much is registration?

Its avaible on my bbs if you cant find it elsewhere, ELWDIPC.ZIP v0.90b for
3.xxNT I believe the regisration was 20-25 bucks see the register.me

[Questman]

Yeah, it's only $25.

That's a good idea - to separate maximum dupes by class.

[Ragtop]

Hey Questman,
Did you get my email about registering this module along with the others we had talked about? The docs don't say where to send the registration fee so I will need that from you. Will send it as soon as you let me know.
Thanks,
Ragtop

[Questman]

Hey Questman,
Did you get my email about registering this module along with the others we had talked about? The docs don't say where to send the registration fee so I will need that from you. Will send it as soon as you let me know.
Thanks,
Ragtop

Not sure. Send again, maybe?

[Ragtop]

Ok, I sent it again. Thanks for all you've done for our community. Hope sometime I can help give back a little

[Stoneslinger76]

Yeah, it's only $25.

That's a good idea - to separate maximum dupes by class.

Have you managed to find some time to add the maximum ip number by class yet?

[Questman]

No - sort of forgot about it

Been really busy at work again - loooooooooong hours.

[Questman]

I've done the following:

- Global command and menu option to list users w/ IP address
- Ghost Kill
- Log signups and logins to a database (menu option to query them is coming soon)

I need someone who is running v3.3 to help me test a few things. On my dev box, 3.3 is not loading the modules I compiled with Borland C++ 5.5.1 (claims it can't find them) but 3.2 is. That version of the compiler was never used during Galacticomm's time, but it's the oldest compiler that will compile SQLite and GALSQL and any module that uses it.

If you are willing to try e-mail me (questman at themajorbbs d0t com)

[Ragtop]

Sounds great! I checked on Elwynor and the new file wasn't there. Where can I find it? I would love to upgrade to this new version.

[Questman]

I should have put 0.9.2 online for upgrade. I'm on 0.9.3 - I just need to put the metrics queries in the menu - and then I can put it out.

But I need someone who is running v3.3 to help me first by installing a small internal DLL and seeing if your BBS starts with it.

[Drex]

Upgrades sound great! Will this also be coming out for the WG2.0 I have?

[Ragtop]

Wish I could help. Running 3.2 here. I will see if I can get 3.3 loaded on a separate computer. If I can get it going, I can test it for you.

[Stoneslinger76]

I should have put 0.9.2 online for upgrade. I'm on 0.9.3 - I just need to put the metrics queries in the menu - and then I can put it out.

But I need someone who is running v3.3 to help me first by installing a small internal DLL and seeing if your BBS starts with it.

I can test it for you, on my dev server first, then live. Just email it or let me know where to DL.

[Questman]

I solved the 3.3 problem. It wasn't a problem with 3.3, it was that my test box didn't have a DLL on it. Ooooooops!

All of these features will be available in WG2 version EXCEPT for the login/signup data collection and queries. I planned to use the GALSQL dll for that piece, which isn't supported in WG2. GALSQL requires BC++ 5.5; WG2 was 4.5, and WG3 itself was only 5.0...

[Ragtop]

Is the latest version (or at least something newer than 0.9.1) of this available anywhere? I'd like to be able to use the global with IP option but it isn't available in 0.9.1. I tried using the beta version but it crashes the board during startup.

[ccs]

No, the password-to-logoff feature does not wait until login; it intercepts the login handler. It does exactly what the Ghost Kill module does.

It doesn't count until the user is logged in for DIP purposes.

My ver of this program stopped working. Do you have an updated release?

Joe

Any word on the WG2.0 ver?

Joe

[Questman]

Send me a quick e-mail to questman (at) themajorbbs.com and let's try to refresh my memory. The latest DLL I've compiled for DOS was 4/2009.

[Ragtop]

Hey Questman!
Good to see you back. I'm trying to upgrade to the newest version of Dupe IP but haven't been able to find it. Can you help please? Currently running 0.9.1

[Questman]

Sure - are you a DOS user or NT?

Send me a note - info at elwynor dot com

[Ragtop]

Running 3.2NT. I sent an email to your address and replied here too, in case you check here first Thanks for your help.

[dspain]

Sure - are you a DOS user or NT?

Send me a note - info at elwynor dot com

speaking of dos you took a crack at wg2 for freedos yet?