--- In [email protected], Cgull Charlie <[EMAIL PROTECTED]> wrote:
>
> penguinforce wrote:
> 
> >I'm definitely starting on my own PC using the loopback interface, and
> >I have a second box on my home network to play with as well.
> >
> >But my goal is to write a peer-to-peer application, and I want to
> >study ways of initiating connections between peers that sit behind
> >NATs (using STUN, etc.).  It's a pretty interesting problem.  That's
> >why I need access to a box with a "real" IP address, that'll run my
> >servers.
> >
> >  
> >
> You can still do all that on a single physical machine.  What is it 
> exactly you dont think can be handled by the VM approach? .
> The other thing that might work, sans VM technology, is to stick a
whole 
> bunch of NICs in one machine, plug them into a single HUB and give them 
> all different IP's.  So long as you are talking IP on different network 
> addresses you can have 1 source machine on 1 NIC, 2 NICs providing NAT 
> in and out and the 4th being the target all on the same physical LAN
and 
> each app on each interface wont be any the wiser.
> Maybe you should provide us with a more detailed description - as close 
> to a network diagram as you can do in plain text.
> That'll help.  Because end of the day, having it all under one desk 
> makes it easier.
> 
> cGull
>

@Akshay: Thanks for the offer!  I'm looking more for a place to tinker
and do development, so it definitely wouldn't be safe to play on your
production machine.

@Brad: I've never looked into UML, but it looks very interesting.

@cGull: Setting up a NAT on my own hardware sounds good.  At the very
least I'm sure the exercise will be educational.  I would be inclined
to do it using virtual machines on just one PC.

The whole reason I've run into this NAT business is because I want
real peer-to-peer connections (without relaying data through a central
server), in order to reduce latency for streaming (real-time) data. 
To cover all the bases, I must be able to connect all combinations of
PCs behind different NATs, the same NAT, or no NAT at all.  That way
anybody can connect to anybody else (with a few exceptions).

If I can figure out how to initiate peer-to-peer connections through
various network setups, I'll still need to experiment with latency and
packet loss over the "real" Internet.  But I'm just getting started,
so this is a way off.

I have enough to keep me busy on my own hardware for a while - I'm
just trying to map out a general direction.  I'll get to work on
setting up some virtual machines.





 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/dubailug/

<*> To unsubscribe from this group, send an email to:
    [EMAIL PROTECTED]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/
 


Reply via email to