Trying to link anope or unreal with ignitionServer gives a
error on the opposite server. "Read error from server:
Unknown Error: 0" Although, IgnitionServices works fine.
I think that we're going to have to start distributing our
own binaries for Anope. That binary is compiled for Unreal,
and we don't use Unreal's linking (we use RFC 1459). I'll
have to get the Visual C++ 7.0 compiler installed and see if
I can make a RFC 1459 build (although, I'm pretty sure that
a build for hybrid-ircd will also work).
[Dec 26 22:00:55 2004] user: NICK from nonexistent nick
ignition.servebeer.com
-- this build does not understand RFC 1459 user
introductions (really an extended NICK command; Unreal uses
something completely different)
[Dec 26 22:01:12 2004] help: user record for Ziggy not found
-- this build doesn't detect me, see previous thing
[Dec 26 22:01:53 2004] PANIC! buffer = :Ziggy NICK :anope
-- this build doesn't understand RFC 1459 nickname changes
I'll have to hack around at this. I'm guessing the only
reason there's only an Unreal build is because Unreal is the
only IRCD that runs on Windows. If I can make Anope work
excellently (even if it's my own build or fork), it'll
replace ignitionServices. ignitionServices is horrible and
needs to be gotten rid of.
Turning this into a tracker bug.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Oh, thanks! That'll be great if it replaces ignitionServices. I'd
love to see what you come up with. :) (And if you can get it
to use nickserv and chanserv profiles like ignitionServices,
that'll be awsome!) Good luck!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=919946
Can you give me a link to Win32 Anope services? I can't seem
to find one anywhere...
As for Unreal, it will never work, because it uses an
entirely different authentication mechanism (it doesn't use
RFC 1459 linking for the most part).
Logged In: YES
user_id=1185045
Offical Windows ANOPE binary AND instructions on how to
compile it yourself:
http://certus.anope.org/windows/index.html
And to prevent any miss communication, I did use the
binary. :P
Logged In: YES
user_id=919946
I think that we're going to have to start distributing our
own binaries for Anope. That binary is compiled for Unreal,
and we don't use Unreal's linking (we use RFC 1459). I'll
have to get the Visual C++ 7.0 compiler installed and see if
I can make a RFC 1459 build (although, I'm pretty sure that
a build for hybrid-ircd will also work).
[Dec 26 22:00:55 2004] user: NICK from nonexistent nick
ignition.servebeer.com
-- this build does not understand RFC 1459 user
introductions (really an extended NICK command; Unreal uses
something completely different)
[Dec 26 22:01:12 2004] help: user record for Ziggy not found
-- this build doesn't detect me, see previous thing
[Dec 26 22:01:53 2004] PANIC! buffer = :Ziggy NICK :anope
-- this build doesn't understand RFC 1459 nickname changes
I'll have to hack around at this. I'm guessing the only
reason there's only an Unreal build is because Unreal is the
only IRCD that runs on Windows. If I can make Anope work
excellently (even if it's my own build or fork), it'll
replace ignitionServices. ignitionServices is horrible and
needs to be gotten rid of.
Turning this into a tracker bug.
Logged In: YES
user_id=1185045
Oh, thanks! That'll be great if it replaces ignitionServices. I'd
love to see what you come up with. :) (And if you can get it
to use nickserv and chanserv profiles like ignitionServices,
that'll be awsome!) Good luck!
Logged In: YES
user_id=919946
Well, I'll probably not screw with their database any.
Although I will probably make an editor if Anope's database
allows.
Latest news post:
<http://www.ignition-project.com/node/view/318>