Just to clarify, yes intervlan works rather easilly once you get a copy of the routing firmware for this switch.
Follow this tutorial [routing firmware included in this guys tutorial].
Here is a copy of my running config:
(Routing) #write me
This operation may take a few minutes.
Management interfaces will not be available during this time.
Are you sure you want to save? (y/n) y
Configuration Saved!
(Routing) #
(Routing) #show run
!Current Configuration:
!
!System Description "FASTPATH Routing"
!System Software Version "5.13.12.14"
!System Up Time "7 days 19 hrs 32 mins 37 secs"
!Additional Packages FASTPATH QOS,FASTPATH Multicast
!Current SNTP Synchronized Time: AUG 06 12:49:28 201 UTC
!
serviceport protocol none
serviceport ip 192.168.255.1 255.255.255.252 192.168.255.2
network parms 192.168.255.5 255.255.255.252 192.168.255.6
vlan database
vlan 200,254-255,300
vlan name 200 "wired user"
vlan name 300 "wlan user"
vlan name 254 "servers"
vlan name 255 "egress wan"
vlan routing 255
vlan routing 300
vlan routing 200
vlan routing 254
exit
no ip http java
ip http secure-server
ip ssh server enable
ip ssh protocol 2
no ip telnet server enable
configure
snmp-server sysname "asteria"
snmp-server location "laundry-room-tr"
!
sntp client mode unicast
! sntp server status is active
sntp server 172.16.255.1
no ip domain lookup
ip domain name xxxxxxxxx.net
ip routing
ip route 0.0.0.0 0.0.0.0 172.16.255.1
bootpdhcprelay enable
bootpdhcprelay serverip 172.16.2.253
users passwd "admin" encrypted 974b0f3f6f87a812129529.........
lineconfig
no transport input telnet
exit
spanning-tree configuration name "60-EB-69-A9-14-A9"
spanning-tree forceversion 802.1w
port-channel apollo-nas
no port-channel linktrap 3/1
interface 0/3
addport 3/1
exit
interface 0/4
addport 3/1
exit
interface 0/1
no shutdown
spanning-tree edgeport
vlan pvid 255
vlan participation exclude 1
vlan participation include 255
vlan tagging 255
ip irdp
exit
interface 0/2
no shutdown
spanning-tree edgeport
vlan pvid 200
vlan participation exclude 1
vlan participation include 200,254
vlan tagging 200
exit
interface 0/3
no shutdown
lacp actor admin key 54
exit
interface 0/4
no shutdown
lacp actor admin key 54
exit
interface 0/5
no shutdown
spanning-tree edgeport
vlan pvid 300
vlan participation exclude 1
vlan participation include 300
exit
interface 0/6
no shutdown
spanning-tree edgeport
vlan pvid 200
vlan participation exclude 1
vlan participation include 200,300
exit
interface 0/7
no shutdown
spanning-tree edgeport
vlan pvid 254
vlan participation exclude 1
vlan participation include 254
vlan tagging 254
exit
interface 0/10
no shutdown
spanning-tree edgeport
vlan pvid 200
vlan participation exclude 1
vlan participation include 200
exit
interface 3/1
no shutdown
port-channel static
no snmp trap link-status
spanning-tree edgeport
no spanning-tree port mode
vlan pvid 200
vlan participation exclude 1
vlan participation include 200
lacp collector max-delay 0
exit
interface 4/1
no shutdown
routing
ip address 172.16.255.2 255.255.255.252
exit
interface 4/2
no shutdown
bandwidth 10000
routing
ip address 172.16.3.1 255.255.255.0
ip irdp
ip mtu 1500
exit
interface 4/3
no shutdown
bandwidth 10000
routing
ip address 172.16.2.1 255.255.255.0
ip irdp
ip mtu 1500
exit
interface 4/4
no shutdown
bandwidth 10000
routing
ip address 172.16.254.1 255.255.255.0
ip irdp
ip mtu 1500
exit
router rip
no enable
exit
router ospf
no enable
exit
exit
!!!!!!!!
Many of the folks here complain about the GUI, but its not too bad. Most places actually have the webgui on switches and routers disabled to minimize attack surface. The gui on this firmware "gets you to where you need to go" so to speak.
This configuration uses 4 vlans (2 user vlans, 1 server/admin vlan, 1 /30 Point-to-point vlan), 1 port channel (0/3 and 0/4), NTP, inter vlan routing, basic RSTP, DHCP relay, and i'm working on SNMP now. My only complaint is that there is no NAT on this switch. I use Windows Server 2016 standard for DNS and DHCP. Don't try to use the dhcp server on this switch. I could not get it to work.
On port 2, I have a trunk link connected to a 1Gb port on my ESXi server. The vswitch configured there handles the tagging, so hosts [ethernet adapters] that I assign to that vswitch join vlan 200 seamlessly.
As for BGP, this switch appears not to have that functionality as far as i can tell.