12,270
edits
L2TP Overview: Difference between revisions
→Configuration Options at AAISP Side
mNo edit summary |
|||
|
=Configuration Options at AAISP Side=
L2TP setting are set by staff, so please do contact them for any changes or setup. The information that would be requested
*Target IP (with an optional backup IP) - the L2TP server at your side
*Host - the hostname we present
*Secret - the password we use (optional)
= '''Some Notes from customers:''' =
Connecting with Windoze 7 was almost as easy except that the default connection settings don't work. You have to edit the connection properties and on the Security tab change 'Type of VPN:' to 'Layer 2 Tunneling Protocol with IPsec (L2TP/IPSec)' otherwise it only tries PPTP, and change 'Data encryption:' to 'Optional encryption (connect even if no encryption)' as it doesn't like A+A's certificate (because RevK declines to use a root certification authority recognised by Microsoft, or is it that Microsoft declines to recognise the root certification authority chosen by RevK). I guess the alternative would probably be to add the root certificate to the machine in question. Anyway, with those two changes it works fine.
Watch out if you are using [[IPv6]]. It seems that Win7 negotiates a non-routable [[IPv6]] address with the LNS. You have to discard this address and manually configure one of your routed [[IPv6]] addresses. ipconfig /release6 is your friend here.
== Cisco Routers ==
- You will need to sanity check routing in your particular environment. This is especially important if you choose to use '''ppp ipcp route default''' on the l2tp tunnel. It's safest to make sure that you have a static route set to the L2TP server.
- I haven't tested this for [[IPv6|IPV6]] yet.
- This is "early release" information - I haven't yet used this in anger over a long period of time but will try to remember to come back and update if I find any major issues.
| |||