FireBrick Road Warrior FireBrick Config: Difference between revisions

FireBrick Road Warrior FireBrick Config (view source)

10 bytes added , 28 July 2023

no edit summary

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

42

edits

Revision as of 09:25, 14 December 2018 (view source) AA-Andrew (talk \| contribs) m (→‎Configuration) ← Older edit		Latest revision as of 07:49, 28 July 2023 (view source) AA-James (talk \| contribs) No edit summary
(One intermediate revision by one other user not shown)
==Overview== In this example we are assuming you can allocate some IP addresses on ~~you~~your LAN. You do this by picking a range of addresses and setting up a roaming-pool (see below). You need to ensure the IP range does not clash with devices on the LAN and is not in the DHCP ranges that could allocate to the LAN. The FireBrick needs a configuration for the connection, and roaming pools and user identities. The connection can be used for any number of devices at once with the same pool of IP addresses; each would have a user name and password defined. </syntaxhighlight> Note: the <tt>force-NAT="0.0.0.0/0"</tt> forces keep-alives which are needed when NAT is involved between the endpoints but and also helps where stateful firewalls are in the route too. (without this set, you may find that the ipsec tunnel drops every hour or so) Each roaming user then needs an <tt>eap</tt> user record. This goes with any user entries near the top of the config.