POE network switch

I am not explaning it well. I have an access point (Ruckus) that is configured with two SSID. One for computers, phones and another for IoT. I have a third network on my firewall (OPNsense) with a Camera network. I want the switch to sit between the firewall and access point. When something connects to IoT it will go through the switch to the firewall as IoT (vlan2). Connect to the computer wireless and it goes to vlan 1. Finally the cameras will be connected by ethernet cables through the switch to vlan3.
Currently this works through two Netgear switchs. One Netgear switch handles the IoT and Computer networks, another handles the Cameras. Both Netgears are not managed, they are just dumb switches. They are capable of vlans, I just haven't set them up that way because the firewall and access point have been able to do the work. The camera network is on a seperate physical network interface. The IoT and Comptuter are on the same interface.
 
Does your firewall have 3 physical interfaces for these 3 networks?

How does your Ruckus have those 2 SSIDs? Is it 1 SSID per VLAN? Or 2 SSIDs on 1 VLAN?

As a simple solution, how about a config where 1/3rd of the ports are in each of the 3 VLANs? You can treat each VLAN as a separate NetGear switch.

enable
conf t
vtp dom Home
vtp mode off

vlan 10
name General
vlan 20
name IOT
vlan 30
name Camera

int range gi 1/0/1 - 8
switchport
switchport host
switchport access vlan 10
no shut
exit

int range gi 1/0/9 - 16
switchport
switchport host
switchport access vlan 20
no shut
exit

int range gi 1/0/17 - 24
switchport
switchport host
switchport access vlan 30
no shut
exit

exit
copy run start
 
Last edited:
The Ruckus has 1 SSID per VLAN.
Does your firewall have 3 physical interfaces for these 3 networks?

How does your Ruckus have those 2 SSIDs? Is it 1 SSID per VLAN? Or 2 SSIDs on 1 VLAN?

As a simple solution, how about a config where 1/3rd of the ports are in each of the 3 VLANs? You can treat each VLAN as a separate NetGear switch.
1/3 for each VLAN will work.
 
Be sure to paste it in to your switch in batches/chunks. If you paste in too much you can overrun the buffer and it'll miss characters ... messing up some things. I added empty lines to see the logical paste chunks.
 
The Ruckus has 1 SSID per VLAN.

1/3 for each VLAN will work.
OK, assuming your router/gateway/firewall is setup to use 802.1q, you just need one trunk port from it to one trunk port on the switch to carry all your VLAN traffic. Your inter-vlan routing, if you want it or don't want it, will be managed at the firewall, since this switch, since it's L2 only, won't route between VLAN's.
 
Here's how I would personally configure it, based on your description (VLAN1 untagged, VLAN2 and 3 tagged) and all devices moved to the new switch.

Once at the enabled prompt (#), type "conf t" to get into configuration mode.

1. enable modern authentication, authorization and accounting:
- aaa new-model
- aaa authentication login local_authen local
- aaa authorization login local_author local

2. Enable password encryption:
- service password-encryption

3. Create your user account:
- username YOURUSERNAME privilege 15 secret YOURPASSWORD

4. Create an enable secret for the terminal:
- enable secret YOURPASSWORD2

5. Since you don't have a separate management VLAN, give the switch an IP on your computer LAN segment:
- int vlan1
- ip address xxx.xxx.xxx.xxx 255.255.255.0 (assuming Class C)

6. Do you want the switch to be able to have accurate time, synch'd to an NTP server? If so:
- ip default-gateway xxx.xxx.xxx.xxx (your firewall's IP)
- ip name-server 208.67.222.222 (or whatever upstream DNS server you want to use, you can also put your home DNS server or firewall here depending on your local setup)
- ntp server time.nist.gov (or you can use your firewall's IP if it provides NTP)

7. Assuming port 1 is our 802.1q uplink:
- int gi1/0/1
- description uplink to firewall
- switchport mode trunk

8. Now, let's assign ports 2 - 12 to VLAN 1 (untagged)
- switchport range gi1/0/2-12
- description computer lan port
- switchport mode access
- spanning-tree portfast

9. Now, let's assign ports 13-23 to VLAN 3 (untagged)
- switchport range gi1/0/13-23
- description camera lan port
- switchport mode access
- switchport access vlan 3
- spanning-tree portfast

Now, there's a quirk where if you don't assign a port to a VLAN, the switch doesn't know the VLAN exists, so we'll temporarily assign port 24 to vlan 2, then turn it into a trunk port for your access point:

- switchport g10/0/24
- switchport access vlan 2
<will get a message about creating VLAN 2>
- no switchport access vlan 2
- description trunk to access point
- switchport mode trunk


So, in this scenario, your router/gateway/firewall, with 802.1q enabled on one of your ports, you connect that to port 1 on the switch. You can then use ports 2-12 for your computer network and ports 13-23 for your cameras. Port 24 is for your wireless access point, also using 802.1q. This assumes VLAN1 on your access point is the untagged VLAN and 2 and 3 will be tagged.

Now, let's restrict management to your LAN subnet. You can use a single IP here (just your workstation) or the entire LAN subnet. For this example, I'm going to use the subnet:

- access-list 23 permit xxx.xxx.xxx.xxx 255.255.255.0 (assuming Class C subnets in use)

And let's setup your VTY consoles for local access and SSH:

- line vty 0 4
- privilege level 15
- authorization exec local_author
- login authentication local_authen

- line vty 5 15
- access-class 23 in
- privilege level 15
- authorization exec local_author
- login authentication local_authen
- transport input ssh

And give the switch a hostname:
- hostname YOURSWITCHNAME

And then finally, commit this configuration to flash:
- exit
- copy run start
 
Last edited:
Thank you @rijndael and @OVERKILL
This switch configuration will take me the rest of the day, but I do appreciate your help.
No problem. We've both gone two different ways on this, I'm assuming 802.1q trunking, he's assuming you want to do a separate uplink for each VLAN. I'm curious to see which way you go, lol, but I assumed you wanted 802.1q (trunking) since you said you wanted all three VLAN's showing up on the access point.
 
he's assuming you want to do a separate uplink for each VLAN. I'm curious to see which way you go, lol, but I assumed you wanted 802.1q (trunking) since you said you wanted all three VLAN's showing up on the access point.

Yea, I was just trying to make an easy migration from NetGear to this, since he said he used separate (unmanaged) NetGear switches.

So moving it over one switch at a time, to predefined chunks of ports, seemed easiest.
 
Screenshot 2025-08-03 134238.webp

I get this error
 
Yes, rinjdael way is easier. I actually had it configured as he posted when Overkill posted. I decided to try Overkills configuration since I have time to work on it today.
 
Yea, I see the issue. His command of:

aaa authorization login local_author local

was the issue. login is not a valid option under authorization, it is under authentication.

3560X(config)#aaa authorization ?
auth-proxy For Authentication Proxy Services
cache For AAA cache configuration
commands For exec (shell) commands.
config-commands For configuration mode commands.
configuration For downloading configurations from AAA server
console For enabling console authorization
credential-download For downloading EAP credential from Local/RADIUS/LDAP
exec For starting an exec (shell).
multicast For downloading Multicast configurations from an AAA server
network For network services. (PPP, SLIP, ARAP)
onep For ONEP authorization service
policy-if For diameter policy interface application.
prepaid For diameter prepaid services.
radius-proxy For proxying radius packets
reverse-access For reverse access connections
subscriber-service For iEdge subscriber services (VPDN etc)
template Enable template authorization
 
Back
Top Bottom