TFTP ARP Timeout

Sebastian Roth

we have a winserver box running DHCP

Please post the settings here and we surely can help you fix this.

As well you might want to check this out: https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence#Using_Windows_Server_2012_.28R1_and_later.29_DHCP_Policy

If you have the DHCP pointing to the correct IP (TFTP should be running on your FOG server!), then we need to have a closer look at this one.

What’s the FOG server IP?
What Linux OS is installed?
Is TFTP running? netstat -antup | grep "69"
Firewall disabled? iptables -L -n -v
SELinux disabled? getenforce

Please post the output of all those commands.

cammykool

DHCP server configuration or fog config? Dont have direct access to DHCP boss does. Just ent him that link and he is working on it now

Sebastian Roth

@cammykool I just updated my below post…

cammykool

@Sebastian-Roth said in TFTP ARP Timeout:

netstat -antup | grep “69”

"netstat -antup | grep “69"”

udp        0      0 0.0.0.0:69              0.0.0.0:*                           1557/in.tftpd
udp        0      0 0.0.0.0:57458           0.0.0.0:*                           690/avahi-daemon: r
udp        0      0 0.0.0.0:45269           0.0.0.0:*                           817/rpc.mountd
udp        0      0 0.0.0.0:5353            0.0.0.0:*                           690/avahi-daemon: r
udp6       0      0 :::69                   :::*                                1557/in.tftpd
udp6       0      0 :::60737                :::*                                690/avahi-daemon: r
udp6       0      0 :::5353                 :::*                                690/avahi-daemon: r

iptables

Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination

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

selinux

user@fog:~$ getenforce
Disabled

Sebastian Roth

@cammykool Ok, this all looks fine. Can you provide output of ip a s command as well?

cammykool

@Sebastian-Roth

user@fog:~$ ip a s
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: enp0s25: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 18:03:73:cf:ab:5a brd ff:ff:ff:ff:ff:ff
    inet 10.1.80.1/8 brd 10.255.255.255 scope global noprefixroute enp0s25
       valid_lft forever preferred_lft forever
    inet6 fe80::7298:8d49:d303:484d/64 scope link noprefixroute
       valid_lft forever preferred_lft forever

cammykool

its set to static info

IP 10.1.80.1
DHCP: 10.1.0.1
DNS: 10.1.0.2, 10.1.0.3

Sebastian Roth

@cammykool said in TFTP ARP Timeout:

inet 10.1.80.1/8 brd 10.255.255.255

What I do notice here is that this broadcast address seems to not match the netmask we see in the picture you posted earlier. Either it’s /16 (255.255.0.0) or /8 (255.0.0.0). While this shouldn’t cause the ARP timeout I am still wondering why you have this mixed up here.

its set to static info

IP 10.1.80.1
DHCP: 10.1.0.1

Really static or maybe DHCP?? FOG server should always be configured to have a static IP!!

Did you re-run the installer after you ran the updateIP script as well?

cammykool

no i did not
i will

Sebastian Roth

@cammykool Fix the subnet mask on your FOG server first!

Sebastian Roth

@cammykool Sorry but I need to head off now. Time to catch some sleep…

cammykool

@Sebastian-Roth

67 is set to 10.1.80.1 in DHCP and ubuntu has it set up manually for the same

george1421

@cammykool OK wait a minute. Why does the first picture have a subnet mask of 255.255.0.0 (/16) and the ubuntu server have 255.0.0.0 (/8)

george1421

Also lets confirm what you have exactly configured in your dhcp server. What do you have defined for dhcp option 66 and 67 respectively?

cammykool

@george1421

i noticed in fogsettings it is set to 255.255.0.0. i changed it there.

george1421

@cammykool You also need to change it in the network manager since you are using ubuntu.

Then from the fog server command prompt key in ip addr show and confirm that the subnet mask matches the rest of your network. If it doesn’t reboot the fog server and then confirm.

cammykool

@george1421

thats the winserver config.

cammykool

@george1421 ip addr show is still showing 255.255.255 even after changing in network manager

user@fog:~$ ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: enp0s25: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 18:03:73:cf:ab:5a brd ff:ff:ff:ff:ff:ff
    inet 10.1.80.1/8 brd 10.255.255.255 scope global noprefixroute enp0s25
       valid_lft forever preferred_lft forever
    inet6 fe80::7298:8d49:d303:484d/64 scope link noprefixroute
       valid_lft forever preferred_lft forever

george1421

@cammykool Actually if you look after the IP address is /8 or 255.0.0.0. Then reboot the fog server since it may only load at boot time.

edit, maybe you could do sudo ifdown enp0s25 then sudo ifup enp0s25 to avoid the reboot time.

george1421

Understand that fixing the subnet mask may not address the pxe booting problem, but it will fix ARP resolution. The subnet mask controls where the broadcast address is. Two different subnet masks have their broadcast address in different locations so the two clients will have difficulty finding each other.

TFTP ARP Timeout

222

12.0k

17.3k

155.2k