Eggdrop 1.6 & ipv6

[teel]

Hi,

I've been running an Eggdrop bots for years now, so I'm not exactly a newbie, but now I've hit a brick wall with ipv6 after moving to another host. See, this new shell requires me to use ipv6.

I've been running Eggdrop 1.8 nightlies now, but it's getting somewhat annoying with all the weird stuff happening. Also I can't use Megahal with it :)

So I tried to configure 1.6 with ipv6 using the 1.6.19 ipv6 patch that is also linked here in egghelp.org. However when pathing 1.6.19 I get an error "patch unexpectedly ends in middle of line" and after compiling the ipv6 settings doesn't work (no surprise there after that error).

So, could anyone help me or give some pointers on setting up a stable eggdrop 1.6.x with ipv6 support (with megahal preferably as the users have become strangely addicted to it).

[pseudo]

Hi,
I've been running Eggdrop 1.8 nightlies now, but it's getting somewhat annoying with all the weird stuff happening (yeah, nightlies, I know, I'm a software developer myself). Also I can't use Megahal with it

Being a software developer, I would expect more precise information.
How come you can't use Megahal with it? The only thing I'm aware of that can prevent loading it is the version check which doesn't recognize 1.8 as supported. I doubt it's a challenge for a developer, but for anybody having problems with it, there are updated module sources at ftp://ftp.eggheads.org/pub/eggdrop/modules/1.8/.
And what's that weird stuff you're talking about? Tell us, we're interested.

So, could anyone help me or give some pointers on setting up a stable eggdrop 1.6.x with ipv6 support

Stable 1.6 with ipv6? You have a good sense of humour.

After investing some time into developing ipv6 for 1.8 I'm not interested in debugging 3rd party patches, but if anybody else is, it might help if you tell people which settings don't work. Note that the crappy patch requires my-ip to be set, in order for my-ip6 to take any effect. The value of my-ip doesn't matter as long as it's set.

[teel]

Being a software developer, I would expect more precise information.

Sorry if I wasn't precise enough. When the bot has been running for a while, it stops responding to anything. It's someting TCL related so probably some of my scripts not working well with 1.8 ("couldn't write file "/dev/null": too many open files"). So it's something I need to look into myself.

How come you can't use Megahal with it? The only thing I'm aware of that can prevent loading it is the version check which doesn't recognize 1.8 as supported. I doubt it's a challenge for a developer, but for anybody having problems with it, there are updated module sources at ftp://ftp.eggheads.org/pub/eggdrop/modules/1.8/.
And what's that weird stuff you're talking about? Tell us, we're interested.t

I tried just removing the version check, but after that it kept crashing after a while when anyone said anything to the bot on the channel (it was some time ago though, I haven't tried it lately). I'm gonna try your version. Thanks!

So, could anyone help me or give some pointers on setting up a stable eggdrop 1.6.x with ipv6 support

Stable 1.6 with ipv6? You have a good sense of humour. ;)

After investing some time into developing ipv6 for 1.8 I'm not interested in debugging 3rd party patches, but if anybody else is, it might help if you tell people which settings don't work. Note that the crappy patch requires my-ip to be set, in order for my-ip6 to take any effect. The value of my-ip doesn't matter as long as it's set.

Ok, "stable" might be a bit far fetched, I admit. What I meant was just something that could actually run and connect to ipv6 servers. As I mentioned, the patch throws an error "patch unexpectedly ends in middle of line" and when I build Eggdrop after that, everything works fine, except any of the ipv6 settings don't work.

Thanks for answering anyway :)

[teel]

Yep, still the same problem with Megahal with the latest 1.8 nightly.

Code: Select all

[18:34:54] *** ATTEMPTING TO FREE NON-MALLOC'D PTR: megahal:megahal.c (1100)
[18:34:54] *** ATTEMPTING TO FREE NON-MALLOC'D PTR: megahal:megahal.c (1100)
[18:34:54] *** ATTEMPTING TO FREE NON-MALLOC'D PTR: megahal:megahal.c (1100)
[18:34:54] *** ATTEMPTING TO FREE NON-MALLOC'D PTR: megahal:megahal.c (1100)
[18:34:54] *** ATTEMPTING TO FREE NON-MALLOC'D PTR: megahal:megahal.c (1100)
[18:34:54] *** ATTEMPTING TO FREE NON-MALLOC'D PTR: megahal:megahal.c (1100)
[18:34:54] *** ATTEMPTING TO FREE NON-MALLOC'D PTR: megahal:megahal.c (1100)
[18:34:54] *** ATTEMPTING TO FREE NON-MALLOC'D PTR: megahal:megahal.c (1100)
[18:34:54] *** ATTEMPTING TO FREE NON-MALLOC'D PTR: megahal:megahal.c (1100)
[18:34:54] *** ATTEMPTING TO FREE NON-MALLOC'D PTR: megahal:megahal.c (1100)
[18:34:54] *** ATTEMPTING TO FREE NON-MALLOC'D PTR: megahal:megahal.c (1100)
[18:34:54] *** ATTEMPTING TO FREE NON-MALLOC'D PTR: megahal:megahal.c (1100)
[18:34:54] *** ATTEMPTING TO FREE NON-MALLOC'D PTR: megahal:megahal.c (1100)
[18:34:54] *** ATTEMPTING TO FREE NON-MALLOC'D PTR: megahal:megahal.c (1100)
[18:34:54] *** ATTEMPTING TO FREE NON-MALLOC'D PTR: megahal:megahal.c (1100)
[18:34:54] *** ATTEMPTING TO FREE NON-MALLOC'D PTR: megahal:megahal.c (1100)
[18:34:54] *** ATTEMPTING TO FREE NON-MALLOC'D PTR: megahal:megahal.c (1100)
[18:34:54] *** ATTEMPTING TO FREE NON-MALLOC'D PTR: megahal:megahal.c (1100)
[18:34:54] *** MEMORY TABLE FULL: megahal:megahal.c (2187)
[18:34:54] * Memory table full

[pseudo]

Regarding 1.8, I have a suggestion. Edit config.h, commenting out or removing the following line:

Code: Select all

#define HAVE_TCL_SETNOTIFIER 1

Do this after running ./configure, but before compiling. After that, run make config/iconfig and compile with 'make eggdrop' instead of just 'make' to check how would megahal perform. Keep in mind though, that it's not eggdrop's fault that megahal.mod is buggy.

[teel]

That seems to work.

Yeah, I have no complaints about Eggdrop, it's been a faithful servant for years despite it's apparently incompetent owner (aka: me).

Thank you so much for the help :)