Hi all
I just want to ask You, if anyone tried to port jabber server to openwrt ? Or is it already avaiable here under any multipackage ?
If not then I can try to port it

Thanks
Jarek

btw: good work ;-)

Hi Jarek,

Which Jabber server were you thinking of, none are currently ported, but there are also many different implementations.

TTFN

Mike

hmm I don't known which is better for openwrt.
But I think to have the jabber server on own router is good idea. And no one tryed it yet I'm suprised ;-)

I fighting with openwrt and NP28G now, then jabber is second priority for now )

good night

Jarek

Hi everyone!

I don't know if it helps, but the Milkfish project seems to have made a package for jabberd.
The package itself is located here, but unfortunately I haven't found the corresponding package files to build the iPKG (e.g. for a new version). But maybe the given package might also work directly with OpenWRT, because Milkfish Boozy is based on OpenWRT to begin with.

But of course I'd like to see an official OpenWRT package for a jabber server.

Either way, thanks for you work so far, folks!

Hi folks,

Yes, Budrus of the Milkfish Project ported jabberd from jabberd.org some time ago for Whiterussian RC4.
Here is the package source: http://packages.milkfish.org/sources/jabberd/

There is one issue existing in the version we made in the dialback (or s2s) module which is:
Dynamically changing WAN IP addresses cause a DNS-cache error on the far end.
This is even valid for usual jabberd applications being statically IPed servers, of course.

I submitted a bug report, but it seems untouched ever since:
http://webview.jabberd.org/cgi-bin/bugz … .cgi?id=54

Apart from that, basic functionality was given with our port.

Here's a more detailed description of the problem:

dialback host:ip-cache inconsitency with dynamic ip servers


If a jabber server is assigned a dynamic ip address a change in this address
(e.g. by a broadband reconnect) results in a invalidation of dialback cache
entries of all other jabber servers having had recent s2s contact with the one
whichs ip just changed.

Server1 Log:
20060530T21:18:44: [warn] (s2s): Denying peer to use the domain [Server1].
Dialback failed (timeout): <db:result to='[Server1]' from='[Server2]' typ

Server2 Log:
20060530T21:18:45: [alert] (s2s): We were told by [Server1] that our sending
name [Server2] is invalid, either something went wrong on their end, we tried
using that name improperly, or dns does not resolve to us

Suggestion:
After such a cache inconsistency is noticed but before the actual rejection
is sent out, the dialback component could update the cache using dns resolution,
as done for new s2s contacts.
If the failure persists there is something wrong indeed.
If not, the cache is thereby updated and communication continues as usual.

I'm currently trying to port jabberd to Kamikaze (planning to switch from whiterussian soon...)
However, I'm not as experienced as I wish I'd be

While compiling I get an error:

configure: error: Couldn't find required libidn installation

staging_dir_mipsel doesn't contain libidn, nor libpth - so how could I solve this?

Sorry, if this is obvious or anything...