Changes

Jump to navigation Jump to search
659 bytes added ,  3 years ago
Reformatted/edited VPNC entry. Created providers section.
Line 532: Line 532:     
== VPNC ==
 
== VPNC ==
 +
VPNC is an open-source VPN client that is compatible with Cisco VPN setups.
 +
VPNC is much easier to configure than the Cisco client and works on almost every flavor of *NIX systems including *BSD, Linux, and even OS/X.
   −
vpnc is an open-source VPN client that is compatible with Cisco VPN setups. VPNC is much easier to configure than the Cisco client and works on almost every flavor of UNIX systems including Linux, Macs and BSD, as well as Ubuntu.
+
=== Installation ===
 +
To install VPNC on Debian based distributions:
 +
    sudo apt-get install vpnc
   −
This is handy if you have a VPN server or IOS router setup and wish to use itw9cr.net runs this as a means to get public IP's directly on nodes, bypassing NAT444 and man-in-the-middle IAX level filtering.
+
=== Configuration ===
 +
Edit the default config file as follows (substitute your own name if you want to name the connection instead of using defaultYou will use this name as @<name> when calling vpnc.)
 +
* Edit /etc/vpnc/default.conf. 
 +
    IPSec gateway <VPNC server IP or FQDN>
 +
    IPSec id AMPRNET
 +
    IPSec secret EzAsARDC
 +
    Xauth username YOUR-CALLSIGN
 +
    Xauth password _YOUR_PASSWORD_HERE_
   −
=== install ===
+
=== Starting the VPN ===
* sudo apt-get install vpnc
+
Use one fo the following commands to start your VPNC based VPN connection.
   −
=== config ===
+
* This command would run VPNC using /etc/vpnc/default.conf, if it exists.  If it does not, it would prompt for the connection information:
 +
    sudo vpnc
   −
Create a configuration file for the RPI Wireless and/or RPI External profile. Usually these files would be stored in /etc/vpnc/profile_name.conf. The default /etc/vpnc/default.conf. 
+
* This would run VPNC using /etc/vpnc/external.conf, if it exists.
 +
    sudo vpnc external
   −
An example config for the W9CR.net vpn server:
+
==== Starting at boot ====
 +
You can start your VPNC based VPN connection at boot using one of the following methods.
   −
'''w9cr example config'''
+
===== /etc/rc.local =====
IPSec gateway cisco.keekles.org
+
This is the simplest way and does not involve creating init scripts or systemd service files.
IPSec id AMPRNET
  −
IPSec secret EzAsARDC
  −
Xauth username YOUR-CALLSIGN
  −
Xauth password _YOUR_PASSWORD_HERE_
     −
=== running it ===
+
Add a line such as the following into your /etc/rc.local file:
 +
  vpnc
   −
To connect to the VPN you would run one of the following commands as root or using sudo:
+
===== systemd =====
 +
To control from systemd:
   −
* sudo vpnc -- This command would run VPNC using /etc/vpnc/default.conf, if it exists. If it does not, it would prompt for the connection information
+
* Edit /usr/lib/systemd/system/vpnc@.service
* sudo vpnc external -- This would run VPNC using /etc/vpnc/external.conf, if it exists.
+
    [Unit]                                                                                                                                                                       
 +
    Description=VPNC connection to %i
 +
    Wants=network-online.target
 +
    After=network.target network-online.target
 +
   
 +
    [Service]
 +
    Type=forking
 +
    ExecStart=/usr/bin/vpnc --pid-file=/run/vpnc@%i.pid /etc/vpnc/%i.conf
 +
    PIDFile=/run/vpnc@%i.pid
 +
 
 +
    [Install]
 +
    WantedBy=multi-user.target
   −
==== Starting it at boot ====
+
* Enable default VPNC configuration to be managed by systemd:
 +
    systemctl enable vpnc
   −
IF you're behind NAT, you want to start this at boot.
+
* Start default VPNC connection with systemd:
 +
    systemctl start vpnc
   −
The simplest way is to call it from /etc/rc.local, but that's a bit in-elegant.
+
Note: If you have multiple VPNC configurations or chose to name your config, you will substitute vpnc for vpnc@<config name>.
 
  −
make the following file at /usr/lib/systemd/system/vpnc@.service
  −
 
  −
[Unit]                                                                                                                                                                       
  −
Description=VPNC connection to %i
  −
Wants=network-online.target
  −
After=network.target network-online.target
  −
  −
[Service]
  −
Type=forking
  −
ExecStart=/usr/bin/vpnc --pid-file=/run/vpnc@%i.pid /etc/vpnc/%i.conf
  −
PIDFile=/run/vpnc@%i.pid
  −
  −
[Install]
  −
WantedBy=multi-user.target
  −
 
  −
So, in order to have your VPN autostart from the configuration file /etc/vpnc/w9cr.conf, you'd do:
  −
 
  −
systemctl enable vpnc@w9cr
  −
systemctl start vpnc@w9cr
      +
== Other ==
 +
Any other information that doesn't fit elsewhere.
   −
=== More info ===
+
= Ham Radio VPN Providers =
If you want a vpn connection via w9cr.net using 44net public IP space, please contact bryan@bryanfields.net.  Include your callsign and details.
+
The following is a table of providers who offer free VPN connections to licensed Ham Radio operators.
    +
'''Note:  No commercial advertisements or pay services are allowed or permitted.  Adding them will get your account removed and/or IP address banned.'''
   −
== Other ==
+
{| class="wikitable" style="text-align: left; width: 85%"
Any other information that doesn't fit elsewhere.
+
|+ Providers of Ham Radio VPN Connections
 +
! System
 +
! Contact
 +
! Type
 +
! Notes
 +
|-
 +
| w9cr.net
 +
| Bryan Fields, W9CR (bryan@bryanfields.net)
 +
| VPNC
 +
| Used as a means to get public IP's directly on nodes, bypassing NAT444 and man-in-the-middle IAX level filtering.  Provides 44net public IP space.  Include your callsign in the details.
 +
|}
    
= Firewall =
 
= Firewall =

Navigation menu