ISP Tagged vlan
Hi,
I am working on residential building project...this building has automation (IOT) setup in each apartment...each floor have apartments and each apartment is connected to the TPlink switch (Floor Switch). each floor have tplink switch and each apartment have a vlan ...
ground floor have a tplink switch in server room and ISP provided a fiber connection which is going to tplink switch on port 28..
ISP given only tagged vlan 1300..
now problem is this, single cable is going to the apartment from the switch and isp provided the dlink router for an apartment. they given pppoe username and password.
now tell me how to do the configuration of current setup all apartments need internet..? what is the best solution.???
[color=#ffffff][url=https://ufabetyou.com/]คาสิโนออนไลน์[/url][/color]
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Firstly your network must have a gateway. If the dlink router hasn't fiber port it's your only gateway, then you may need to use the following topology.
ISP----(VLAN1300)----(port 28) tplink switch (server room) (port1)----dlink router----tplink switch (Floor Switch)
tplink switch (server room)
Create VLAN1300 and add port 28 to VLAN 1300 and should be tagged. Add port 1 to VLAN1300 and should be untagged.
dlink router
Set up PPPoE for WAN.
tplink switch (Floor Switch)
Refer to the FAQ.
https://www.tp-link.com/en/support/faq/2149/
Please set up different IP address for every switch and router to avoid IP conflict.
- Copy Link
- Report Inappropriate Content
Andone wrote
Firstly your network must have a gateway. If the dlink router hasn't fiber port it's your only gateway, then you may need to use the following topology.
ISP----(VLAN1300)----(port 28) tplink switch (server room) (port1)----dlink router----tplink switch (Floor Switch)
tplink switch (server room)
Create VLAN1300 and add port 28 to VLAN 1300 and should be tagged. Add port 1 to VLAN1300 and should be untagged.
dlink router
Set up PPPoE for WAN.
tplink switch (Floor Switch)
Refer to the FAQ.
https://www.tp-link.com/en/support/faq/2149/
Please set up different IP address for every switch and router to avoid IP conflict.
That's not what he said he has as a configuration...
Using a modification of your diagram:
(per Apartment)
|----dlink router
|----dlink router
tplink switch (server room) (port1)----tplink switch (Floor Switch)|----dlink router
|----dlink router
|----dlink router
|----dlink router
|----dlink router
ISP----(VLAN1300)----(port 28) tplink switch (server room) (port2)----tplink switch (Floor Switch)|----dlink router
|----dlink router
|----dlink router
|----dlink router
|----dlink router
tplink switch (server room) (port3)----tplink switch (Floor Switch)|----dlink router
|----dlink router
|----dlink router
The ISP connection needs to be configured on Port 28, so it needs to be configured as:
switchport general allowed vlan 1300 tagged
Then, an interface VLAN 1300 needs to be configured on the switch, with the IP address assigned by the ISP.
The other ports on the server room switch will connect to the floor switches. Assuming that they are all the same type of TP-Link switch, and are all Layer 3 capable, I would suggest setting up each of the other ports on the server room switch as Layer 3 ports (no switchport), and set up Layer 3 subnets from those routed ports to each of the floor switches, where there would also be a Layer 3 uplink port configured to connect to the server room switch.
Then, on each floor switch, configure a VLAN for the network facing the apartments, and configure the IP gateway on the VLAN interface for that VLAN. Put all of the apartment-facing switchports in that VLAN, and set up DHCP for the D-Link routers to obtain an internet facing address and default route.
This will require static routing to be configured, since the TP-Link switches do not support dynamic routing. So, the server room switch would need a default route pointing to the Internet, and static routes pointing to each VLAN subnet on the floor switches. The floor switches only need a default route pointing to the server room next hop switch.
There is a lot of design, engineering and configuration involved in this project. Way too much to detail it here in a blog post.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 1070
Replies: 2
Voters 0
No one has voted for it yet.