]>
Commit | Line | Data |
---|---|---|
3bd189cb JR |
1 | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> |
2 | <HTML> | |
3 | <HEAD> | |
4 | <TITLE> [IRCServices] Chanserv UNBAN Bug | |
5 | </TITLE> | |
6 | <LINK REL="Index" HREF="index.html" > | |
7 | <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Chanserv%20UNBAN%20Bug&In-Reply-To=1b0cfe51b09426.1b094261b0cfe5%40shaw.ca"> | |
8 | <META NAME="robots" CONTENT="index,nofollow"> | |
9 | <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> | |
10 | <LINK REL="Previous" HREF="004238.html"> | |
11 | <LINK REL="Next" HREF="004239.html"> | |
12 | </HEAD> | |
13 | <BODY BGCOLOR="#ffffff"> | |
14 | <H1>[IRCServices] Chanserv UNBAN Bug</H1> | |
15 | <B>Andrew Church</B> | |
16 | <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Chanserv%20UNBAN%20Bug&In-Reply-To=1b0cfe51b09426.1b094261b0cfe5%40shaw.ca" | |
17 | TITLE="[IRCServices] Chanserv UNBAN Bug">achurch at achurch.org | |
18 | </A><BR> | |
19 | <I>Sun Apr 18 18:38:04 PDT 2004</I> | |
20 | <P><UL> | |
21 | <LI>Previous message: <A HREF="004238.html">[IRCServices] Chanserv UNBAN Bug | |
22 | </A></li> | |
23 | <LI>Next message: <A HREF="004239.html">[IRCServices] Chanserv UNBAN Bug | |
24 | </A></li> | |
25 | <LI> <B>Messages sorted by:</B> | |
26 | <a href="date.html#4245">[ date ]</a> | |
27 | <a href="thread.html#4245">[ thread ]</a> | |
28 | <a href="subject.html#4245">[ subject ]</a> | |
29 | <a href="author.html#4245">[ author ]</a> | |
30 | </LI> | |
31 | </UL> | |
32 | <HR> | |
33 | <!--beginarticle--> | |
34 | <PRE>><i>As I figured from the version change log, this issues has not been fixed and still produces the same effect on .30 | |
35 | </I> | |
36 | You're using Unreal, yes? I looked into the problem, and it seems | |
37 | that Unreal is applying bans based on client IP address as well as real and | |
38 | fake hostmasks. The problem with this is that the Unreal protocol doesn't | |
39 | send client IP addresses to other servers (Services included), so Services | |
40 | doesn't have any way to tell whether a given ban will match a client's IP | |
41 | address. In short, you're SOL unless you can switch to another ircd. I'll | |
42 | note this in the FAQ for the next release. | |
43 | ||
44 | --Andrew Church | |
45 | <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">achurch at achurch.org</A> | |
46 | <A HREF="http://achurch.org/">http://achurch.org/</A> | |
47 | ||
48 | ||
49 | </PRE> | |
50 | ||
51 | <!--endarticle--> | |
52 | <HR> | |
53 | <P><UL> | |
54 | <!--threads--> | |
55 | <LI>Previous message: <A HREF="004238.html">[IRCServices] Chanserv UNBAN Bug | |
56 | </A></li> | |
57 | <LI>Next message: <A HREF="004239.html">[IRCServices] Chanserv UNBAN Bug | |
58 | </A></li> | |
59 | <LI> <B>Messages sorted by:</B> | |
60 | <a href="date.html#4245">[ date ]</a> | |
61 | <a href="thread.html#4245">[ thread ]</a> | |
62 | <a href="subject.html#4245">[ subject ]</a> | |
63 | <a href="author.html#4245">[ author ]</a> | |
64 | </LI> | |
65 | </UL> | |
66 | ||
67 | </body></html> |