TP SG108PE + Ubiquiti Edge Router
-
I bought an AP, router, and switch online so I can have a bit more advanced setup at home. The switch is a tplink sg108pe, which has 8 ports, 4 of them being POE, and a bunch of goodies. The router is an edgerouter x from ubiquiti. I was screwing around with it yesterday and the UI is fantastic. The AP is a ubiquiti uap-lite.
I set up DHCP and vlans on the router yesterday. I didnt set up a routing since its just the one router and switch. Eth0 on the router goes to port 8 of the switch, port 1 on the switch goes to AP, port 7 is my desktop.
Vlans are
20: wireless- 10.0.20.0/24
30: wired- 10.0.30.0/24i have the ip on the router set to 10.0.0.1 and the switch at 10.0.0.2
DHCP doesnt appear to be working, i have to statically set my addresses
For some reason, I cant get the vlans to work on my switch. There isnt an option(or i dont see it) to set up a trunk from port 8 to the router,
Can you guys help me figure this out, and explain why I am doing what I am doing?
Any help would be appreciated, feel free to ask questions because I amsure I forgot something.
-
Several switches don't have a "Trunk" settings... what I've done in the past is just set up all the vlans as tagged on the port that would be the trunk.
-
@brianlittlejohn so there is an option to tag vlans and ports, but it doesnt designate which one would be the "uplink".
THe switch has options for MTU vlan, 802.1Q, then port based vlan. Port based was only vlan 2-8, so i couldnt even use it.
The MTU didnt seem to do anything, and 802.1Q allows me to specify which vlan a port is and whether its tagged, but not if i can specify an "uplink"
-
@cteneyck There is nothing special about an "uplink" port. In the past they were designated ports for crossover connections, but now with MDIX you no longer need to worry about it. The "trunk" setting that is on Cisco switches etc, all it does is tag all the vlans on the port, so If you go in and tag all the vlans you are using on that port it should work.
-
http://www.tp-link.us/faq-788.html
there is a link to what the web gui looks like. Maybe I am oblivious but its really confusing. Why are there two untagged vlans? how does that even work
-
@cteneyck From the link you sent, it appears they are using Port 1 as the "Trunk" port... If you look at the diagrams where they are tagging VLAN 101 and VLAN 102, they tag it on port 1, they are using ports 2-4 for vlan 101 (leaving untagged for no vlan aware devices) and ports 4-8 for vlan 102 (untagged for non vlan aware devices)
-
Alright. Ill try that. Does the rest of my configuration look good? Should I change anything?
-
Can i get a bump? I wont have internet after i get off work and I want to make sure everything from above looks good. I dont need a MGMT vlan do i?
-
For HOME? No, a management VLAN is not critical for home use.
-
@scottalanmiller does the IP addressing and general setup look good?
-
@cteneyck said in TP SG108PE + Ubiquiti Edge Router:
http://www.tp-link.us/faq-788.html
there is a link to what the web gui looks like. Maybe I am oblivious but its really confusing. Why are there two untagged vlans? how does that even work
Tagging is just one way to VLAN, it's the common one, but not the only kind.
-
@scottalanmiller good to know
-
Address scheme seems fine.
-
Oh , before I forget.
The AP im assuming gets an IP address. Should I put it in the wireless vlan(10.0.30.0) or should i put it in the seperate subnet(10.0.0.0) just like the switch and router?
-
@cteneyck said in TP SG108PE + Ubiquiti Edge Router:
Oh , before I forget.
The AP im assuming gets an IP address. Should I put it in the wireless vlan(10.0.30.0) or should i put it in the seperate subnet(10.0.0.0) just like the switch and router?
The AP itself is untagged by default.
-
@JaredBusch so 10.0.0.3 would work?
-
Here are some pictures from my adventure last night. I spent several hours trying to get it to work but gave up. I got the vlans to work, as show by the pings. However, I cant get anything to route. I dont know what the route to leave my router needs to be because i dont know what the address on the other side is. do i need to do something to figure that our or is there a tool in the router that can do that? also,do i need to nat, and how should i set that up.
-
@cteneyck, first you need to forget about doing anything with a VLAN. Create your flat network. Get all the wired devices working.
Then add VLAN tags to the switch ports that the router and access point are plugged into. At that point a device on the wifi should pull an ip from the router.
Remember this is why you see @scottalanmiller and myself always recommending a flat network. VLANS add complication. You are doing this to learn about them, so that is good. But this is exactly why VLANS do not belong in a network with very specific reasons.
-
The VLANS are working, i just cant get outside my network now because i have no idea how to get the IP of the device on the other side of my wall jack. How do i set that up
-
@cteneyck by starting over. You jumped in the middle without ever getting the beginning done.
start with a flat network and a working router config then you add complexity.
