Home › Forums › Archive › VaporSec › how to configure IPsec for host <-> network

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • June 23, 2003 at 9:40 pm #355951
    Anonymous
    Participant

    My configuration needs are for a single host at work to communicate with an entire private home network (using IPsec to provide secure communications).

    Reading the docs and articles recommended (afp548, FreeBSD, etc.), I see lots of info about host <-> host (transport mode) and network <-> network (tunnel mode) info for VaporSec and IPsec in general. However, I’d like the configuration to provide access only from a single host to the internal network. The main point here is that I don’t want the home network to be accessible to other hosts on the work network.

    The work machine is an OS X 10.2. box.

    The home network has an OS X 10.2 box with a static IP address as a gateway with NAT services (and DHCP) for the internal network on a DSL line.

    Can anyone give me advice on how to set this up either with VaporSec or simply with direct command-line IPsec configuration? Is anyone aware of an article that describes this kind of setup?

    Many thanks for any help.

    – MSB

    September 23, 2003 at 9:56 pm #356459
    Anonymous
    Participant

    I’m trying to do the same thing as the original poster of this thread. I have a g4 tower and a g4 laptop. I’d like to be able to connect to the tower through a vpn.

    As you describe, the two machines both need VaporSec running and will have specific entries in the top part of the new dialogue box. It makes sense to me from a client perspective but not so for a server perspective.

    My specs:
    g4 tower info: eth0 a.b.c.d inet #, http://www.domain.com, eth1 10.0.1.1 lan # (NAT router)
    g4 laptop info: eth0 192.168.0.211, no domain name, router: w.x.y.z inet IP#.

    I’m thinking I would enter into each VaporSec forms:
    laptop:
    Remote IPSec device: http://www.domain.com
    Remote Network: 10.0.1.1/24
    Local Network Mask: 32

    g4 tower:
    Remote IPSec device: w.x.y.z ??
    Remote Network: 192.168.0.1/24 ??
    Remote Network Mask: 32 ??

    (Question marks added out of confusion).

    And then, if I have both machines configured properly, I click Vaporize? Maybe I could help out with the usability of this. 😀

    In the readme, is says:
    7. Wait until the button begins to flash again which symbolizes that everything has been set up. Then try to connect to the remote network.

    How do I try to connect to the remote network?

    Thanks for making this radical gui. I hope to get it working.

    Al

  • Author
    Posts
Viewing 2 posts - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.

Comments are closed

Copyright © 2025 AFP548. All Rights Reserved.