not authoritative for subnet 192.168.2.0 ??

divyashree · 07-28-2009, 12:20 PM

Why is this log

Code:

not authoritative for subnet 192.168.2.0

in /var/log/messages ,rejecting the connection ???

TB0ne · 07-28-2009, 12:32 PM

Quote:

Originally Posted by divyashree

Why is this log

Code:

not authoritative for subnet 192.168.2.0

in /var/log/messages ,rejecting the connection ???

Going to have to give some more information, before anyone can really help you. What version/distro of Linux? What are you doing when this occurs? What are the lines around this statement??

From a quick Google search, it may have something to do with DHCP, but since you don't give much information, it's hard to say. Have you Googled for it, and are you running DHCP on that box? What kind of environment is it in??

divyashree · 07-28-2009, 12:46 PM

Quote:

Originally Posted by TB0ne

Going to have to give some more information, before anyone can really help you. What version/distro of Linux? What are you doing when this occurs? What are the lines around this statement??

From a quick Google search, it may have something to do with DHCP, but since you don't give much information, it's hard to say. Have you Googled for it, and are you running DHCP on that box? What kind of environment is it in??

Sorry bro,here is all info.

I use RHEL5 server with dhcp server,sambaserver,and squid.
this is my dhcp.conf

Code:

ddns-update-style interim;
ignore client-updates;

subnet 192.168.2.0 netmask 255.255.255.0 {

# --- default gateway
        option routers                  192.168.2.254;
        option subnet-mask              255.255.254.0;

#       option nis-domain               "domain.org";

#       option domain-name              "domain.org";
#       option domain-name-servers      192.168.1.1;

        option time-offset              -18000; # Eastern Standard Time
#       option ntp-servers              192.168.1.1;
#       option netbios-name-servers     192.168.1.1;
# --- Selects point-to-point node (default is hybrid). Don't change this unless
# -- you understand Netbios very well
#       option netbios-node-type 2;

        range dynamic-bootp 192.168.2.250 192.168.2.254;
        default-lease-time 21600;
        max-lease-time 43200;

        # we want the nameserver to appear at a fixed address
        #host ns {
        #        next-server marvin.redhat.com;
        #        hardware ethernet 12:34:56:78:AB:CD;
        #        fixed-address 207.175.42.254;
        #}
}

And also setup the samba server,But unable to acces the samba share from windows.so at the accessing time from windows to my el5 log file I got that line

Code:

DHCPINFORM from 192.168.2.253 via eth0: not authoritative for subnet 192.168.2.0

divyashree · 07-29-2009, 02:17 AM

Thanks to all,I just solve the issue by putting

Code:

authoritative;

at the 1st line of dhcp.conf

abhikeny · 05-01-2015, 05:20 PM

Hi,
I understand this could be more of a question than an answer in this post, but can you explain what 'authoritative' stands for, in this config file?

Thanks in advance.

onebuck · 05-02-2015, 02:31 PM

Hi,

Please do not resurrect necro threads, this one is over 6 years old. You can do a search and find for 'dhcp.conf';

Quote:

From http://pcc-services.com/sles/dhcp_parameters.html

When fine-tuning your DHCP Server, you may have to add additional parameters to the server in order to get it to function properly, or provide the correct information to your clients. Here is a list of the parameters available and a quick description of what they do. Most of these parameters allow you to provide more information about your network to your clients, while some allow you to modify the behaviour of the DHCP Server. The Yast DHCP Server module does a very good job of showing what parameters are available to adjust depending upon what you are editing (i.e. What type of descriptor you are adjusting).

Quote:

Table from above link showes;

"allow" "Controls the response of the DHCP server to various sorts of requests. This can be used to allow certain instances, such as bootp, client updates, etc. For more information check the dhcp.conf man page."

"authoritative" "When set, tells your clients that the configuration information about the given network segment is known to be correct and is authoritative."

Hope this helps.
Have fun & enjoy!