L2TP Client: pfSense: Difference between revisions

← Older edit

L2TP Client: pfSense (view source)

Revision as of 11:26, 8 December 2022

66 bytes added , 8 December 2022

m

→‎Step 1

AA-Andrew

autoreview, Bureaucrats, editor, Interface administrators, reviewer, Administrators

12,274

edits

Revision as of 22:40, 12 August 2017 (view source) Nhumfrey (talk \| contribs) (→‎Step 2) ← Older edit		Latest revision as of 11:26, 8 December 2022 (view source) AA-Andrew (talk \| contribs) m (→‎Step 1)
(One intermediate revision by one other user not shown)
__NOTOC__<indicator name="L2TP">[[File:Menu-L2TP.svg\|link=:Category:~~Incoming_L2TP~~Incoming L2TP\|30px\|Back up to the Incoming L2TP Category]]</indicator> [[Category:~~Incoming_L2TP~~Incoming L2TP]] [https://www.pfsense.org/ pfSense] is an open source firewall distribution, built on top of the FreeBSD Operating System. # Set the '''Username''' to your AAISP login # Set the '''Password''' to you AAISP password - as seen on the 'Broadband Circuit Details' page on [[Category:Control Pages\|control.aa.net.uk]] # Set the '''Gateway IP''' to '90194.~~155~~4.53172.1912' - by using an IP address you can avoid performing a DNS lookup, and having to ensure DNS works before and after the tunnel comes up. - though the IP can change - so we'd suggest actually using l2tp.aa.net.uk # No Local IP Address is required - it will be chosen automatically When you are finished, press '''Save''' at the bottom of the screen. === Step 2 === # I used the '''description'''/name 'L2TP' for my interface # Set ~~the~~ the '''IPv4 Configuration Type''' to 'L2TP' # Set ~~the~~ the '''IPv6 Configuration Type''' to 'SLAAC' - you don't actually need a global IPv6 address on the interface at all - it will just use Link Local addressing, but setting to SLAAC seems to enable IPv6 on the interface without causing any problems When you are finished, press '''Save''' at the bottom of the screen.