0

Currently I run the below scheme. The problem is that when ESXi is down it takes down all the network with it, so I have to boot up another router to log in to it.

 WAN > OPNsense (in ESXi)> switch (C3560G)

OPNsense is DHCP server

Thing is that i would like the switch to deal with the DHCP, to avoid being naked when ESXi needs maintenance.

Also need to setup a VPN on OPNsense but will that be possible if 3560 is acting as the DHCP server?

Since the 3560 is L3 i could have it act as DHCP server and handle the VLANs, there's some uncertainty in an OpenVPN VLAN creation by the OPNsense.

edit1:

This is a mockup of current/future network. Some stuff is left out but are of no importance.

Topology

Current ISPmodem cannot be set to bridge, waiting for one with different FW, that will allow bridge mode.

There is a lot of space for improvement and while the office is not active for the next 2-3 weeks there is no actual rush. All comments are welcome.

About the OPNsense situation, I'm sorry if I overstepped here, I am aware of the general idea for rules here but as at my last place (~150 on site, ~20 remote users) we had a pfSense running, it actually didn't even cross my mind that this could potentially be off topic. Next edit will be with the mockup of the switch configuration with which I will require quite a lot of assistance.

So here's the very basic switch config

    Current configuration : 2717 bytes
!
version 12.2(37)SE1
no service timestamps log datetime msec
no service timestamps debug datetime msec
no service password-encryption
!
hostname c3560g
!
!
!
ip dhcp excluded-address 10.0.0.0 10.0.0.10
ip dhcp excluded-address 10.0.10.0 10.0.10.10
ip dhcp excluded-address 10.0.20.0 10.0.20.10
ip dhcp excluded-address 10.0.30.0 10.0.30.10
!
ip dhcp pool mgmt
 network 10.0.0.0 255.255.255.0
 default-router 10.0.0.1
 dns-server 10.0.0.2
 domain-name LAN
ip dhcp pool trusted
 network 10.0.10.0 255.255.255.0
 default-router 10.0.10.1
 dns-server 10.0.0.2
ip dhcp pool untrusted
 network 10.0.20.0 255.255.255.0
 default-router 10.0.20.1
 dns-server 10.0.0.2
ip dhcp pool guest
 network 10.0.30.0 255.255.255.0
 default-router 10.0.30.1
 dns-server 10.0.0.2
!
!
ip routing
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
spanning-tree mode pvst
!
!
!
!
!
!
interface FastEthernet0/1
 switchport mode access
 switchport nonegotiate
 spanning-tree portfast
!
interface FastEthernet0/2
 switchport mode access
 switchport nonegotiate
 spanning-tree portfast
!
interface FastEthernet0/3
 switchport access vlan 10
 switchport mode access
 switchport nonegotiate
 spanning-tree portfast
!
interface FastEthernet0/4
 switchport access vlan 10
 switchport mode access
 switchport nonegotiate
 spanning-tree portfast
!
interface FastEthernet0/5
 switchport access vlan 20
 switchport mode access
 switchport nonegotiate
 spanning-tree portfast
!
interface FastEthernet0/6
 switchport access vlan 30
 switchport mode access
 switchport nonegotiate
 spanning-tree portfast
!
interface FastEthernet0/7
!
interface FastEthernet0/8
!
interface FastEthernet0/9
!
interface FastEthernet0/10
!
interface FastEthernet0/11
!
interface FastEthernet0/12
!
interface FastEthernet0/13
!
interface FastEthernet0/14
!
interface FastEthernet0/15
!
interface FastEthernet0/16
!
interface FastEthernet0/17
!
interface FastEthernet0/18
!
interface FastEthernet0/19
!
interface FastEthernet0/20
!
interface FastEthernet0/21
!
interface FastEthernet0/22
!
interface FastEthernet0/23
 switchport trunk encapsulation dot1q
 switchport mode trunk
!
interface FastEthernet0/24
 switchport trunk encapsulation dot1q
 switchport mode trunk
!
interface GigabitEthernet0/1
!
interface GigabitEthernet0/2
!
interface Vlan1
 ip address 10.0.0.1 255.255.255.0
!
interface Vlan10
 mac-address 0090.0c64.7301
 ip address 10.0.10.1 255.255.255.0
!
interface Vlan20
 mac-address 0090.0c64.7302
 ip address 10.0.20.1 255.255.255.0
!
interface Vlan30
 mac-address 0090.0c64.7303
 ip address 10.0.30.1 255.255.255.0
!
ip default-gateway 10.0.0.2
ip classless
!
ip flow-export version 9
!
!
!
!
!
!
!
!
line con 0
 logging synchronous
!
line aux 0
!
line vty 0 4
 login
!
!
!
!
end

Now I will need to add some access list, hopefully avoiding restricting each vlan one by one, but will come to it if nothing pops up.

7
  • Yes, you can configure the 3560 as a DHCP server. If you provide more details, we can help with a configuration. But configuring OPNsense is off topic here.
    – Ron Trunk
    Aug 19 '20 at 12:34
  • 1
    Why is OPNsense off topic? It's a firewall product like any other. SO if it's off topic all questions about Cisco ASA, Juniper SRX, Fortigate are also off topic. And I know several people using pfsense / opensense in large production environments because other systems where pretty bad when it came top IPv6. They probably still are.
    – Jens Link
    Aug 19 '20 at 12:49
  • According to the help center, for a product to be on topic, it needs to have paid support from the manufacturer.
    – Ron Trunk
    Aug 19 '20 at 12:59
  • @JensLink, because the manufacturer of pfSense offers optional, paid support, it is on-topic, but the open-source software does not have that option.
    – Ron Maupin
    Aug 19 '20 at 13:00
  • 1
    opnsense.org/support-overview/commercial-support And in any case we could argue that there is almost no need for this site because people could use the vendor support. Thats what they are paying for.
    – Jens Link
    Aug 19 '20 at 13:06
0

Yes you can setup a VPN server and not acting as your internal network's DHCP. Your VPN system will be a DHCP and offer IPs to externally connected clients. Your L3 switch will be offering IPs to your internal network.

For this scenario to work, I have assigned another IP subnet for VPN use only, no VLAN. Of course this subnet has to be routed. I used static routes for communication between the VPN IP subnet and the rest of the IP subnets/VLANs. OpenVPN is installed on a Debian Linux VM, I can't tell if you have the flexibility to configure everything needed on OPNsense OpenVPN server, but technically it's possible to achieve what you're asking.

I don't have any proposal if you need your VPN clients to be offered IP on the same subnets and VLANs as your internal network clients.

1
  • There is no necessity for being in the same subnet or in any particular one as long as it will be able to reach all LAN devices, will be used for maintenance and the owner. 1. Access to all internal network 2. Internet access while connected.
    – Diosim
    Aug 19 '20 at 16:17

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.