Docker and host cannot communicate on separate vlans

I have been transitioning my dockers and servers over to a new vlan/network. All dockers/servers can get out to the internet just fine, but they cannot communicate with the Unraid host network. All gateways live on a layer 3 switch. Trunking is set up properly between the unraid host and switch. There are currently no ACLs restricting access between networks.

4 vlans:
Vlan 3: 10.3.0.0/24 Management
Vlan 33: 10.33.0.0/24 Data
Vlan 66: 10.66.0.0/24 Guest
Vlan 99: 10.99.0.0/24 Servers/Dockers

default via 10.33.0.1 dev br0 metric 100
default via 10.3.0.1 dev br0.3 metric 110
default via 10.66.0.1 dev br0.66 metric 120
default via 10.99.0.1 dev br0.99 metric 130
10.3.0.0/24 dev br0.3 proto kernel scope link src 10.3.0.33
10.9.0.0/24 dev tun0 proto kernel scope link src 10.9.0.1
10.33.0.0/24 dev br0 proto kernel scope link src 10.33.0.33
10.66.0.0/24 dev br0.66 proto kernel scope link src 10.66.0.33
10.99.0.0/24 dev br0.99 proto kernel scope link src 10.99.0.33
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown

 docker network ls
NETWORK ID          NAME                DRIVER              SCOPE
6b3df8fc3284        br0                 macvlan             local
4141e5a41216        br0.3               macvlan             local
d39a8d8db5c2        br0.66              macvlan             local
cb92e1599c10        br0.99              macvlan             local
00f45fae7a11        bridge              bridge              local
f7b8213cd062        host                host                local
7d708d99278d        none                null                local

brctl show
bridge name     bridge id               STP enabled     interfaces
br0             8000.fcaa1499b53c       no              bond0
br0.3           8000.fcaa1499b53c       no              bond0.3
br0.66          8000.fcaa1499b53c       no              bond0.66
br0.99          8000.fcaa1499b53c       no              bond0.99
docker0         8000.02424f573247       no              veth484c2f1
                                                        vethaa05a75
virbr0          8000.52540065b66b       yes             virbr0-nic

My dockers on the 10.99.0.0 network can communicate with the Internet and can ping the gateway of the 10.33.0.1/24 network, however I can't ping 10.33.0.33 the IP address of my Unraid host. Additionally, from my Unraid host, I can ping 10.99.0.1 but cannot ping anything else on the 10.99.0.1/24 network.

I think it has something to do with the host routing/bridging. I think the 10.99.0.0 network may be able to reach the unraid host, but the host is then unable to route the traffic back properly.

From Unraid host (10.33.0.33)

traceroute 10.99.0.211
traceroute to 10.99.0.211 (10.99.0.211), 30 hops max, 60 byte packets
 1  10.99.0.33 (10.99.0.33)  3053.222 ms !H  3053.185 ms !H  3053.173 ms !H

From a docker:

root@991a253e5b66:/$ ifconfig
eth0      Link encap:Ethernet  HWaddr 02:42:0A:63:00:D7
          inet addr:10.99.0.215  Bcast:0.0.0.0  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:6602 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4374 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:3021498 (2.8 MiB)  TX bytes:653922 (638.5 KiB)
lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:252 errors:0 dropped:0 overruns:0 frame:0
          TX packets:252 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:26131 (25.5 KiB)  TX bytes:26131 (25.5 KiB)
root@991a253e5b66:/$ traceroute 10.33.0.33
traceroute to 10.33.0.33 (10.33.0.33), 30 hops max, 46 byte packets
 1  10.99.0.1 (10.99.0.1)  2.927 ms  0.484 ms  0.504 ms
 2  *  *  *
 3  *  *  *