PXE-E32: TFTP open timeout

[Mahmood N]

Hello,
Here are some more information and I will appreciate any help despite that the problem is not directly related to dhcp. The server has two interfaces. eth0 is used for internet and eth1 is used for the tftp services.

On four separated terminals, I have run the following commands in the debug mode and they should log any new transaction

    dhcp -d
    xinetd -d
    in.tftpd --verbose

    tcpdump -vv -i eth1


>First check if xinetd is actually listening for the request:
Yes it is listening
    # netstat -nlp | fgrep ":69 "
    udp        0      0 0.0.0.0:69         0.0.0.0:*          2295/xinetd         



> First see if the netfilter modules are loaded:
I have one line less than yours, the x_tables
    # lsmod | fgrep table
    iptable_filter          2793  1 
    ip_tables              17831  1 iptable_filter
    ip6table_filter         2889  1 
    ip6_tables             19458  1 ip6table_filter



>If they are NOT loaded (i.e. empty output) then running the following
>commands will actually load the modules.
Sorry which command?

 


>Look for things that might deny your request, or maybe look for the 
>specific opening that needs to be there.

    # iptables -t filter -L -v -n
    Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
     pkts bytes target     prot opt in     out     source               destination         
     5540 7783K ACCEPT     all  --  *      *       0.0.0.0/0            0.0.0.0/0           state RELATED,ESTABLISHED 
        0     0 ACCEPT     icmp --  *      *       0.0.0.0/0            0.0.0.0/0           
        2   120 ACCEPT     all  --  lo     *       0.0.0.0/0            0.0.0.0/0           
        0     0 ACCEPT     tcp  --  *      *       0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:22 
       24  6006 REJECT     all  --  *      *       0.0.0.0/0            0.0.0.0/0           reject-with icmp-host-prohibited 

    Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
     pkts bytes target     prot opt in     out     source               destination         
        0     0 REJECT     all  --  *      *       0.0.0.0/0            0.0.0.0/0           reject-with icmp-host-prohibited 

    Chain OUTPUT (policy ACCEPT 3363 packets, 143K bytes)
     pkts bytes target     prot opt in     out     source               destination         



I also made full permission to the ftfp folder 
    # ls -laR /var/lib/tftpboot/
    /var/lib/tftpboot/:
    total 23664
    drwxrwxrwx.  3 root root     4096 Aug  2 18:34 .
    drwxr-xr-x. 37 root root     4096 Aug  2 16:34 ..
    -rwxrwxrwx.  1 root root 20139567 Aug  2 18:34 initrd.img
    -rwxrwxrwx.  1 root root    60928 Aug  2 16:44 menu.c32
    -rwxrwxrwx.  1 root root    26828 Aug  2 16:43 pxelinux.0
    drwxrwxrwx.  2 root root     4096 Aug  2 19:32 pxelinux.cfg
    -rwxrwxrwx.  1 root root  3987376 Aug  2 18:34 vmlinuz
   
    /var/lib/tftpboot/pxelinux.cfg:
    total 12
    drwxrwxrwx. 2 root root 4096 Aug  2 19:32 .
    drwxrwxrwx. 3 root root 4096 Aug  2 18:34 ..
    -rwxrwxrwx. 1 root root  151 Aug  2 19:32 default




Now I start the client. It ends up with "PXE-E11: ARP timeout". I don't know what happened that I receives this error message again!
Looking in to the debugged messages:
- xinetd and in.tftpd receive no message (!) I mean the last message before starting the client is still the last message.
- dhcpd shows "DHCPACK on 10.0.2.5 to 08:00:27:69:73:7a via eth1"
- tcpdump shows this message
        10.0.2.1.bootps > 255.255.255.255.bootpc: [udp sum ok] BOOTP/DHCP, Reply, length 300, xid 0x2869737a, secs 4, Flags [Broadcast] (0x8000)
          Your-IP 10.0.2.5
          Server-IP 10.0.2.1
          Client-Ethernet-Address 08:00:27:69:73:7a (oui Unknown)
          file "pxelinux.0"
          Vendor-rfc1048 Extensions
            Magic Cookie 0x63825363
            DHCP-Message Option 53, length 1: ACK
            Server-ID Option 54, length 4: 10.0.2.1
            Lease-Time Option 51, length 4: 43200
            Subnet-Mask Option 1, length 4: 255.255.255.240
            RN Option 58, length 4: 21600
            RB Option 59, length 4: 37800
 
and multiple lines containing "ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.0.2.1 tell 10.0.2.5, length 46"




Conclusion:
While I wrote "next-server 10.0.2.1", which is ip address of eth1, in the dhcpd.conf, I don't know why it doesn't reply back to the client. The client asks multiple times who has 10.0.2.1 and the server doesn't reply although it granted 10.0.2.5 to the client.





Regards,
Mahmood 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20140806/ebf3f54e/attachment-0001.html>