Docs/Switches: Difference between revisions
Jump to navigation
Jump to search
(Created page with "Our firewall/router runs [https://www.pfsense.org/ pfSense], soon to be migrated to [https://opnsense.org/ OPNsense]. All IP addressing of servers and virtual machines happens through DHCP, and can be viewed in the pfSense 'DHCP Leases' tab. (except Proxmox nodes, which don't support DHCP and require static addressing) Otherwise, most configuration can be viewed by poking around the web interface. === Firewall rules === View the WebUI for the specific firewall rules,...") |
No edit summary |
||
| Line 5: | Line 5: | ||
Otherwise, most configuration can be viewed by poking around the web interface. |
Otherwise, most configuration can be viewed by poking around the web interface. |
||
== Switches == |
|||
Our WAN is a LAGG across two ports. The link needs '''LACP enabled''' ("Static mode" '''off''' in 1Gb Ubiquiti Switch) [https://www.reddit.com/r/Ubiquiti/comments/7xs70n/lag_dynamic_vs_static/duauolg/], and '''STP off'''. |
|||
IT configures their switches to automatically shut off ports if they detect STP advertisements. |
|||
<describe vlan config> |
|||
== OPNsense == |
|||
=== Firewall Rules === |
|||
View the WebUI for the specific firewall rules, but some of the more basic/essential ones are: |
View the WebUI for the specific firewall rules, but some of the more basic/essential ones are: |
||
| Line 17: | Line 26: | ||
## Neither config should have access to WAN, just to prevent someone getting LUG in hot water if they attempt to torrent or something similarly dumb through the VPN. |
## Neither config should have access to WAN, just to prevent someone getting LUG in hot water if they attempt to torrent or something similarly dumb through the VPN. |
||
=== |
=== Routing === |
||
==== Main networks ==== |
|||
We have two main networks: |
We have two main networks: |
||
* 10.10.0.0/24 - Management (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]) |
* 10.10.0.0/24 - Management (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]) |
||
| Line 25: | Line 36: | ||
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 (so we can't do it like IT and exclusively use publicly routable addresses). |
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 (so we can't do it like IT and exclusively use publicly routable addresses). |
||
=== VPN Networks === |
==== VPN Networks ==== |
||
In addition, there are two main VPN networks: |
In addition, there are two main VPN networks: |
||
Revision as of 20:59, 22 April 2025
Our firewall/router runs pfSense, soon to be migrated to OPNsense.
All IP addressing of servers and virtual machines happens through DHCP, and can be viewed in the pfSense 'DHCP Leases' tab. (except Proxmox nodes, which don't support DHCP and require static addressing)
Otherwise, most configuration can be viewed by poking around the web interface.
Switches
Our WAN is a LAGG across two ports. The link needs LACP enabled ("Static mode" off in 1Gb Ubiquiti Switch) [1], and STP off.
IT configures their switches to automatically shut off ports if they detect STP advertisements.
<describe vlan config>
OPNsense
Firewall Rules
View the WebUI for the specific firewall rules, but some of the more basic/essential ones are:
- Management cannot communicate with LAN/WAN (the internet), and LAN cannot communicate with Management.
- Generally, Management should be restricted from everything else. (maybe even other iDrac servers?)
- OOB services tend to be super vulnerable, there are dozens of premade scripts that instapwn iDRACs and give you a root shell by just pointing them at the IP address.
- Because of this, the iDRAC web login interface should only be accessible to anyone you're okay having root on the server.
- Wireguard
- The admin/user split is so all members can be given a wireguard config to the internal network without having to worry about them being able to trivially get root on all servers running premade-exploits like these on the iDracs.
- If someone shows up to a couple meetings they're probably fine to get an admin config; this is more for peace-of-mind to not need to worry about the configs given to people who went to one meeting once at the beginning of the semester and have never been seen again.
- Neither config should have access to WAN, just to prevent someone getting LUG in hot water if they attempt to torrent or something similarly dumb through the VPN.
Routing
Main networks
We have two main networks:
- 10.10.0.0/24 - Management (OOB Management services like Dell iDRAC / HP iLO)
- 10.10.1.0/24 - LAN (servers/VMs)
We may also be getting a /27 of Tech's 141.219.0.0/16 block through IT (~28-30 usable public IP addresses).
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 (so we can't do it like IT and exclusively use publicly routable addresses).
VPN Networks
In addition, there are two main VPN networks:
- 10.10.10.0/24 - OpenVPN
- 10.10.11.0/24 - Wireguard
- 10.10.11.0/25 - Wireguard admin range (access to Management+LAN, no WAN)
- 10.10.11.128/25 - Wireguard user range (access to only LAN, no WAN)