1.5.3


Old Stuff

 www.your-freedom.net
 www.secure-tunnel.com

Ticket #40 (closed defect: fixed)

Opened 3 years ago

Last modified 3 years ago

Cannot resolve IP address of remote host

Reported by: bcohen@raba.com Assigned to: andrei
Priority: normal Milestone: AlmostVPN 1.0 Future
Component: PreferencePanel Version: 0.9
Severity: normal Keywords:
Cc:

Description

I'm trying to create Almost VPN connections. I get a warning about not being able to resolve IP address for the remote host (i.e. sleepingpenguin)

If I configure Almost VPN with the remote IP address 198.. for the remote host through its /etc/hosts configuration window it works.

Why do I need to do this? My plain old SSH tunnels previously worked fine using the DNS name for the remote host?

Change History

10/18/05 09:18:21 changed by andrei

  • owner changed from admin to andrei.
  • status changed from new to assigned.
  • milestone set to AlmostVPN 1.0.

AlmostVPN is using "standard" means to resolve host name to IP address. "Can not resolve IP address..." message indicate that gethostbyname() function fail to do so. It will be interesting to see if you could "resolve" the same name at the same time from other application ( like ping <host name> from command line ). It is possible to "teach" AlmostVPN IP addresses for your internal host names. You might want to take a look at http://www.leapingbytes.com/documents/almostvpn/AlmostVPNNames.html#KnownServers.

10/24/05 10:25:53 changed by andrei

  • status changed from assigned to closed.
  • resolution set to fixed.

Fixed. AlmostVPN used to complain about "can not resolve" in situations when it was OK not to be able to do it. Now it will just mark this as a possible problem and will let user to continue. Also, "Known Servers" manager dialog now effectively "extend" /etc/hosts file while AlmostVPN profile is running. So, now it should be possible to fix ANY "host name resolution" related problems with "Known Server" manager.