nescivi wrote:
> Hiho,
>
> On Sunday 30 November 2008 22:32:10 torbenh@email-addr-hidden wrote:
>> On Sun, Nov 30, 2008 at 12:27:41PM -0500, nescivi wrote:
>>> On Saturday 29 November 2008 23:50:32 torbenh@email-addr-hidden wrote:
>>>> hi...
>>>>
>>>> now that the backend is mostly done, i am thinking about
>>>> a GUI for netjack.
>>>>
>>>> i already found gtknetsource.py on my HD, i started mucking
>>>> with that some months ago.
>>>> i plan to extend that thingy now.
>>>>
>>>> but setting up the connection, and getting IP addresses
>>>> of users is still a PITA.
>>>> i am thinking along the lines of an IM like thing,
>>>> based on jabber.
>>>>
>>>> i am not seeing good options to making this available
>>>> in the various IM clients.
>>>> thats why i would rather like to have modified jabberd running
>>>> on jackaudio.org or at the consortium servers.
>>>>
>>>> it would not support chatting or stuff.
>>>> only show who is online. and if a session is running.
>>>> it would only make the IP of a user available when he agrees,
>>>> to open session... blabla... security.
>>>>
>>>> so basically you click on your buddy, to open a session.
>>>> buddy agrees.
>>>> IP of buddy is transmitted. tool measures connection.
>>>> provides you with some options.
>>>> ie compression ratio, number of channels, latency, who is master ?
>>>>
>>>> and starts the netjack session.
>>>>
>>>> thoughts ?
>>> Does irclib for python help?
>>> Creates a python irc client, which you can then have only the options you
>>> propose.
>>> Not jabber based though.
>> this might be a very good alternative.
>> one would need to register a second nick on freenode for this i guess.
>>
>> it would still not be easy to detect the IP of a peer, if he was using a
>> cloak. i basically want to expose IP only if user agrees.
>> and detecting IP from inside NAT is not trivial.
>> not sure how i should tacke this. i there some service out there,
>> which can tell me my IP if i open a TCP connection to it ?
>>
>> if you have a solution for this, irc would become my choice i guess ;D
>
> Hmm... not really.
> Although.. sk wrote a http-tunnel for a project of ours once in ruby, to
> tunnel osc messages to the outside world, so I could control a remote
> scsynth, regardless of firewalls, that may be in between.
> But it required a server running a host script, which connected the tunnels.
>
> It's a bit convoluted, and may send audio streams around with some detour,
> depending where the server is, and where the participants are.
> But I'm sure linuxaudio.org would be eager to give some bandwidth ;)
>
> Maybe our LAC streamteam has some brilliant idea how to do this...
this part of the lac streamteam must confess it doesn't have the
faintest... which may partly be attributed to sushi deprival syndrome.
even though i hosted stefan's nat-piercing script for one of marije's
projects, i never bothered to find out how it works... i guess it's a
reflector that actually bounces the data back and forth.
i'm very sure that's not what you want for a netjack connection if you
care for latency. plus you would burn huge amounts of bandwidth for
basically nothing.
the way i see it, if you want to netjack between two natted hosts,
there's no easy way around port forwardings on both ends. which is fine
imho, since we are not competing with skype here, are we?
for the simple case (both end points have real ip addresses), some
simple directory script (such as the icecast streamer list) might
suffice, but the cool thing about the jabber idea is you can ssl it and
maybe also use it to agree on a login procedure without having to post
your ip (and hence, your open netjack port) for all the world to see.
(btw, torben, great to hear from you again! do get in touch if you ever
need a crashpad in essen.)
best,
jörn
-- jörn nettingsmeier home://germany/45128 essen/lortzingstr. 11/ http://spunk.dnsalias.org phone://+49/201/491621 _______________________________________________ Linux-audio-dev mailing list Linux-audio-dev@email-addr-hidden http://lists.linuxaudio.org/mailman/listinfo/linux-audio-devReceived on Mon Dec 1 16:15:02 2008
This archive was generated by hypermail 2.1.8 : Mon Dec 01 2008 - 16:15:02 EET