error in relay while using ISC DHCP code??

[Arun Prasad]

Hi ameen,

please brief me about your relay agent?? is it router (cisco) ?? or any
other make?? from the relay agent IP are you able to ping server IP address
(vice-versa)..

regards
Arun.

On Thu, Dec 15, 2011 at 6:50 PM, Arun Prasad <prasad.nagappan at gmail.com>wrote:

> hi aman,
>
> what is your relay agent ip-address.. it should be in 10.0.0.X
>
> On Thu, Dec 15, 2011 at 6:32 PM, <ameen.shajahan at wipro.com> wrote:
>
>>  Hi all ,****
>>
>>                 I am using ISC DHCP-4.2.3 code and testing the DHCPV4
>> server and relay.****
>>
>> ** **
>>
>>                 Also I am using the default conf file.****
>>
>>                 Client and server communication happened successfully by
>> sending DHCP discover , offer ,Request ,Ack messages.****
>>
>> ** **
>>
>>                 But in relay there is some problem.****
>>
>> ** **
>>
>> ** **
>>
>> *My Scenario :*
>>
>> ** **
>>
>>                 Server------------eth0--------------relay
>> ----------------------eth1-----------------------------Client****
>>
>>          192.168.0.1                            192.168.0.8
>> 10.0.0.1****
>>
>> ** **
>>
>> * *
>>
>> *In Server Side*
>>
>> * *
>>
>> # route add default gateway 192.168.0.8****
>>
>> # route -n****
>>
>> Kernel IP routing table****
>>
>> Destination     Gateway         Genmask         Flags Metric Ref    Use
>> Iface****
>>
>> 192.168.0.0     0.0.0.0         255.255.255.0   U     0      0        0
>> ixp0****
>>
>> 0.0.0.0         192.168.0.8     0.0.0.0         UG    0      0        0
>> ixp0****
>>
>> # ./dhcpd -4 -d  -f -cf /etc/dhcpd.conf -lf /var/db/dhcpd.leases ixp0****
>>
>> Internet Systems Consortium DHCP Server 4.2.3****
>>
>> Copyright 2004-2011 Internet Systems Consortium.****
>>
>> All rights reserved.****
>>
>> For info, please visit https://www.isc.org/software/dhcp/****
>>
>> Wrote 0 class decls to leases file.****
>>
>> Wrote 0 deleted host decls to leases file.****
>>
>> Wrote 0 new dynamic host decls to leases file.****
>>
>> Wrote 2 leases to leases file.****
>>
>> Listening on LPF/ixp0/00:60:43:60:ca:99/192.168.0.0/24****
>>
>> Sending on   LPF/ixp0/00:60:43:60:ca:99/192.168.0.0/24****
>>
>> Sending on   Socket/fallback/fallback-net****
>>
>> ** **
>>
>> * *
>>
>> *In Relay Side*
>>
>> ** **
>>
>> # route add default gateway 192.168.0.1****
>>
>> # route -n****
>>
>> Kernel IP routing table****
>>
>> Destination     Gateway         Genmask         Flags Metric Ref    Use
>> Iface****
>>
>> 192.168.0.0     0.0.0.0         255.255.255.0   U     0      0        0
>> ixp0****
>>
>> 10.0.0.0        0.0.0.0         255.0.0.0       U     0      0        0
>> ixp1****
>>
>> 0.0.0.0         192.168.0.1     0.0.0.0         UG    0      0        0
>> ixp0****
>>
>> # ./dhcrelay -4 -d -i ixp1 -i ixp0 192.168.0.1****
>>
>> Internet Systems Consortium DHCP Relay Agent 4.2.3****
>>
>> Copyright 2004-2011 Internet Systems Consortium.****
>>
>> All rights reserved.****
>>
>> For info, please visit https://www.isc.org/software/dhcp/****
>>
>> Listening on LPF/ixp0/00:60:43:80:41:92****
>>
>> Sending on   LPF/ixp0/00:60:43:80:41:92****
>>
>> Listening on LPF/ixp1/00:60:43:80:41:93****
>>
>> Sending on   LPF/ixp1/00:60:43:80:41:93****
>>
>> Sending on   Socket/fallback****
>>
>> Forwarded BOOTREQUEST for 00:40:05:1e:07:0f to 192.168.0.1****
>>
>> Forwarded BOOTREQUEST for 00:40:05:1e:07:0f to 192.168.0.1****
>>
>> Forwarded BOOTREQUEST for 00:40:05:1e:07:0f to 192.168.0.1****
>>
>> Forwarded BOOTREQUEST for 00:40:05:1e:07:0f to 192.168.0.1****
>>
>> Forwarded BOOTREQUEST for 00:40:05:1e:07:0f to 192.168.0.1****
>>
>> Forwarded BOOTREQUEST for 00:40:05:1e:07:0f to 192.168.0.1****
>>
>> Forwarded BOOTREQUEST for 00:40:05:1e:07:0f to 192.168.0.1****
>>
>> Forwarded BOOTREQUEST for 00:40:05:1e:07:0f to 192.168.0.1****
>>
>> Forwarded BOOTREQUEST for 00:40:05:1e:07:0f to 192.168.0.1****
>>
>> Forwarded BOOTREQUEST for 00:40:05:1e:07:0f to 192.168.0.1****
>>
>> Forwarded BOOTREQUEST for 00:40:05:1e:07:0f to 192.168.0.1****
>>
>> Forwarded BOOTREQUEST for 00:40:05:1e:07:0f to 192.168.0.1****
>>
>> ** **
>>
>> *In Client side*
>>
>> ** **
>>
>> C:\Documents and Settings\admin>ipconfig /renew****
>>
>> ** **
>>
>> Windows IP Configuration****
>>
>> * *
>>
>> *An error occurred while renewing interface Remote : unable to contact
>> your DHCP*
>>
>> *server. Request has timed out.*
>>
>> ** **
>>
>> C:\Documents and Settings\admin>****
>>
>> ** **
>>
>> I* have added  the below subnets in the  conf file. Please have a look.*
>>
>> * *
>>
>> subnet 192.168.0.0 netmask 255.255.255.0 {****
>>
>>    option subnet-mask 255.255.255.0;****
>>
>>    range dynamic-bootp 192.168.0.30 192.168.0.49;****
>>
>>    option domain-name "test.com";****
>>
>>    default-lease-time 86400;****
>>
>>    max-lease-time 86400;****
>>
>>    min-lease-time 86400;****
>>
>>   }****
>>
>>   subnet 10.0.0.0 netmask 255.255.255.0  {****
>>
>>    ****
>>
>>    option routers 10.0.0.1;****
>>
>>    option subnet-mask 255.255.255.0;****
>>
>>    range dynamic-bootp 10.0.0.30 10.0.0.49;****
>>
>>    }****
>>
>>   ****
>>
>> ** **
>>
>> ** **
>>
>> From the server side I had ping manually to eth1 side of relay. But it is
>> not pinging to eth1 side of relay.****
>>
>> ping 10.0.0.1****
>>
>> ** **
>>
>> Even though I have added the statement in the server side  route add
>> default gateway 192.168.0.8****
>>
>> ** **
>>
>> ** **
>>
>> What should I change?****
>>
>> Where would be the problem actually??****
>>
>> Please let me know.****
>>
>> Where the problem actually.****
>>
>> ** **
>>
>> ** **
>>
>> ** **
>>
>> Regards,****
>>
>> Ameen S****
>>
>> ** **
>>
>> * Please do not print this email unless it is absolutely necessary. *****
>>
>> The information contained in this electronic message and any attachments
>> to this message are intended for the exclusive use of the addressee(s) and
>> may contain proprietary, confidential or privileged information. If you are
>> not the intended recipient, you should not disseminate, distribute or copy
>> this e-mail. Please notify the sender immediately and destroy all copies of
>> this message and any attachments.
>>
>> WARNING: Computer viruses can be transmitted via email. The recipient
>> should check this email and any attachments for the presence of viruses.
>> The company accepts no liability for any damage caused by any virus
>> transmitted by this email.
>>
>> www.wipro.com
>>
>> _______________________________________________
>> dhcp-users mailing list
>> dhcp-users at lists.isc.org
>> https://lists.isc.org/mailman/listinfo/dhcp-users
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20111215/611de71d/attachment.html>