Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 1 subscriber
  • Views 910 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Problems with IPSec between SSH Sentinel and ASL

Andy_01
Hi,

i'm using ASL 3.031 and SSH Sentinel 1.3 Beta-1. My problem is, i can't assign a virtual IP address to my client. The connection is ok, the diagnostic says everything is fine, but as soon as i want to assign a virtual IP address nothing works...

Any ideas?

thx,
Andy.


This thread was automatically locked due to age.
  • 0
    Hi Andy, 

    virtual ip addresses are not supported by ASL.

    Kind regards
    Gert

    [ 11 March 2002: Message edited by: Gert Hansen ]

  • 0 in reply to Gert Hansen
    Assignment of a static Virtual IP address in Sentinel 1.3 is broken. A connection can be successfully negotiated but tunneled packets cannot be received by Sentinel's virtual network interface.

    Dynamic assignment of virtual IP addresses currently is not supported by FreeS/WAN but I have plans to implement the IETF Draft "DHCPv4 Configuration of IPsec Tunnel Mode" over the next couple of months, making it possible for FreeS/WAN
    to forward DHCP information on behalf of VPN clients like SSH Sentinel.

    Regards

    Andreas
  • 0 in reply to Andreas Steffen
    Dear Gerd,

    i haven't found a different way to get an IP address in SSH Sentinel 1.3, there is only "aquire virtual IP address" and i can choose 4 different ways, which i tried without success. What can i do to get my IPSec Clients running? Is there a different solution in an older SSH Sentinel (i never tried older versions)?

    thx,

    Andy.
Unfiltered HTML