udhcpc **deleting routers**
-
Hi,
UBUNTU OS 16.04
I have Multiple VLAN setup with one centralized FOG server (IP 10.1.7.xx) & storage server at remote locations, TFTP pxe boot on central location & use inits and kernel from remote side (10.51.0.x)
This setup was working very perfectly on 1.4.0 with revision 6069.
Now I have upgraded my FOG server from 1.4.0 to 1.5.4, TFTP pxe boot from central location & inits and kernel from remote side and it is booted, when come to DHCP lease
Below is the error
udhcpc: sending discover
udhcpc: sending select for 10.51.0.x
udhcpc: lease of 10.51.0.16 obtained, lease time xxxxx
deleting routers
adding dns 10.51.0.xxx
DHCP failed… after press enter…*Attempting to check in…
*(in Line for 4.23)
*Attempting to check in…
*(in Line for 4.24)
*Attempting to check in…
*(in Line for 4.25)
*Attempting to check in…
*(in Line for 4.26)& Going on continuously
This problem occurs only if i upgraded my FOG server from 1.4.0 to 1.5.4.
Regards
L.Satheesh -
@satheesh said in udhcpc **deleting routers**:
deleting routers
That is not the issue I reckon. My guess is that the client fails to reach out to the FOG server via HTTP. Newer versions of FOG check HTTP connection after they got an IP via DHCP (which seems fine from what you posted). Possibly your have some kind of network filter between your VLANs that don’t allow TCP port 80 (HTTP) from the clients to your FOG server?!
-
I am not understand…
in same VLAN already configured windows system getting IP from DHCP
IP 10.51.0.16
Gw 10.51.0.10
DNS 10.51.0.200 10.51.0.201From this system I able to open the FOG server on http protocol
http://10.1.7.xx/fog – that means port 80 is open and client able to access the server from this VLAN.why **udhcpc :- deleting routers ** here during PXE boot operation
Regards
L.Satheesh -
@satheesh there is no problem with ‘deleting routers’ as Sebastian said. Your problem is with FOS checking in to the fog server. When you are seeing the messages ‘attempting to check in…’ look at the apache access log on the fog server to see if it’s even getting the request. You can do a
tail -f /var/log/apache2/access.logyou should see entries as the FOS client tries to check in. If you don’t, it means the FOG server is not getting the requests. If you do, it means FOG server is replying but FOS is not getting the reply. -
@satheesh said in udhcpc **deleting routers**:
DHCP failed… after press enter…
@developers does that look ok?
-
@wayne-workman said in udhcpc **deleting routers**:
DHCP failed… after press enter…
I am fairly sure this is not the exact message. @Satheesh Please take a picture of the error on screen and upload here so we see what exactly you see on screen.
