Re: lwl servers

> That's what the idea has been in terms of using the jabber (or other
> IM) network.  That would give presence notification, and host IP
> addresses could also be transferred that way. The public servers
> already exist to do that .  The problem with lwl is that it really
> needs resources that will be maintained for the long term, and there's
> no apparent way for that to happen yet.

I am admining a server that maybe could be suitable. Querying the
Management if a little corporate sponsorship of this endeavour could be
possible.

I need to know how much bandwidth and CPU and disk space a LWL server of
the required capacity needs. Educated guesses are more than welcomed.

> It's not as big an ask to host a simple script on a webserver as it is
> to host a lwl server - or it may be that the user can supply The NAT
> information directly in some cases.

Can't we integrate this functionality to the LWL server itself? When
connecting to the server, the client reveals its external IP
automagically. We could patch LWL and the clients for support of querying
for this information (and possibly for other chunk of code, eg. a stripped
down version of the client capabilities and required NAT workaround method
I proposed for the Jabber solution). If both clients have the same
external IP address, it may be presumed they are on the same network and
their internal IP addresses may be returned instead.

(In other news, S.J. Henriksen of the Speex patch fame reported
considerable success with NAT support in Windows version. This, together
with the modified LWL, could be a Big Solution. I am also suggesting the
ability to specify source UDP address, which could possibly solve some
problems in configuration where both incoming and outgoing port is the
same, in our case 2074 and 2075.)

Jabber-like solution is a next step, decentralized to avoid wide-scale
dependence on a single central server.

> So jabber can replace lwl, but I'm still hoping for something a bit
> cleaner to come up for transparently determining NAT addresses.  Until
> it's working, you can always initiate a conversation via a jabber or
> other IM client, and tell your address to the other party manually,
> and in the case of a NAT, use a web browser to first determine your
> own address.

Reports of what works and what doesn't work manually would be very
beneficial for development of automated solution.

An automated outside address determination can take place either by the
way of modified LWL server, or by using a small utility querying a
preconfigured server automagically on the client side, or allowing an
user-supplied parameter if the user knows what he's doing.

                      * * *

To unsubscribe from this mailing list, send E-mail containing
the word "unsubscribe" in the message body (*not* as the
Subject) to [email protected]