A few days ago I came across a very detailed desciption about how to configure IPsound software for remote connection but I misplaced the link. As far as I remember it was on some software-radio webpage. After lots of desperate googling I can't find it back. Does someone have it maybe saved ?
Thanks and sorry for having to bother you with this question. I am looking for an alternative to replace Skype for CW audio transport.
Thanks, 73!
zoli ha1ag
____________________________________________________________________________________
Expecting? Get great news right away with email Auto-Check.
Try the Yahoo! Mail Beta.
http://advision.webevents.yahoo.com/mailbeta/newmail_tools.html
Stan W4MQ
1. Both computers have to point to the same port.
2. This port must be unblocked. My ISP blocks
4444 and many others. At the answering end, this
port must be forwarded to the answering computer
behind the firewall, if any.
3. The originating computer has to have the correct
IP address of the answering computer entered.
4. The answering computer has to be in autoanswer.
5. IP Sound has to be running on the answering computer.
If that computer is rebooted, IP sound must be manually
restarted.
By far the biggest problem is port blockage.
I had a working IP sound connection. I moved the
originating computer to a different ISP and it didn't
work any more. This has to be due to port blockage.
Note that the IP Address of the originating system
is irrelevent.
Hope that helps.
Rick N6RK
Yesterday I thought I would try it from our local public library. I
could NOT access IP-Sound or ARHP at my home from the library. Is
this likely because the library block Ports 4444 (IP Sound) and 50000
(ARHP). Are there different ports that may have more likely success?
Is this situation typical of public HotSpots?
Thanks
- Paul KW7Y
For instance, your IP-Sound send out data to port 4444 of the server
and designates a return port, e.g. 4444 on its Client. Unfortunately
most routers will re-map the return port, e.g. 4444 to another value,
e.g. 56789 and send that one out to the distant server. Thus the
Library router actually expects a return to 56789 and would send that
correctly to the IP-Sound. Unfortunately IP-Sound does NOT read the
request return port, but just sends out on its fixed setup port, e.g.
4444. This is then not passed by the Library router and thus NO
sound. Poor design!! Incidentally Echolink does the same thing but
for different reasons -- to allow conferencing-- and thus has similar
problems.
Best to run IP-Sound using a Virtual Private Network, VPN, such as
Hamachi and thus have no router problems.
Stan W4MQ
>Best to run IP-Sound using a Virtual Private Network, VPN, such as
>Hamachi and thus have no router problems.
How does using VPN with IP-Sound solve this problem? Doesn't it is
still require both PC's to communicate on PORT 4444?
Thanks
- Paul
Another workaround (besides just looking for open ports)
is to use a free VPN service, like Hamachi (now owned
by logmein.com). This can generally punch holes in any
firewall, no matter what shenanigans the ISP is playing.
BTW, LogMeIn is a free remote desktop service. It's like
the much more well known "GoToMyPC" except it is free. I use
it to control the computer at my remote base. I have
been very happy with it. It seems to be able to get
through firewalls easily, even from my work computer.
Rick N6RK
> _______________________________________________
> Remotebase mailing list
> Remot...@mailman.qth.net
> http://mailman.qth.net/mailman/listinfo/remotebase
>
Stan
Stan W4MQ
Next time I'll definitely get Hamachi installed
before hitting the road.
Rick N6RK
> -----Original Message-----
> From: remot...@googlegroups.com [mailto:remot...@googlegroups.com]On
> Behalf Of W4MQ Stan
> Sent: Wednesday, July 04, 2007 3:08 PM
> To: remot...@googlegroups.com
>For ham radio ops using WiFi, hotels, etc. excellent results have
>been obtained with Hamachi VPN.
So if I understand you correctly, juts the fact that I have the 2
computers communicating with VPN will defeat the fact that PORT 4444
may be blocked or translated by the router. Is that correct?
BTW I have VNC which I presume will do the same as VPN
- Paul
Stan
>Yes to the VPN question. FYI, VPN and VNC are as different as apples
>and cupcakes, i.e. there is no similarity, VPN is a network tunneling
>approach and VNC is a computer display transmission approach.
Based on that then are you saying it will not work with VNC?
- Paul
Stan W4MQ
VNC works with VPN. I routinely use VNC to log-in back to my office PC
using Hamachi's 5.x.x.x VPN network. VNC and VPN have two completely
different purposes. VPN is an encrypted transmission medium, whereas VNC is
a desktop control program that can communicate on the VPN as its
communications medium.
Generally, VNC can log-in to the host computer with or without a VPN
tunneling program. Not always, but much of the time. However, IP-Sound
requires VPN tunneling more often than not. When I'm on the road, I use
Hamachi VPN for everything, including IP-Sound, VNC, and file transfers. I
have Hamachi set to load automatically when Win XP boots up and connect
through it whether I need to or not since Hamachi does not affect my
transmission bandwidth.
Paul, W9AC
-----Original Message-----
From: "Richard (Rick) Karlquist" <ric...@karlquist.com>
To: remot...@googlegroups.com
Sent: 7/4/07 3:23 PM
Subject: [IRB] Re: [Remotebase] IPsound and ARHP access?
I was too busy trying to work BS7H to spend
time installing Hamachi :-) I just used my
auto phone patch for audio instead of IP sound.
Next time I'll definitely get Hamachi installed
before hitting the road.
Rick N6RK
> -----Original Message-----
> From: remot...@googlegroups.com [mailto:remot...@googlegroups.com]On
> Behalf Of W4MQ Stan
> Sent: Wednesday, July 04, 2007 3:08 PM
> To: remot...@googlegroups.com
> Subject: [IRB] Re: [Remotebase] IPsound and ARHP access?
>
>
>
> For ham radio ops using WiFi, hotels, etc. excellent results have
Stan
- Paul