@scottalanmiller we have an ERP system that MOST of the companies work is done in.

They could still use office and such, but without the link the ERP stuff is useless. Production could continue on paper, it would just slow down

Email isnt local either, we use cloud based email which is stemmed from the datacenter.

That is a good point thank you for mentioning that

UPDATE:
This is just a copy and paste from my message to SAM btw

I got the firmware updated on all my devices and I got my network up. Not like I want though.

So I had it working with VLANS(as in DHCP, DNS, and routing were working), but then i had issues because my AP (10.0.10.2) couldnt connect to the desk(which is the wireless controller) which is 10.0.20.2

It had something to do with L3 integration on the AP, and I spent 9 hours on the support with Ubiquiti. They basically told me to wait for the next patch for the L3 support.

So i had to remove my vlans and just have a flat network. :((((

So with tagging vlans, i have a question:
the ports you tag on are the "trunks" in cisco terms?

On my switch, what i did is i tagged ports 1, and 8
1 is the AP, and then 8 is the switch->router port
I did this on both vlan 10 and vlan 20
this makes it so that if vlan 20 traffic goes to the wireless it will actually work correct?

I have a TPLink SG108PE.
It can do 802.1Q Vlanning. I have 8 ports and you can assign a PVID per port, and also assign which ports are tagged and untagged.

Port 1 goes to my AP, so it will be be a "trunk" in cisco terms.
Port 8 goes to the router, so it will be to be a "trunk"

Ports 3-7 will be vlan 20, and
port 2 will be 10

Wired is vlan 20
wireless is vlan 10

Am I correct in that ports 1 and 8 need to be tagged for both vlan 10 and 20, and that they are untagged for 2-7?

Am I correct in that ports 3-7 will have a PVID of 20, and port 2 will have a PVID of 10?

Am i correct in that ports 1 and 8 will have a PVID of 1 (the default)?