]>
Commit | Line | Data |
---|---|---|
3bd189cb JR |
1 | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> |
2 | <HTML> | |
3 | <HEAD> | |
4 | <TITLE> [IRCServices Coding] Unreal and akill excludes | |
5 | </TITLE> | |
6 | <LINK REL="Index" HREF="index.html" > | |
7 | <LINK REL="made" HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Unreal%20and%20akill%20excludes&In-Reply-To="> | |
8 | <META NAME="robots" CONTENT="index,nofollow"> | |
9 | <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> | |
10 | <LINK REL="Previous" HREF="003024.html"> | |
11 | <LINK REL="Next" HREF="003030.html"> | |
12 | </HEAD> | |
13 | <BODY BGCOLOR="#ffffff"> | |
14 | <H1>[IRCServices Coding] Unreal and akill excludes</H1> | |
15 | <B>Craig McLure</B> | |
16 | <A HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Unreal%20and%20akill%20excludes&In-Reply-To=" | |
17 | TITLE="[IRCServices Coding] Unreal and akill excludes">Craig at chatspike.net | |
18 | </A><BR> | |
19 | <I>Tue Apr 27 17:48:21 PDT 2004</I> | |
20 | <P><UL> | |
21 | <LI>Previous message: <A HREF="003024.html">[IRCServices Coding] is this a bug | |
22 | </A></li> | |
23 | <LI>Next message: <A HREF="003030.html">[IRCServices Coding] OperServ help | |
24 | </A></li> | |
25 | <LI> <B>Messages sorted by:</B> | |
26 | <a href="date.html#3026">[ date ]</a> | |
27 | <a href="thread.html#3026">[ thread ]</a> | |
28 | <a href="subject.html#3026">[ subject ]</a> | |
29 | <a href="author.html#3026">[ author ]</a> | |
30 | </LI> | |
31 | </UL> | |
32 | <HR> | |
33 | <!--beginarticle--> | |
34 | <PRE>Theres been some discussion recently about how Unreal wont send user information properly between servers, the chances are, that akill exclusions have been removed because of this. | |
35 | ||
36 | Quoting Andrew Church: | |
37 | You're using Unreal, yes? I looked into the problem, and it seems | |
38 | that Unreal is applying bans based on client IP address as well as real and | |
39 | fake hostmasks. The problem with this is that the Unreal protocol doesn't | |
40 | send client IP addresses to other servers (Services included), so Services | |
41 | doesn't have any way to tell whether a given ban will match a client's IP | |
42 | address. In short, you're SOL unless you can switch to another ircd. I'll | |
43 | note this in the FAQ for the next release. | |
44 | ||
45 | This was an issue with Chanserv unban. But i'm guessing the same problem would exist with akill exceptions. | |
46 | ||
47 | /**************************************** | |
48 | * Craig "FrostyCoolSlug" McLure | |
49 | * InspIRCd - <A HREF="http://www.inspircd.org">http://www.inspircd.org</A> - REVIVED | |
50 | * ChatSpike - <A HREF="http://www.chatspike.net">http://www.chatspike.net</A> | |
51 | ****************************************/ | |
52 | ||
53 | ||
54 | /**************************************** | |
55 | * From - Arathorn <<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">arathorn at theonering.net</A>> | |
56 | * To - <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">ircservices-coding at ircservices.za.net</A> <<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">ircservices-coding at ircservices.za.net</A>> | |
57 | * Sent - 2004-04-28 00:04:18 | |
58 | * Subject - Re: [IRCServices Coding] Unreal and akill excludes | |
59 | ****************************************/ | |
60 | ||
61 | /****** - Begin Original Message - ******/ | |
62 | ||
63 | ><i>----- Original Message ----- | |
64 | </I>><i>From: "Andrew Church" <<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">achurch at achurch.org</A>> | |
65 | </I>><i>To: <<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">ircservices-coding at ircservices.za.net</A>> | |
66 | </I>><i>Sent: Friday, April 02, 2004 4:12 AM | |
67 | </I>><i>Subject: Re: [IRCServices Coding] Unreal and akill excludes | |
68 | </I>><i> | |
69 | </I>><i> | |
70 | </I>>><i> >I can't get them to work. It sends a gline if someone matches an akill = | |
71 | </I>>><i> >whether or not there's an exclude on it. This of course makes excludes = | |
72 | </I>>><i> >useless. | |
73 | </I>>><i> | |
74 | </I>>><i> Fixed, thanks for the report. | |
75 | </I>>><i> | |
76 | </I>>><i> --Andrew Church | |
77 | </I>><i> | |
78 | </I>><i>Hm, I'm probably completely missing a critical part of this thread, but in | |
79 | </I>><i>ircservices-5.0.30.diff: | |
80 | </I>><i> | |
81 | </I>><i>diff -uNr ircservices-5.0.29/modules/protocol/unreal.c | |
82 | </I>><i>ircservices-5.0.30/modules/protocol/unreal.c | |
83 | </I>><i>--- ircservices-5.0.29/modules/protocol/unreal.c 2004-03-24 19:23:26 | |
84 | </I>><i>+0900 | |
85 | </I>><i>+++ ircservices-5.0.30/modules/protocol/unreal.c 2004-04-14 11:33:36 | |
86 | </I>><i>+0900 | |
87 | </I>><i>@@ -889,10 +895,6 @@ | |
88 | </I>><i> } else { | |
89 | </I>><i> /* Successfully parsed */ | |
90 | </I>><i> unreal_version = ver; | |
91 | </I>><i>- /* Unreal 3.2 (protocol version 2303) and above support | |
92 | </I>><i>- * autokill exclusions, so make a note of that */ | |
93 | </I>><i>- if (ver >= 2303) | |
94 | </I>><i>- protocol_features |= PF_AKILL_EXCL; | |
95 | </I>><i> } | |
96 | </I>><i> } | |
97 | </I>><i> | |
98 | </I>><i>doesn't this completely remove support for akill excludes in unreal? Have | |
99 | </I>><i>they been given up on as a lost cause, or can I re-flag support for them in | |
100 | </I>><i>unreal.c? Apologies if i'm failing to find an explanatory post on the lists | |
101 | </I>><i>or missing something in the Changelog, | |
102 | </I>><i> | |
103 | </I>><i>cheers, | |
104 | </I>><i> | |
105 | </I>><i>A. | |
106 | </I>><i> | |
107 | </I>><i>________________________________________________________________ | |
108 | </I>><i>Matthew Hodgson <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">arathorn at theonering.net</A> Tel: +44 7968 722968 | |
109 | </I>><i> Arathorn: Co-Sysadmin, TheOneRing.netR | |
110 | </I>><i> | |
111 | </I>><i> | |
112 | </I>><i> | |
113 | </I>><i>------------------------------------------------------------------ | |
114 | </I>><i>To unsubscribe or change your subscription options, visit: | |
115 | </I>><i><A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">http://www.ircservices.za.net/mailman/listinfo/ircservices-coding</A> | |
116 | </I>><i>. | |
117 | </I> | |
118 | /******* - End Original Message - *******/ | |
119 | ||
120 | ||
121 | ||
122 | ||
123 | </PRE> | |
124 | ||
125 | <!--endarticle--> | |
126 | <HR> | |
127 | <P><UL> | |
128 | <!--threads--> | |
129 | <LI>Previous message: <A HREF="003024.html">[IRCServices Coding] is this a bug | |
130 | </A></li> | |
131 | <LI>Next message: <A HREF="003030.html">[IRCServices Coding] OperServ help | |
132 | </A></li> | |
133 | <LI> <B>Messages sorted by:</B> | |
134 | <a href="date.html#3026">[ date ]</a> | |
135 | <a href="thread.html#3026">[ thread ]</a> | |
136 | <a href="subject.html#3026">[ subject ]</a> | |
137 | <a href="author.html#3026">[ author ]</a> | |
138 | </LI> | |
139 | </UL> | |
140 | ||
141 | </body></html> |