IPV6

[bILLY]

Code: Select all

Eggdrop v1.6.17-ipv6 © 1997 Robey Pointer © 2004 Eggheads
[19:46] --- Loading eggdrop v1.6.17-ipv6 (Mon Jul 10 2006)
[19:46] * Hostname IPV6 self-lookup failed.

[Alchera]

Ever heard of the Search function?

Self lookup ipv6 connection failed.

[sauce]

I'm having the same problem. Bot crashes frequently with this message on IRC (EFnet)

Code: Select all

* @eggdrop (eggdrop@eggdrop.com) Quit (Remote host closed the connection)

This is the only error I can find in eggdrop.log:

Code: Select all

* Hostname IPV6 self-lookup failed.

Here is a clip of my eggdrop.conf

Code: Select all

set my-hostname6 "myipv6.hostname.com"
set my-ip6 "2001:aaaa:bbbb:cccc:0000:0000:0000:0001"
set my-ip "192.168.1.10"

It was stable for weeks with this same configuration, then something happened.

Whats going on with the IPv6 patch for 1.6.18?

[nml375]

Have you linked your bot into a botnet, or use the dcc file-transfer features?

If so, you're suffering from a known bug in the 1.6.17-ipv6 patch. It is unrelated to the host-lookup issues however.

[sauce]

Yes it is linked to a botnet. Whats the workaround?

[nml375]

The patch adds a function to the global export list (src/modules.c and src/mod/module.h) known as "getprotocol". As it is based on the 1.6.13-patch, it incorrectly assumes the end of that list to be the same as in 1.6.13. Unfortunately, there's been a few functions added to the list, resulting in a collision and offset of the list..

The fix is to locate the entry for "getprotocol" (in src/modules.c), and the related macro (in src/mod/module.h), and relocate them in a fashion that does not offset any of the other functions in the list.

Simplest thing would probably be to move it to one of the "spare" slots left behind when ipv6-support was pulled from the source...

that is, change

Code: Select all

   (Function) tell_bottree,
   (Function) getprotocol,
   (Function) MD5_Init,

into

Code: Select all

   (Function) tell_bottree,
   (Function) MD5_Init,

and

Code: Select all

  (Function) file_readable,
  (Function) 0,                   /* IPv6 leftovers: 286                 */
  (Function) 0,                   /* IPv6 leftovers: 287                 */

into

Code: Select all

  (Function) file_readable,
  (Function) getprotocol,                   /* IPv6 leftovers: 286                 */
  (Function) 0,                   /* IPv6 leftovers: 287                 */

And finally:

Code: Select all

#define getprotocol ((int (*)(char *))global[277]) /* get protocol */

into

Code: Select all

#define getprotocol ((int (*)(char *))global[286]) /* get protocol */

[sauce]

okie, i recompiled the bot with the patches you mentioned.

Code: Select all

 [19:50] * Hostname IPV6 self-lookup failed. 

I still get this error but the bot loads okay and hasn't crashed yet. Lets see how it behaves over night, I will post my results in the morning. Thanks for the help!

[sauce]

nah the bot just crashed, its not fixed. how far off is the ipv6 patch for 1.6.18?

[nml375]

Just one check, realized my instructions was abit unclear on one thing..
After relocating "(Function) getprotocol", how many rows with "(Function) 0" do you have directly following it?

Should be something like this:

Code: Select all

  (Function) file_readable,
  (Function) getprotocol,         /* IPv6 leftovers: 286                 */
  (Function) 0,                   /* IPv6 leftovers: 287                 */
  /* 288 - 291 */
  (Function) 0,                   /* IPv6 leftovers: 288                 */
  (Function) strip_mirc_codes,
  (Function) check_ansi,

Is there any debug output available on the shell?

How far off an ipv6-patch for .18 is? Depends on wether someone is working on one.

[sauce]

After rechecking the code it seems I made a mistake. I replaced the wrong 0 with getprotocol. My code now looks exactly like your code. I will post my results.

there is no debug output except for the log but it doesn't log why the bot crashes.

I thought IPv6 was pretty popular on IRC... wonder why its taking so long. I wish it was built-in to eggdrop.

[demond]

I thought IPv6 was pretty popular on IRC... wonder why its taking so long. I wish it was built-in to eggdrop.

no it's not; there's only a handful of ipv6-enabled servers scattered over the networks

there are many issues with the transition from ipv4 to ipv6, so don't expect this to find its way in the standard eggdrop distribution anytime soon (or ever for that matter)

[KrzychuG]

I thought IPv6 was pretty popular on IRC... wonder why its taking so long. I wish it was built-in to eggdrop.

It is, in 1.9. 1.6.x series won't have that feature.

Yes, IPv6 is popular on IRC, but rather on lame (right demond?) IRCnet.

[nml375]

I guess that's in the eye of the beholder
In one way, it's good that there's applications for IPv6, as this most likely results in more IPv6-enabled softwares once deployment picks up the pace.
Tho, for most users, I'd say it's just a gimmick for now.

I'd say, most of the IPv6-ircd's deployed are either part of some development/deployment study, or run bu those ppl who always gotta have the latest stuff, always use alfa/beta-drivers (yeah, I know, I'm exaggerating abit here, but I think you get what I'm getting at

[sauce]

The bot just crashed after 8 hours uptime. I really thought it was fixed, because it used to crash every 60 minutes.

The last thing in the log is:
[18:21] * Hostname IPV6 self-lookup failed.

And the quit message:
Quit (Read error: Connection reset by peer)

I think I'm just gonna compile 1.6.18 and stick with that. No cool vhosts for me.

[nml375]

Too bad you did'nt get any DEBUG-file or coredump on yer shell..
Would help alot to track down the cause for the crash..
I would guess it's either an unrelated bug, or a different one introduced by that ipv6-patch.

Also, if you can live without ipv6 for dcc, botnets, etc, you could always set up an 6tunnel to connect your bot to that ipv6-server...