Contents

Introduction

Setup

FAQ

Troubleshooting

Web Application

Release Notes

Download

Language

English

Japanese

 

Info

Home

Home (alt.)

FAQ

Q1. What channel modes are available in the DICE?
Q2. What is "Excess Flood"?
Q3. What is DICE Manager?
Q4. What is OpenNap?
Q5. Why is there no "you are banned" message in OpenNap? Can I know if I'm banned or not in OpenNap?
Q6. What is IRC User Shell?
Q7. Can I redistribute a DICE package?
Q8. What is the difference between the evaluation version and the full version of the DICE?
Q9. Is there any difference between chat from IRC clients and from opennap clients? What happened to those '='-prefixed-nick users?
Q10. Can I open a new channel by an opennap client?
Q11. I got the "DCC is blocked" message. Can I use DCC in the DICE?
Q12. Why does it show idle time in an IRC /whois result as always zero?
Q13. My new channel doesn't show up on the list.
Q14. When I login to DICE IRC I got a port scan alert. What's happening?
Q15. Can I link multiple DICE servers?
Q16. What can I do for my PC to improve DICE performance?
Q17. Are there any security features in the DICE?
Q18. I want to make a channel sticky.
Q19. I encounter too many "excess flood" kills in IRC.

 

 

Q1. What channel modes are available in the DICE?

The available channel modes are:

+a: anonymous
+b
: set a ban mask
+c
: channel members only (available for registered channels)
+e
: ban exempt
+i
: invite only
+k: key required
+l: limited number of users
+m: moderated; only operators/voicers can talk
+r: user with a registered account only
+s: secret; doesn't appear on whois or the channel list
+z: SSL-user only

In the default state, only operators can change the topic (traditional +t), and external channel messages are ignored (traditional +n). Members of registered channels are immune from channel restrictions such as +k/+i. Invited users to a +i channel lose admission after they leave the channel.

OpenNap users can't join +a/+i/+k channels.

The available channel user modes are:

+o: channel operator
+v: channel voicer
+d: silent user

Channel user modes are mutually exclusive. It means you can't be an operator and a voicer at the same time.

Channel operators can control various properties of a channel. Voicers are special users who can speak in a +m channel. The server gives +o/+v to a registered operator/voicer when they join a channel.

While +o and +v have a positive effect, a user with +d is forced to be mute in a channel. It's basically opposite to the +m channel mode in which no user except for +o/+v can speak. +b sets +d onto a banned user in a channel if that person is not yet kicked out. Though the IRC standard states banned users can't speak in a channel, the DICE allows an operator to set -d on banned users. In other words, +b in the DICE is composed of channel access control (+b) and speech control (+d), and one of them can be turned on and off separately.

 

Q2. What is "Excess Flood"?

It means that a client issued too many messages in a short time and the server killed that user to reduce server load. You should be careful not to flood since at the third "excess flood" the IP address of a flooding user is banned automatically. Some IRC scripts that do background jobs may result in flooding, so watch out how they work under the hood.

 

Q3. What is DICE Manager?

Though most of administration tasks can be done via the web UI by a web browser, it's still better for security to force some of fundamental settings of the DICE require administrator privileges in the context of Windows. DICE Manager is a Windows desktop application that work as a simple shell for such tasks.

 

Q4. What is OpenNap?

The OpenNap supported in the DICE is actually a stripped-down version of a protocol known as OpenNap that basically acts as a simple file sharing hub for OpenNap clients. In the DICE, administration commands and unnecessary information about users and files are removed while bindings to IRC is added. For example, OpenNap users can enter an IRC channel and can exchange private messages with IRC users too. Also you can allow OpenNap queries only for users joining in a certain channel.

 

Q5. Why is there no "you are banned" message in OpenNap? Can I know if I'm banned or not in OpenNap?

To minimize the security risk, automatic ban in the DICE doesn't notice banned users about what actually went wrong. Abusers tend to rely on information provided by a target.

 

Q6. What is IRC User Shell?

In DICE IRC, all user services are accessible through the "/shell" command (Type "/shell" in the command line in an IRC client). Common IRC servers such as Unix IRCd are backed up by several services that are running in the outside of an IRC server process and users interact with them independently ("nickserv", "chanserv", "memoserv", proxy-scanner service). In the DICE, users can access all functions including administration commands via the IRC User Shell of which account is created and managed in the web UI. IRC users are authenticated by a registered nickname and a password for IRC.

 

Q7. Can I redistribute a DICE package?

As long as you don't modify the archive for it, you can redistribute it. Distributing older versions are not recommended though since they are out of support. Please refer to the license document in the package for details.

 

Q8. What is the difference between the evaluation version and the full version of the DICE?

The IRC server function is limited in the evaluation version whereas all functions are available in the full version. In the evaluation version, IRC users can't use their own nick names. Other parts are basically identical. If you find the IRC server function in the DICE valuable, please purchase the full version.

 

Q9. Is there any difference between chat from IRC clients and from opennap clients? What happened to those '='-prefixed-nick users?

IRC clients can create channels freely while opennap clients can't. Opennap clients can't join in restricted types of channels (+i/+k/+r) except for a +l channel. Users with '=' at the head of their nicks are users from the other side (IRC users seen from opennap users, opennap users seen from IRC users). You can send private messages to users in the other side with '='-prefixed nicks. IRC User Shell is available only for IRC users.

 

Q10. Can I open a new channel by an opennap client?

To prevent creation of op-less channels, you can't. Use an IRC client or the Web IRC Client.

 

Q11. I got the "DCC is blocked" message. Can I use DCC in the DICE?

Type "/shell set dcc" in the IRC-User Shell and you'll see how-to. A recipient of a DCC request has to set DCC block off or has to add a sender to the DCC whitelist if DCC block is enabled.

 

Q12. Why does it show idle time in an IRC /whois result as always zero?

It's intentionally set zero to hide users' activity from unsolicited inspectors. If you have to notice others that you are alive do it yourself.

 

Q13. My new channel doesn't show up on the list.

The channel list is updated by the interval set in the configuration in the web UI.

 

Q14. When I login to DICE IRC I got a port scan alert. What's happening?

They are done to check spoofing via insecure proxy servers. If you don't have unnecessary ports open there's no problem.

 

Q15. Can I link multiple DICE servers?

No you can't for the moment.

 

Q16. What can I do for my PC to improve DICE performance?

You may find where the bottleneck of your system is by watching the Performance Monitor of your Windows. If the bottleneck is in the CPU, it's a good idea to use a faster multi-core processor or a multi-processor setup. Fast and high-bandwidth RAM will also help. Faster HDD is also important for a web server.

Another possible bottleneck is the network. In the OS side, network performance and other Windows kernel activity can be slightly optimized by tweaking TCP/IP-related Windows registry; check out MS Knowledge Base for details. In the hardware side, if your PC is behind a router, you should check how many concurrent sessions it can handle. If network bandwidth is not enough (especially in aggressive use of OpenNap), it may be the time to upgrade your internet connection.

 

Q17. Are there any security features in the DICE?

All failed login and flooding are logged in the activity log found in the "log" folder in the DICE application data folder. You can figure out what's going on in your server by scanning it. Login lockdown helps to discourage brute-force crackers. Automatic ban will decrease resource consumption by DoS attacks. Of course you should apply security patches released by Microsoft to your Windows OS as quickly as possible to keep it up-to-date.

 

Q18. I want to make a channel sticky.

Use the command "/shell admin bot" and let a bot join in the channel.

 

Q19. I encounter too many "excess flood" kills in IRC.

Adjust the "IRCExcessFloodThresholdLines" value in the DICE configuration.