Works fine for me on both.  Does EchoLink use fixed ports ?  If so, natting
and routing should work as designed.  A nat will take the incoming port and
reroute to the machine in house.  The Example:

1.  Internal machine has IP address 10.1.1.1 
2. Router has 67.1.1.1 (example only please)
3. EchoLink machine goes out on 10.1.1.1 
4.  The router creates a NAT entry 10.1.1.1:[port number]  to 67.1.1.1
[port number]

BTW: port numbers are the same, they are just mapped incoming and outgoing.
The mapping is internal in a Network Address  Translation table created by
the NAT router.

Unless the port is below 1024, there should be no problems mapping machines
automatically and there should be no problems with functionality.

5. the translation is transparent between the outside of the world and the
internal world.
6.  Unless you get lower in the OSI  model, you should have transparency.
7.  If there are issues with your configuration, creating a DMZ might help
alleviate the issue but this requires advanced configuration.

73,


Jose - KK4JZX


-----Original Message-----
From: For blind ham radio operators [mailto:[log in to unmask]]
On Behalf Of Steve Dresser
Sent: Wednesday, August 21, 2013 12:23 AM
To: [log in to unmask]
Subject: Re: echolink

Butch,

If you use the same static IP address on both machines, you'll get away with
it.  Just don't try to connect both machines to the network at the same
time.

Steve

----- Original Message -----
From: "Butch Bussen" <[log in to unmask]>
To: <[log in to unmask]>
Sent: Tuesday, August 20, 2013 20:13
Subject: Re: echolink


>I didn't think you could either.  How do you forward ports to both
> machines?  interesting....
> 73
> Butch
> WA0VJR
> Node 3148
> Wallace, ks.
>
>
> On Tue, 20 Aug 2013, Barbara Lombardi wrote:
>
>> I must be mistaken but I didn't think you could put it on desktop and
>> laptop.  If I'm wrong, I do apologize.  A friend of mine informed me of 
>> that
>> but must be mistaken
>>
>>
>>
>> Barb K1EIR
>>
>>
>[port number]