TFTP ARP Timeout
-
@cammykool Ok, this all looks fine. Can you provide output of
ip a scommand as well? -
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 -
its set to static info
IP 10.1.80.1
DHCP: 10.1.0.1
DNS: 10.1.0.2, 10.1.0.3 -
@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.1Really 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
updateIPscript as well? -
no i did not
i will -
@cammykool Fix the subnet mask on your FOG server first!
-
@cammykool Sorry but I need to head off now. Time to catch some sleep…
-
-
@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)
-
Also lets confirm what you have exactly configured in your dhcp server. What do you have defined for dhcp option 66 and 67 respectively?
-
i noticed in fogsettings it is set to 255.255.0.0. i changed it there.
-
@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 showand confirm that the subnet mask matches the rest of your network. If it doesn’t reboot the fog server and then confirm. -
thats the winserver config.
-
@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 -
@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 enp0s25thensudo ifup enp0s25to avoid the reboot time. -
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.
-
@george1421 it looked to be /8 too before
pxe is still getting 255.255.0.0 at boot
-
@cammykool So you updated the network manager application and then either did the ifup/ifdown or reboot and its still set to /8?
The pxe stuff is coming from your dhcp server not the fog server. Your client is still having a problem finding the fog server from your first picture.
-
yes it is. Netowkr manager has always been correct.
-
im working on the guide i was sent initially. boss gave me direct access to the DHCP server
