Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm running a DHCP on Suse 10.1. All is working 100%, except when it assigns IP's it assigns the last available IP in the range, instead of the first one! What am I missing?? Any help would be appreciated. Thanks
DHCPD.CONF:
option time-servers 10.0.0.1;
option domain-name "mydomain.com";
option domain-name-servers 10.0.0.1, 11.0.0.1;
option routers 10.0.0.1;
option ntp-servers 10.0.0.1;
option lpr-servers 10.0.0.1;
option netbios-name-servers 10.0.0.1;
log-facility local7;
# File with key we shall use to securely update zone files
##########################################################
include "/etc/secret.id";
# Our server is authority
#########################
server-identifier Server.mydomain.com;
authoritative ;
# Zone specification
###########################################
zone mydomain.forward { primary 10.0.0.1; key DHCP_UPDATER;}
zone mydomain.reverse { primary 10.0.0.1; key DHCP_UPDATER;}
ignore client-updates;
ddns-domainname "mydomain.com";
ddns-updates on;
ddns-update-style interim;
max-lease-time 172800;
default-lease-time 864000;
# Declaration of network properties ( range ... )
#################################################
subnet 193.168.1.0 netmask 255.255.255.192 {
#options
option subnet-mask 255.255.255.192;
option domain-name "mydomain.com";
#forward and reverse lookup zones
zone mydomain.com { primary 127.0.0.1; key DHCP_UPDATER; }
zone 0.0.10.in-addr.arpa. { primary 127.0.0.1; key DHCP_UPDATER; }
one-lease-per-client on;
range 10.0.0.2 10.0.0.48;
default-lease-time 864000;
max-lease-time 2678400;
}
Yes it's working fine, but I still need it to start issuing IP's from the start of the range because i'm going to end up with a lot of zones, and will be running scripts on the zone files.
I'm running a DHCP on Suse 10.1. All is working 100%, except when it assigns IP's it assigns the last available IP in the range, instead of the first one! What am I missing?? Any help would be appreciated. Thanks
DHCPD.CONF:
option time-servers 10.0.0.1;
option domain-name "mydomain.com";
option domain-name-servers 10.0.0.1, 11.0.0.1;
option routers 10.0.0.1;
option ntp-servers 10.0.0.1;
option lpr-servers 10.0.0.1;
option netbios-name-servers 10.0.0.1;
log-facility local7;
# File with key we shall use to securely update zone files
##########################################################
include "/etc/secret.id";
# Our server is authority
#########################
server-identifier Server.mydomain.com;
authoritative ;
# Zone specification
###########################################
zone mydomain.forward { primary 10.0.0.1; key DHCP_UPDATER;}
zone mydomain.reverse { primary 10.0.0.1; key DHCP_UPDATER;}
ignore client-updates;
ddns-domainname "mydomain.com";
ddns-updates on;
ddns-update-style interim;
max-lease-time 172800;
default-lease-time 864000;
# Declaration of network properties ( range ... )
#################################################
subnet 193.168.1.0 netmask 255.255.255.192 {
#options
option subnet-mask 255.255.255.192;
option domain-name "mydomain.com";
#forward and reverse lookup zones
zone mydomain.com { primary 127.0.0.1; key DHCP_UPDATER; }
zone 0.0.10.in-addr.arpa. { primary 127.0.0.1; key DHCP_UPDATER; }
one-lease-per-client on;
range 10.0.0.2 10.0.0.48;
default-lease-time 864000;
max-lease-time 2678400;
}
try to give this entry of range in reverse range 10.0.0.2 10.0.0.48;
like range 10.0.0.48 10.0.0.2;
then i suppose u r problem would resolove , some times it try to take ips in reverse order
You could, of course, make reservations based on the mac-address for all machines. It sounds strange to do this, but the use of a DHCP server is still a good choise.
I'm not completely sure, but I think the DHCP deamon will choose IP adresses to lease based oan a round-robin algorithm, so that it will appear to be rather random, but I may be mistaken here.
I've never seen a DHCP server that will always use the first address in the pool, then the second and so on.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.