Claudia wrote :
>> Certainly I have XP and 2k operating as RW with dynamic IP.
>> Generally, the dynamic IP machine has to initiate the connection.
>
> Thanks for the extra info, Cameron. In the latest version of the
> interop table, I've clarified that it can work both ways.
>
Hi Claudia,
first point - I tried to email this directly but it looks like the email
bounced when being forwarded from freeswan.org.
main point-
I'm not sure I've added anything new, or whether there might be a
mistake in the interop guide. I was just following Nate Carlson's and
Marcus Mueller's guides, which both have ms-win machines as r/w. I note
that in the section down the page with MS-win 2k/XP interop links, that the
link to
Nate Carlson's page says "Unusually, FreeS/WAN is the Road Warrior
here". This seems misleading, because I think his page is describing
using X509 for F/swan and ms-win systems as r/w to a f/swan gateway.
(not f/swan as r/w to MS-win server). I wonder if misinterpreting this
gave rise to the comment in the interop table. I cannot find anywhere
describing a F/swan R/W connecting to a Windows machine where the
windows machine is the one with static IP. (and I don't need to do it
either). All your (working) links refer to Windows *client* software.
Cheers,
Cameron.
Claudia Schmeing <mailto:[EMAIL PROTECTED]> wrote on Wednesday, 6
August 2003 09:04:
_______________________________________________
FreeS/WAN Users mailing list
[EMAIL PROTECTED]
https://mj2.freeswan.org/cgi-bin/mj_wwwusr
