View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001867 | unreal | ircd | public | 2004-06-10 17:20 | 2007-04-27 05:44 |
| Reporter | avone | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | wont fix | ||
| Product Version | 3.2 | ||||
| Summary | 0001867: Q:lined nicks | ||||
| Description | Q:lined nicks with snomask +q set on will report to always be rejected from the local server and not reported to be rejected from remote servers. Another words if a nickname is qlined, someone tries to change their nick to the qlined nick on a remote server, the server notice will report that the persons nick was rejected on your local server and not the remote server. | ||||
| Steps To Reproduce | sqline a nickname across the network set /mode nick +s +q on your local client connect a client on a remote server and change the remote clients nickname to the qlined nick, look at your local client server notice | ||||
| 3rd party modules | |||||
|
|
Can you paste an example? |
|
|
(5:23:00:pm) ••• (s) Q:lined nick r_BOT00880 from av[5] on FiberOptic.DigitalIRC.Net av[5] was actually connected to sinner.digitalirc.net when I changed it's nick to the r_BOT00880 nickname but did report the qlined nick globally on all servers. I also noticed that it doesn't send out a global notice when a person connects with a certain qlined nickname. It's only local to the server on which the person is trying to connect to. For example. (4:30:49:pm) ••• (s) Q:lined nick |[m0r0nz]|-15660 from <unregistered> on FiberOptic.DigitalIRC.Net it only shows this notice on the local server and won't show it globally for <unregistered> |
|
|
[Quote avone: it only shows this notice on the local server and won't show it globally for <unregistered> ] Which is good, or do you want global qlined nick notices flood? Look here: -> http://bugs.unrealircd.org/bug_view_advanced_page.php?bug_id=0001335 |
|
|
Why should any of this be reported globally? |
|
|
I figured out how that works, and as codemastr said, its not global. The Q:Line shows up on the FiberOptic.DigitalIRC.Net because that is where the Q:Line is set (maybe its set in the conf file, or its set on that server only), so therefore, that server only reports to that server's clients. Downside to not sending the q:line globally [which means it is most likely a config qline] is that it cant be forbidden remotely. I know this because it does that on the net I'm with: * Nick1 is now known as Badnick [Nick1 is connected to Server1.mynet.net] *** Q:lined nick Badnick from Nick1 on Server2.mynet.net However, if they are on that server, it goes like this: *** Forbidding Q:lined nick Badnick from Nick1 (something like that). they must have a good reason for doing it like that (maybe save bandwidth on info not intended to go global.... conf qlines are designed to be local.).. and i dont think they are planning on remotely reporting all that.... seems to me that information is only pertinent to that server's admin if its a conf qline. if the netadmins/net owners want it, they can request the logs or park a log bot on the server. :) |
|
|
well, q:line is global, that q:lines are set via services. (SQLINE) |
|
|
Actually what I was doing was watching for certain bots that all have a similar nickname. I would just qline part of their nicknames but they would still connect up to the servers and I would see a ton of unknown connections, so I setup a script to gzline the ip addresses as I saw the qline server notices. I had to connect a client up to every server in order to see all the qlines on the individual servers because it doesn't show them globally for <unregistered>. I understand about getting flooded off the network because it can be bad when part of a floodnet connects to just one server, the qline notices can be overwhelming. I don't see this as a bug anymore as I have learned. What I would like to see is the ircd somehow control qline floods from the same ip address. |
|
|
you mean 0001335 ? |
|
|
This may be off topic [and you admins may delete this after reading it] but, if the BugNotes you are posting [codemastr, syzop] are marked private, why do I recieve an e-mail notice about it if I cannot see the message? LoL. |
|
|
Zell, that's a very good question. I'll be sure to ask the Mantis team about that :) |
|
|
Please re-submit for 3.3 or 3.2.6/7 instead if this issue still exists. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2004-06-10 17:20 | avone | New Issue | |
| 2004-06-10 17:39 |
|
Note Added: 0006629 | |
| 2004-06-10 18:27 | avone | Note Added: 0006630 | |
| 2004-06-14 05:35 | Rocko | Note Added: 0006640 | |
| 2004-07-13 18:40 |
|
Note Added: 0007035 | |
| 2004-07-14 23:49 | Zell | Note Added: 0007074 | |
| 2004-07-15 03:21 | Rocko | Note Added: 0007083 | |
| 2004-07-16 00:04 | avone | Note Added: 0007109 | |
| 2004-10-08 04:28 | aquanight | Note Added: 0007909 | |
| 2004-10-12 19:19 | Zell | Note Added: 0007991 | |
| 2004-10-13 01:03 |
|
Note Added: 0007992 | |
| 2007-04-27 05:44 |
|
Status | new => closed |
| 2007-04-27 05:44 |
|
Note Added: 0013836 | |
| 2007-04-27 05:44 |
|
Resolution | open => wont fix |
