|
|
|
|
Hi Judy, Thanks for your response. There is only one dhcp client which has unusual behavior. Rest of the clients are normally working on the same server. Any clue? Regards,
Muhammad Faisal.
From: Judy Hao <[hidden email]>
To: Muhammad Faisal <[hidden email]>; Users of ISC DHCP <[hidden email]>
Sent: Wednesday, October 28, 2015 3:41 AM
Subject: RE: Strange behavior No Gateway address after successful IP lease on ISC DHCP Server 4.1
As far as I understand, you can have only one default route and the router must be reachable on your Linux host. Check whether there is already a default route
on your DHCP client host. Also check whether you can ping the router (10.0.0.1, 10.0.0.2 in your case) on your DHCP client host.
Thanks,
Judy
From: [hidden email] [mailto:[hidden email]]
On Behalf Of Muhammad Faisal
Sent: Tuesday, October 27, 2015 11:10 AM
To: [hidden email]
Subject: Strange behavior No Gateway address after successful IP lease on ISC DHCP Server 4.1
We have configured the DHCP Server using ISC DHCP server version 4.1 on CentOS. The server deployment remain successful and most of
the host are acquiring IP address normally. On of the host is successfully acquiring IP but not the default gateway which is defined in the server as "option routers" parameter under dhcp scope.
I have tried to compare the message of working host with that of problematic one the following differences I have found:
1- Message Size parameter is sent by the problematic client which is a modem Gigaset SX686
2- All the messages are same on both problematic client and normal client
3- DHCP is successfully leasing the IP
I have tried hit and trials but no success. The server is operating with default parameters. Can someone please suggest.
one-lease-per-client true;
get-lease-hostnames false;
subnet 10.0.0.0 netmask 255.255.255.0 {
option routers 10.0.0.1, 10.0.0.2;
option subnet-mask 255.255.255.0;
option broadcast-address 10.0.0.255;
option domain-name-servers 10.0.0.3, 8.8.8.8;
option interface-mtu 1500;
range 10.0.0.4 10.0.0.254;
Regards, Muhammad Faisal.
_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users
|
|
|
I don't believe you answered Judy's question. Related to that - is there a static entry on this workstation that is conflicting with what DHCP would be returning?
You looked at the messages between the client and server. Did you confirm that the packets coming from the DHCP server have the data you expect?
Are there other Gigaset SX686 on the network? That is, when you are comparing your failing host to a working host, are you comparing it to a similar piece of hardware? I'm curious about the implication that the Message Size parameter is only being sent from
a single host - what is the DHCP server's response to that parameter, if any?
From: [hidden email] [[hidden email]] on behalf of Muhammad Faisal [[hidden email]]
Sent: Tuesday, October 27, 2015 11:50 PM
To: Judy Hao; Users of ISC DHCP
Subject: Re: Strange behavior No Gateway address after successful IP lease on ISC DHCP Server 4.1
Hi Judy,
Thanks for your response.
There is only one dhcp client which has unusual behavior. Rest of the clients are normally working on the same server. Any clue?
Regards, Muhammad Faisal.
From: Judy Hao <[hidden email]>
To: Muhammad Faisal <[hidden email]>; Users of ISC DHCP <[hidden email]>
Sent: Wednesday, October 28, 2015 3:41 AM
Subject: RE: Strange behavior No Gateway address after successful IP lease on ISC DHCP Server 4.1
As far as I understand, you can have only one default route and the router must be reachable on your Linux host. Check
whether there is already a default route on your DHCP client host. Also check whether you can ping the router (10.0.0.1, 10.0.0.2 in your case) on your DHCP client host.
Thanks,
Judy
From: [hidden email] [mailto:[hidden email]]
On Behalf Of Muhammad Faisal
Sent: Tuesday, October 27, 2015 11:10 AM
To: [hidden email]
Subject: Strange behavior No Gateway address after successful IP lease on ISC DHCP Server 4.1
We have configured the DHCP Server using ISC DHCP server version 4.1 on CentOS. The server deployment remain successful and most of the host are acquiring IP address
normally. On of the host is successfully acquiring IP but not the default gateway which is defined in the server as "option routers" parameter under dhcp scope.
I have tried to compare the message of working host with that of problematic one the following differences I have found:
1- Message Size parameter is sent by the problematic client which is a modem Gigaset SX686
2- All the messages are same on both problematic client and normal client
3- DHCP is successfully leasing the IP
I have tried hit and trials but no success. The server is operating with default parameters. Can someone please suggest.
one-lease-per-client true;
get-lease-hostnames false;
subnet 10.0.0.0 netmask 255.255.255.0 {
option routers 10.0.0.1, 10.0.0.2;
option subnet-mask 255.255.255.0;
option broadcast-address 10.0.0.255;
option domain-name-servers 10.0.0.3, 8.8.8.8;
option interface-mtu 1500;
range 10.0.0.4 10.0.0.254;
Regards, Muhammad Faisal.
_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users
|
|
|
Hi Patrick, No static entry on work station. I'm preparing to test with a different device to verify the behavior. Currently we have 2x routers defined I will check it with single router IP.
Yes verified the DHCP packets the required information is there in the dhcp options.
Yes, only Gigaset-SX686 is send message size parameter in client side signaling.
I will share the feedback one have tested as mentioned in the begining. Regards,
Muhammad Faisal.
I don't believe you answered Judy's question. Related to that - is there a static entry on this workstation that is conflicting with what DHCP would be returning?
You looked at the messages between the client and server. Did you confirm that the packets coming from the DHCP server have the data you expect?
Are there other Gigaset SX686 on the network? That is, when you are comparing your failing host to a working host, are you comparing it to a similar piece of hardware? I'm curious about the implication that the Message Size parameter is only being sent from
a single host - what is the DHCP server's response to that parameter, if any?
From: [hidden email] [[hidden email]] on behalf of Muhammad Faisal [[hidden email]]
Sent: Tuesday, October 27, 2015 11:50 PM
To: Judy Hao; Users of ISC DHCP
Subject: Re: Strange behavior No Gateway address after successful IP lease on ISC DHCP Server 4.1
Hi Judy,
Thanks for your response.
There is only one dhcp client which has unusual behavior. Rest of the clients are normally working on the same server. Any clue?
Regards, Muhammad Faisal.
From: Judy Hao <[hidden email]>
To: Muhammad Faisal <[hidden email]>; Users of ISC DHCP <[hidden email]>
Sent: Wednesday, October 28, 2015 3:41 AM
Subject: RE: Strange behavior No Gateway address after successful IP lease on ISC DHCP Server 4.1
As far as I understand, you can have only one default route and the router must be reachable on your Linux host. Check
whether there is already a default route on your DHCP client host. Also check whether you can ping the router (10.0.0.1, 10.0.0.2 in your case) on your DHCP client host.
Thanks,
Judy
From: [hidden email] [mailto:[hidden email]]
On Behalf Of Muhammad Faisal
Sent: Tuesday, October 27, 2015 11:10 AM
To: [hidden email]
Subject: Strange behavior No Gateway address after successful IP lease on ISC DHCP Server 4.1
We have configured the DHCP Server using ISC DHCP server version 4.1 on CentOS. The server deployment remain successful and most of the host are acquiring IP address
normally. On of the host is successfully acquiring IP but not the default gateway which is defined in the server as "option routers" parameter under dhcp scope.
I have tried to compare the message of working host with that of problematic one the following differences I have found:
1- Message Size parameter is sent by the problematic client which is a modem Gigaset SX686
2- All the messages are same on both problematic client and normal client
3- DHCP is successfully leasing the IP
I have tried hit and trials but no success. The server is operating with default parameters. Can someone please suggest.
one-lease-per-client true;
get-lease-hostnames false;
subnet 10.0.0.0 netmask 255.255.255.0 {
option routers 10.0.0.1, 10.0.0.2;
option subnet-mask 255.255.255.0;
option broadcast-address 10.0.0.255;
option domain-name-servers 10.0.0.3, 8.8.8.8;
option interface-mtu 1500;
range 10.0.0.4 10.0.0.254;
Regards, Muhammad Faisal.
_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users
|
|
Locked
