DHCP sevrer on VLAN

› Forums › Network Management › ZeroShell › DHCP sevrer on VLAN

  • This topic is empty.
Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • August 28, 2014 at 4:40 pm #44026
    staifan13
    Member

    Hi all,
    How do I do too run the DHCP server on a VLAN ?

    I ask this because my DHCP server works fine on several IP ranges on my ETH01 network interface (192.168.1.0/24, 192.168.2.0/26 and 192.168.3.0/26). I just created the VLAN ETH01.1 with IP 192.168.254.0/26 but I can not run the DHCP server on that VLAN.
    If anyone can help me thank you in advance .

    Staifan

    I run ZS 3.1.0

    This is teh DHCPD log :


    
17:53:44 	Internet Systems Consortium DHCP Server V3.1-ESV
    
17:53:44 	Copyright 2004-2010 Internet Systems Consortium.
    
17:53:44 	All rights reserved.
    
17:53:44 	For info, please visit https://www.isc.org/software/dhcp/
    
17:53:44 	WARNING: Host declarations are global. They are not limited to the scope you declared them in.
    
17:53:44 	Internet Systems Consortium DHCP Server V3.1-ESV
    
17:53:44 	Copyright 2004-2010 Internet Systems Consortium.
    
17:53:44 	All rights reserved.
    
17:53:44 	For info, please visit https://www.isc.org/software/dhcp/
    
17:53:44 	WARNING: Host declarations are global. They are not limited to the scope you declared them in.
    
17:53:44 	Internet Systems Consortium DHCP Server V3.1-ESV
    
17:53:44 	Copyright 2004-2010 Internet Systems Consortium.
    
17:53:44 	All rights reserved.
    
17:53:44 	For info, please visit https://www.isc.org/software/dhcp/
    
17:53:44 	WARNING: Host declarations are global. They are not limited to the scope you declared them in.
    
17:53:44 	Wrote 0 deleted host decls to leases file.
    
17:53:44 	Wrote 0 new dynamic host decls to leases file.
    
17:53:44 	Wrote 0 leases to leases file.
    
17:53:44 	Listening on LPF/ETH01.1/00:24:01:ee:18:83/192.168.254.0/26
    
17:53:44 	Sending on LPF/ETH01.1/00:24:01:ee:18:83/192.168.254.0/26
    
17:53:44
    
17:53:44 	No subnet declaration for VPN99 (192.168.250.254).
    
17:53:44 	** Ignoring requests on VPN99. If this is not what
    
17:53:44 	you want, please write a subnet declaration
    
17:53:44 	in your dhcpd.conf file for the network segment
    
17:53:44 	to which interface VPN99 is attached. **
    
17:53:44
    
17:53:44
    
17:53:44 	No subnet declaration for ETH00 (192.168.0.75).
    
17:53:44 	** Ignoring requests on ETH00. If this is not what
    
17:53:44 	you want, please write a subnet declaration
    
17:53:44 	in your dhcpd.conf file for the network segment
    
17:53:44 	to which interface ETH00 is attached. **
    
17:53:44
    
17:53:44 	Listening on LPF/ETH01/00:24:01:ee:18:83/SN_192.168.1.0M255.255.255.0_192.168.2.0M255.255.255.192_192.168.3.0M255.255.255.192
    
17:53:44 	Sending on LPF/ETH01/00:24:01:ee:18:83/SN_192.168.1.0M255.255.255.0_192.168.2.0M255.255.255.192_192.168.3.0M255.255.255.192
    
17:53:44 	Sending on Socket/fallback/fallback-net
    
17:53:44 	There's already a DHCP server running.
    
17:53:44
    
17:53:44 	If you did not get this software from ftp.isc.org, please
    
17:53:44 	get the latest from ftp.isc.org and install that before
    
17:53:44 	requesting help.
    
17:53:44
    
17:53:44 	If you did get this software from ftp.isc.org and have not
    
17:53:44 	yet read the README, please read it before requesting help.
    
17:53:44 	If you intend to request help from the dhcp-server@isc.org
    
17:53:44 	mailing list, please read the section on the README about
    
17:53:44 	submitting bug reports and requests for help.
    
17:53:44
    
17:53:44 	Please do not under any circumstances send requests for
    
17:53:44 	help directly to the authors of this software - please
    
17:53:44 	send them to the appropriate mailing list as described in
    
17:53:44 	the README file.
    
17:53:44
    
17:53:44 	exiting.
    
17:53:44 	WARNING: Host declarations are global. They are not limited to the scope you declared them in.
    
17:53:44 	Wrote 0 deleted host decls to leases file.
    
17:53:44 	Wrote 0 new dynamic host decls to leases file.
    
17:53:44 	Wrote 0 leases to leases file.
    
17:53:44
    
17:53:44 	No subnet declaration for VPN99 (192.168.250.254).
    
17:53:44 	** Ignoring requests on VPN99. If this is not what
    
17:53:44 	you want, please write a subnet declaration
    
17:53:44 	in your dhcpd.conf file for the network segment
    
17:53:44 	to which interface VPN99 is attached. **
    
17:53:44
    
17:53:44
    
17:53:44 	No subnet declaration for ETH00 (192.168.0.75).
    
17:53:44 	** Ignoring requests on ETH00. If this is not what
    
17:53:44 	you want, please write a subnet declaration
    
17:53:44 	in your dhcpd.conf file for the network segment
    
17:53:44 	to which interface ETH00 is attached. **
    
17:53:44
    
17:53:44 	Internet Systems Consortium DHCP Server V3.1-ESV
    
17:53:44 	Copyright 2004-2010 Internet Systems Consortium.
    
17:53:44 	All rights reserved.
    
17:53:44 	For info, please visit https://www.isc.org/software/dhcp/
    
17:53:44 	WARNING: Host declarations are global. They are not limited to the scope you declared them in.
    
17:53:44 	Wrote 0 deleted host decls to leases file.
    
17:53:44 	Wrote 0 new dynamic host decls to leases file.
    
17:53:44 	Wrote 0 leases to leases file.
    
17:53:44 	Listening on LPF/ETH01.1/00:24:01:ee:18:83/192.168.254.0/26
    
17:53:44 	Sending on LPF/ETH01.1/00:24:01:ee:18:83/192.168.254.0/26
    
17:53:44
    
17:53:44 	No subnet declaration for VPN99 (192.168.250.254).
    
17:53:44 	** Ignoring requests on VPN99. If this is not what
    
17:53:44 	you want, please write a subnet declaration
    
17:53:44 	in your dhcpd.conf file for the network segment
    
17:53:44 	to which interface VPN99 is attached. **
    
17:53:44
    
17:53:44
    
17:53:44 	No subnet declaration for ETH00 (192.168.0.75).
    
17:53:44 	** Ignoring requests on ETH00. If this is not what
    
17:53:44 	you want, please write a subnet declaration
    
17:53:44 	in your dhcpd.conf file for the network segment
    
17:53:44 	to which interface ETH00 is attached. **
    
17:53:44
    
17:53:44 	Listening on LPF/ETH01/00:24:01:ee:18:83/SN_192.168.1.0M255.255.255.0_192.168.2.0M255.255.255.192_192.168.3.0M255.255.255.192
    
17:53:44 	Sending on LPF/ETH01/00:24:01:ee:18:83/SN_192.168.1.0M255.255.255.0_192.168.2.0M255.255.255.192_192.168.3.0M255.255.255.192
    
17:53:44 	Sending on Socket/fallback/fallback-net
    
17:53:44 	There's already a DHCP server running.
    
17:53:44
    
17:53:44 	If you did not get this software from ftp.isc.org, please
    
17:53:44 	get the latest from ftp.isc.org and install that before
    
17:53:44 	requesting help.
    
17:53:44
    
17:53:44 	If you did get this software from ftp.isc.org and have not
    
17:53:44 	yet read the README, please read it before requesting help.
    
17:53:44 	If you intend to request help from the dhcp-server@isc.org
    
17:53:44 	mailing list, please read the section on the README about
    
17:53:44 	submitting bug reports and requests for help.
    
17:53:44
    
17:53:44 	Please do not under any circumstances send requests for
    
17:53:44 	help directly to the authors of this software - please
    
17:53:44 	send them to the appropriate mailing list as described in
    
17:53:44 	the README file.
    
17:53:44
    
17:53:44 	exiting.
    August 28, 2014 at 4:53 pm #53436
    redfive
    Participant

    In DHCP section , “New” button, you should be able to find the new 192.168.254.0/26 network, and then create the scope.
    Regards

    August 28, 2014 at 6:03 pm #53437
    staifan13
    Member

    It’s already done . In the log the DHCP server seems to work but the client doesn’t colect the IP .

    August 28, 2014 at 7:10 pm #53438
    redfive
    Participant

    But are you using a managed switch or anyway a vlan aware device, between Zs and the client ? If not , the client will get the ip address from the network which is on the untagged/native vlan, not from the tagged one.
    Regards

    August 30, 2014 at 1:02 pm #53439
    staifan13
    Member

    redfive,
    it’s that . I have a switch between ZS and the client . So I looked here and there on the web and I realized that most of the switch handle or not VLAN. So I lean over and thank you for the information.

  • Author
    Posts
Viewing 5 posts - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.