22 Aug, 2007, blueice wrote in the 1st comment:
Votes: 0
> ban site
[36] no (65) Tue Jul 24 20:16:57 2007 Gohan -1 *charter.com

>last fromhost charter.com
Zeranamu Jul. 28th at 19:08:57 71-80-206-202.dhcp.mdfd.or.charter.com
Sidd Jul. 29th at 22:50:29 24-177-157-111.dhcp.mrqt.mi.charter.com
Tyrael Jul. 31st at 03:18:04 68-191-248-210.dhcp.oxfr.ma.charter.com
Winzaar Aug. 02nd at 01:16:48 66-169-181-51.dhcp.ftwo.tx.charter.com
Ness Aug. 15th at 17:50:59 68-184-40-194.dhcp.oxfr.ma.charter.com
Winzaar Aug. 17th at 04:05:34 66-169-181-51.dhcp.ftwo.tx.charter.com
Lyon Aug. 17th at 14:44:47 24-181-225-203.dhcp.oxfr.ma.charter.com
Lyon Aug. 18th at 03:44:31 71-10-229-61.dhcp.oxfr.ma.charter.com
Bodaki Aug. 18th at 08:50:38 66-214-75-144.dhcp.mrba.ca.charter.com

does anyone have any idea exactly why this is not working?
22 Aug, 2007, Zeno wrote in the 2nd comment:
Votes: 0
Best bet might to be use gdb to step through the ban code.
22 Aug, 2007, Guest wrote in the 3rd comment:
Votes: 0
Because the Smaug ban code is a pile of crap and really needs to be tossed out and redone. I've had spotty performance from banning in the few cases it's been necessary. Sometimes they stick. Sometimes they don't. The DNS resolution doesn't quite work out. Always some little thing. And the code is just a big fat mess to try and maintain.
23 Aug, 2007, Remcon wrote in the 4th comment:
Votes: 0
Just testing out ban on mine to see.
Banned sites:
[ #] Warn (Lv) Time By For Site
—- —- —- ———————— ————— —- —————
[ 1] no (100) Wed Aug 22 9:06:41PM 2007 Remcon -1 *0.1

telnet 6000
Connected to localhost.localdomain (
Escape character is '^]'.
Your site has been banned from this Mud.
Connection closed by foreign host.

Worked like it should have for now at least lol.
23 Aug, 2007, Conner wrote in the 5th comment:
Votes: 0
Yes, but Remcon, the issue is if you ban by name, banning by IP should work because it's not having to resolve the IP to determine the IP. :sad:
23 Aug, 2007, Mister wrote in the 6th comment:
Votes: 0
You can't ban by name, unless you wait until the name is resolved before checking for a ban.

I guess that's why some muds output "Making a dns lookup, please wait" if you type your name too fast on login.
23 Aug, 2007, blueice wrote in the 7th comment:
Votes: 0
well from what i can tell the character is just creating before their dns can be looked up, otherwise the dns wouldn't be showing up in my login history, it would simply be an ip address. so i'm just gonna add check_ban to more than one part of the nanny function and also in my update handler, that should at least solve my problem of keeping people banned.