Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have an embedded board that has the CFE, a minimal loader. I have a host machine - linux FC16, where I am running a dhcpd server. My interface is p3p1. Here are the details of the ifcfg-p3p1.


Now, I have the following dhcpd.conf file -

default-lease-time 600;
max-lease-time 7200;
option subnet-mask;

ddns-update-style interim;
allow booting; 
allow bootp;
ignore client-updates;
set vendorclass = option vendor-class-identifier;

subnet netmask {
    option routers;
    option subnet-mask;
    default-lease-time  21600;
    max-lease-time  43200;

The client is not getting the IP address, thus I am first trying to troubleshoot the issue of the connectivity.

I assigned an IP address to my client -


Now, when I try to ping my host from the client, I see the following.

At client side -

CFE> ping ( is not responding (seq=0) ( 1 packets sent, 0 received
*** command status = 1

At host side -

# tcpdump -e -i p3p1 -vvv 
tcpdump: listening on p3p1, link-type EN10MB (Ethernet), capture size 65535 bytes
16:20:23.885757 e0:b7:b1:23:60:d0 (oui Unknown) > 14:d6:4d:1f:f3:f8 (oui Unknown), ethertype IPv4 (0x0800), length 98: (tos 0x0, ttl 100, id 33, offset 0, flags [none], proto ICMP (1), length 84) > ICMP echo request, id 988, seq 0, length 64

I see that the mac address is correct here. The client MAC address is e0:b7:b1:23:60:d0 The host mac address is the following 14:d6:4d:1f:f3:f8.

What could be the issue here? Please give me some pointers here as I am new to networking.

# ifconfig
em1       Link encap:Ethernet  HWaddr B8:CA:3A:89:EE:F1  
          inet addr:  Bcast:  Mask:
          inet6 addr: fe80::baca:3aff:fe89:eef1/64 Scope:Link
          RX packets:4362507 errors:0 dropped:2 overruns:0 frame:0
          TX packets:1467982 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:5484308631 (5.1 GiB)  TX bytes:115472934 (110.1 MiB)
          Interrupt:20 Memory:f7e00000-f7e20000 

lo        Link encap:Local Loopback  
          inet addr:  Mask:
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:32118 errors:0 dropped:0 overruns:0 frame:0
          TX packets:32118 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:6121874 (5.8 MiB)  TX bytes:6121874 (5.8 MiB)

p3p1      Link encap:Ethernet  HWaddr 14:D6:4D:1F:F3:F8  
          inet addr:  Bcast:  Mask:
          inet6 addr: fe80::16d6:4dff:fe1f:f3f8/64 Scope:Link
          RX packets:209 errors:0 dropped:0 overruns:0 frame:0
          TX packets:411 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:49526 (48.3 KiB)  TX bytes:60967 (59.5 KiB)

I am running dhcpd on the interface p3p1 only.

share|improve this question
On the issue of the ping: Are ping replies allowed on iptables? Can you manually ping back from the DHCP server host to the client? On the issue of the DHCP: Does the next-server parameter need to be specified? Why is it pointing to your gateway? Is there any file clients need to load from there? – kenkh Mar 18 '14 at 12:18
probably not the problem but, your embedded board static ip is in the dhcp range. – chaput Mar 18 '14 at 12:22
@chaput - yes, the static ip is in the dhcp range. But, does it matter? I thought ideally, it should be in the range only right? – dexterous_stranger Mar 18 '14 at 15:28
@kenkh - What do you mean by iptables here? No, I cannot ping the client from the host. It is not working. The client can speak to server, but server cannot speak to client. I don't about next-server, it is copied and pasted from the tutorials. Ok, I have added a route, whenever I get messages from the ip address ranges - 10.240.100.x , it will be diverted to the ip address - I have done this, since I have two NIC's. One NIC is connected to my office network, and the other one is which I am trying to connect to embedded box. – dexterous_stranger Mar 18 '14 at 15:32
@SHREYAS JOSHI - the problem with that is that you'll end up with a duplicate IP or the client will generate an error when he'll try te reply to the dhcp who have exactly the same IP address. – chaput Mar 18 '14 at 15:36

You must log in to answer this question.

Browse other questions tagged .