Docs/OPNsense: Difference between revisions

Jump to navigation Jump to search
m
No edit summary
 
(9 intermediate revisions by 3 users not shown)
'''For Layer 1 network details, see [[Docs/Cables]].'''
[[Docs|<small>~/Docs</small>]]
 
'''For Layer 2 network details, see [[Docs/Switches]].'''
 
OPNsense is our router/firewall.
We have two OPNsense devices, Lasagna and Ravioli.
 
== Network ==
'''The VLAN configuration (like VLAN IDs) should probably be moved to [[Docs/Switches]] to keep this article strictly Layer3'''
 
=== Management (OOB) ===
{| class="wikitable"
!Subnet
!VLAN ID
|-
|10.10.0.0/24
|1?
|}
OOB Management services like [https://www.dell.com/en-us/lp/dt/open-manage-idrac Dell iDRAC] / [https://www.hpe.com/us/en/hpe-integrated-lights-out-ilo.html HP iLO] and internal networking hardware.
Because of this, the iDRAC web login interface should only be accessible to anyone you're okay having root on the server.
 
=== LAN ===
{| class="wikitable"
!Subnet
!VLAN ID
|-
|10.10.1.0/24
|2?
|}
Servers and Virtual Machines.
LAN cannot communicate with Management.
 
=== WAN ===
{| class="wikitable"
!Subnet
!Main WAN IP
!VLAN ID
|-
|141.219.80180.64/27
|141.219.180.69
|640
|}
Our public IP subnet under Tech's <code>141.219.0.0/16</code> block.
 
The plan is to use reverse-NAT to map the public IPs to select internal IPs, since we won't have enough IPs for every VM.
 
== VPN Networks ==
 
=== OpenVPN ===
{| class="wikitable"
!Subnet
!VLAN ID
|-
|10.10.10.0/24
|N/A
|}
 
 
OpenVPN can be used as a secondary admin/user option compared to wireguard or can be used for homelab routing. This allows devices on a members network to communicate directly with lug devices, depending on what is configured on the user side and the server's side.
 
=== Wireguard ===
{| class="wikitable"
!Subnet
!VLAN ID
|-
|10.10.11.0/24
|N/A
|}
<code>10.10.11.0/25</code> - Wireguard admin range (access to LAN+Management)
<code>10.10.11.128/25</code> - Wireguard user range (access to only LAN)
 
All members can be freely givenrequest 'user' wireguard configsconfigurations to connect to LUG infrastructure. OnlyThese admin'user' configs needare restricted to beLUG's restrictedLAN network only. (due to the aforementioned iDrac exploit issues).
 
Neither wireguard config should have access to the internet and are not intended for standard VPN traffic through LUG as an exit.▼
 
Endpoint networks can be configured as needed but OpenVPN may be preferred for this usecase as LUG/users can dynamically change routes/receive DHCP updates.
 
=== pfsync ===
{| class="wikitable"
!Subnet
|-
|10.10.250.0/24
|}
Interface used for High Availability (HA) sync between the 2 firewalls.
 
Cannot communicate with any other subnet.
 
== OPNSense ==
▲Neither wireguard config should have access to the internet.
<Rules for access, updates, generating wireguard configs, etc>
42

edits

Navigation menu