This is a firewalling system based on SOCKS. After adding a binding for your IP, you connect to the eggdrop and it will relay your connection to whatever hostname and port you specified. It will make your username@host.name look exactly the same as your bot's. That will keep people from seeing your real IP address, and hence, will not be able to winnuke, ssping, click nuke, ICMP echo flood, UDP flood, port flood, or any of the other generally bad things that can be done to ones machine when knowing it's IP. To use this, edit the variables below and load into your eggdrop. To use the firewall, you must create a firewall binding, or something that tells where a specific IP is supposed to redirected to. If you want to have a connection from you (174-250-34.ipt.aol.com) firewalled to irc.server.net on port 6667, you would type on the party line: .firewall add 174-250-34.ipt.aol.com irc.sprynet.com 6667 The eggdrop would reply with something like this: 152.174.250.34 -> 165.121.1.46:6667 added to firewall bindings In this version of Firewall, IP addresses are used for security purposes. At that point, you'd just have to connect to your eggdrop on the port that you specified in the script, and you'd be firewalled to irc.sprynet.com on port 6667. Only people from your IP address would be able to use it. You would be able to have as many sessions as you liked at one time. You are allowed to create as many bindings as you want, but easy one has to have a different IP address. To list current firewall bindings, simply type: .firewall list To remove a binding (or multiple bindings), type: .firewall delete 152.174.250.34 You are allowed to use wildcards, such as "152.*" with the delete command. You have use the IP address in the delete command, it won't recognize hosts. To get help on the command and other options, type either: .firewall or: .firewall such as: .firewall add BUGS: Occasionally get false \"does not exist!\" error. Cause: Unknown, suspected to be an error in \"host.\" Fix: Simply repeat the command There is a small chance that "\Port F*ck\"-style attacks MAY cause the eggdrop to crash. Cause: An idx that existed after the checking of idx existance but closed by by peer before eggdrop could close it; normally wouldn't do anything ot her than cause a TCL error, but because of a bug in eggdrop it crashes the entire thing without even a core dump or DEBUG file. Fix: Set firewall_port to something that hackers aren't likely to find. Firewall list lost whenever the bot is .rehash'ed or .restart'ed. Cause: The firewall variable is reinitialized. Fix: Don't rehash the bot :) NEXT VERSION: Improvement to .firewall delete Wildcards allowed Hostmasks as well as IP addresses used. Faster connection authetication and establishment Faster firewall data transfer