Welcome to TP-LINK Tech Support Forum
+ Reply to Thread
Results 1 to 13 of 13
  1. #1

    TL-SG3424P DHCP Question

    Model :

    Hardware Version :

    Firmware Version :

    ISP : [/COLOR]

    Good day everyone,

    Now we have a juniper with 3 vlans configured. Its still a 10/100 and we want to change it.
    We bought a TL-SG3424P Switch.
    I already configured 4vlan's (1 for shop, 1 for technical department, 1 for wifi and 1 to connect ip-phones with POE in the future).

    Is it possible to configure the dhcp on this switch? Or is it not possible on this switch and do i have to work with a router/modem before the switch?
    If its possible how do i have to configure it? Every vlan needs a other ip-range (besides vlan4 the phones it may have the same ipadres of vlan 1)
    If its not possible, what mode/router do you advice where i can configure 3 different dhcp ranges?

  2. #2
    Members R1D2 is on a distinguished road
    Join Date
    Dec 2015
    Posts
    1,300
    Quote Originally Posted by PC Action View Post
    Is it possible to configure the dhcp on this switch? Or is it not possible on this switch and do i have to work with a router/modem before the switch?
    No, the TL-SG3424 is a L2 switch, it has no DHCP server function. You need to set up a separate DHCP server.

    If its not possible, what mode/router do you advice where i can configure 3 different dhcp ranges?
    How do you realize DHCP services with the 3 VLANs of the Juniper? Could this DHCP server not serve another IP range, too? If not, I would recommend a Linux-based system, either a server system or some SoC running Linux. This would give you any flexibility needed to set up any environment one can think of.

  3. #3
    Quote Originally Posted by R1D2 View Post
    How do you realize DHCP services with the 3 VLANs of the Juniper?
    Its configured on te juniper like this, so the juniper gives them. We have a normal mobem of our isp that just gives a ipadress.

    is it the only L3 switches that have dhcp function on them?

  4. #4
    Simply, dhcp is one of the basic function to define a L3 switch. But some other L2 switch can also has this function, like TP-Link T2600G series.

  5. #5
    Well the TL-SG3424P is actually the T2600G-28MPS.
    Now if i put a gigabit router before the switch, how can i configure it that vlan1 get IP-adres from 192.168.9.2 to 192.168.9.75 and vlan 2 get IP-adres from 192.168.9.76 to 192.168.9.150 and vlan 3 get IP-adres from 192.168.9.151 to 192.168.9.230?
    Can i specific it somewhere?
    It is als that a couple of pc's from vlan 2 needs to print to priners that are in vlan 1, how can i do that?

  6. #6
    Members R1D2 is on a distinguished road
    Join Date
    Dec 2015
    Posts
    1,300
    I don't still understand why you do not configure the fourth DHCP pool on the Juniper, which already provides DHCP services for the other three VLANs?

    Configuration of the DHCP server on a router depends on the DHCP software it runs. But with almost all DHCP servers, it is just a matter of defining the IP address range, interface and lease time. How to do this depends on the software you use for your router or the Juniper switch.

    As for the T2600G-28MPS: this is the new model name for the TL-SG3424P. It is still a L2 switch with almost the same functionality as the TL-SG3424P. The T2700 series are the L2+ switches with a DHCP server on board.

    As to your question how to use VLAN1 printers from VLAN2: you need to set up inter-VLAN routing. This can be done either on the router or the Juniper or the T2600G. Just define interfaces for both VLANs, assign those interfaces an IP address from the subnet used in the VLANs and set up static routes. See the User's Guide for examples how to do this. There is also an older post somewhere in this forum in which I gave step-by-step instructions how to setup inter-VLAN routing, just search for it.

  7. #7
    The juniper has to go. Because its a 10/100 and it also starts to give errors. So we have to replace it with something else.
    Thats why my collegue ordered this one, but he didnt watch for the dhcp...
    Oke i will try something more with a other router.
    I will search for the otherpost of you.
    Allready a big thanks for the answers and help!

  8. #8
    Members R1D2 is on a distinguished road
    Join Date
    Dec 2015
    Posts
    1,300
    I see. I would recommend a Linux-based router (e.g. a fast hardware with Debian or LEDE) if you are UNIX-savvy.

    As for inter-VLAN routing I found the post, it's here: http://forum.tp-link.com/showthread....l=1#post211076

  9. #9
    Thx for the link. I will try it this weekend.
    Do you know a good router? But even it is with a unix system on it, is it still posible to configur it through a web-based platform?
    Because to only work with commands its alleady been to long ago..
    Would it be possibl to make a DHCP server on a raspberry-pi?

  10. #10
    Members R1D2 is on a distinguished road
    Join Date
    Dec 2015
    Posts
    1,300
    Quote Originally Posted by PC Action View Post
    Do you know a good router? But even it is with a unix system on it, is it still posible to configur it through a web-based platform?
    If you want a web UI, take a look at the EdgeRouter and/or EdgeRouter-X from UBNT.

    Because to only work with commands its alleady been to long ago..
    For advanced settings you would even need to go to the command line interface (CLI) on EdgeRouters and any other UNIX-based system, too, albeit for standard procedures they offer a nice and also powerful web UI.

    Would it be possibl to make a DHCP server on a raspberry-pi?
    If it runs Linux: sure. But I have no idea wether it supports features like hardware off-loading, so before choosing a platform for routing make sure it will achieve the bandwidth needed. For example, the EdgeRouters perform with up to 300 Mbit/s NAT throughput on their interfaces in standard (web UI) config, although this can be raised up to 900 Mbit/s NAT throughput if hardware offloading is enabled through the CLI.

    I don't know RasPi's features nor even their architecture, so can't give a recommendation.

  11. #11
    Thx for all the info R1D2!
    For now i'm just going to put a normal gigabit router before the switch with only one dhcp pool but with the vlans in it.
    Now i have one problem. on port one there was standard a vlan1 with a ipadress i installed (to manage it) 192.168.9.2
    The router has ipadres 192.168.9.1 with dhcp 192.168.9.2 - 192.168.9.254
    now when i put the cable from the router in port 1 i cannot go on the inernet. I lose the connection.
    When i put the cable in port 2 then i can connect with intenet.
    can i not use port 1? Or is thee a way that i use port 1 that connects from the router and use the other ports to go on internet

  12. #12
    Oke here i am again... I was looking further yesterday and today and also tested today.
    When i connect our server to vlan 10 and a pc to vlan 20 i still can go to the documents on the server (it should not be possible to cces the files from the) what am i doing wrong?
    Also thinking about to put the switch to factory defaults and start over...
    Th meaning would be to connect the inrnet connection from the router to port 1.
    Then create vlan 10 (shop) on ports 2 - 10 and create a vlan 20 (technical department) on pôrts 11-20.
    The pc's we connect to vlan 20 should not connect with the serve and pc's that will be connect on vlan 10. But they als need to go to internet...
    I hope someone can help me clear it a little bit out.

    Alleady a big thx for all th support here ;-)

  13. #13
    Members R1D2 is on a distinguished road
    Join Date
    Dec 2015
    Posts
    1,300
    If you assign all ports to the same subnet, the router will forward packets of all devices in this subnet regardless of the VLANs used for transport.

    On the router, you need to a) assign an own interface for each separate subnet which should handle the devices in a VLAN and b) use firewalling (or ACLs) to prevent inter-VLAN routing.


 

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts

Copyright © 1996-2018 TP-LINK Technologies Co., Ltd. All rights reserved.