Does a DHCP switch exist?
Solved/Closed
fg03
Posted messages
515
Registration date
Status
Contributeur
Last intervention
-
brupala Posted messages 111942 Registration date Status Membre Last intervention -
brupala Posted messages 111942 Registration date Status Membre Last intervention -
Hello,
I wanted to know if there is a switch with around 16 ports that can perform DHCP?
The idea is that since we have the headquarters as well as different branches, employees can come with their laptop from one branch to another and plug in easily!
Moreover, since the sites are connected via VPN, but only have a server at headquarters, is it possible to manage the different extended zones that a DHCP switch would provide from the server? Does the switch need to have an 802.3 certification or something?
The DHCP relay server on the routers is not possible; otherwise, that was the solution I was considering.
Thank you.
I wanted to know if there is a switch with around 16 ports that can perform DHCP?
The idea is that since we have the headquarters as well as different branches, employees can come with their laptop from one branch to another and plug in easily!
Moreover, since the sites are connected via VPN, but only have a server at headquarters, is it possible to manage the different extended zones that a DHCP switch would provide from the server? Does the switch need to have an 802.3 certification or something?
The DHCP relay server on the routers is not possible; otherwise, that was the solution I was considering.
Thank you.
5 réponses
It's crazy, sometimes I feel like I'm talking to the walls!
I’m not asking for an explanation on what to do.
I just want to know if it exists?
Someone told me it existed and I was surprised!
By the way, I haven't found any online while doing my research.
> Kalamit: I’ll just tell you that the roles can be played by whatever you want! You buy a firewall, a VPN router... or you build a PC to do the same thing... there are no rules!
I’m not asking for an explanation on what to do.
I just want to know if it exists?
Someone told me it existed and I was surprised!
By the way, I haven't found any online while doing my research.
> Kalamit: I’ll just tell you that the roles can be played by whatever you want! You buy a firewall, a VPN router... or you build a PC to do the same thing... there are no rules!
So to be clear, yes, there are DHCP switches
now it's up to you to do some research among the different manufacturers (BATM, Cisco, 3Com, Nortel,...) and to look at the datasheets according to your budget
--
Sincerely
@ + Seb
now it's up to you to do some research among the different manufacturers (BATM, Cisco, 3Com, Nortel,...) and to look at the datasheets according to your budget
--
Sincerely
@ + Seb
hi
why do you want a DHCP switch?
you need a PC that provides addresses to the PCs on your network, that's your server. Can't it provide IP addresses to all the PCs after a regular switch?
why do you want a DHCP switch?
you need a PC that provides addresses to the PCs on your network, that's your server. Can't it provide IP addresses to all the PCs after a regular switch?
Yes, in the context of a LAN.
But in the context of a WAN with multiple LANs connected via VPN-type links, the address ranges are different.
The ideal solution would be to have a server in each branch that can synchronize, but the cost is much less ideal.
There would be the solution of having a single DHCP server that would manage multiple zones, but that means the routers allow requests to pass, which is not our case.
There could eventually be the solution of setting up low-cost Linux-based servers in each branch... we'll see! There are surely dedicated distributions for this purpose (I believe they use a distro at AFPA that can be configured remotely via a web service and offers VPN, FTP/web server functions, etc...
Otherwise, if the DHCP switch exists and allows creating an extended zone and specifying a DNS/WINS server, it will be even simpler and I won't have to set up old PCs to act as servers.
But in the context of a WAN with multiple LANs connected via VPN-type links, the address ranges are different.
The ideal solution would be to have a server in each branch that can synchronize, but the cost is much less ideal.
There would be the solution of having a single DHCP server that would manage multiple zones, but that means the routers allow requests to pass, which is not our case.
There could eventually be the solution of setting up low-cost Linux-based servers in each branch... we'll see! There are surely dedicated distributions for this purpose (I believe they use a distro at AFPA that can be configured remotely via a web service and offers VPN, FTP/web server functions, etc...
Otherwise, if the DHCP switch exists and allows creating an extended zone and specifying a DNS/WINS server, it will be even simpler and I won't have to set up old PCs to act as servers.
You can configure each switch L at each agency to have an allocated DHCP range with DHCP options, or alternatively, on your routers, you need to add, if it exists, the DHCP relay function by specifying the IP address of the DHCP server. As a result, the routers will relay the DHCP client requests or the server you have specified.
That’s not at all its role.
This role is attributed to the upper layers: routers or servers.
And that's just fine.
Already, I find that some switches where you can configure VLANs by protocol, or even by IP subnet, are a bit outside their domain, unless they are L3 switches, of course.
Let everyone do their job and do it well.
We’re not asking for more.
A switch should be transparent to everything at the IP level (except its own address, of course).
To conclude more clearly:
It does not exist on L2 switches, but it does exist on L3 switches (routers) such as the Catalyst 3550.
--
And ... Voili Voilou Voila!
today we find manageable switches with DHCP server, as they lack a console port, and to connect to the HTTP interface, a minimum configuration of the PC is required.
But it's just for accessing the initial configuration, then we remove it because it generates a conflict with the real servers that provide gateway and DNS and other things potentially.