No more network device - failed

[Tom Elliott]

@palermo am I too understand your modem is what’s providing networking for your systems? Maybe this is where the breakdown is occurring? Most modems don’t have the granularity as a consumer router would have for fogs needs.

[Tom Elliott]

I should also note that the modem typically has its own definition of tftp settings as this is how the modem is configured by the isp. Maybe this is the reason for the message you’re seeing.

[palermo]

@tom-elliott said in No more network device - failed:

@palermo am I too understand your modem is what’s providing networking for your systems? Maybe this is where the breakdown is occurring? Most modems don’t have the granularity as a consumer router would have for fogs needs.

thanks for the answer
exactly what do I do?

Which command do I write to the server?

[Tom Elliott]

@palermo I’d recimmend using the modem in a “bridged” mode. Basically a consumer router that connects to the modem, then your hosts connect to the router. At least we would remove the modems own tftp settings from the picture and we would be better able to assist. At a minimum, if this is at home, look up dd-wrt for supported routers. (Netgear is what I’d suggest for consumer router.) if this is enterprise a managed switch might suffice and you could route through your own dhcp server, which we can definitely help with. In the meantime, I’d highly suggest looking into proxydhcp setup on your fog server.

[palermo]

@tom-elliott

How can I install proxydhcp?

I installed it like this video
https://www.youtube.com/watch?v=jXLcORPm5YY

I have a problem

[Sebastian Roth]

@palermo Yeah from the picture of the modem configuration you posted it looks like you cannot add PXE settings to the DHCP configuration there. So as Tom said you might look into proxydhcp. Find stuff on that in our wiki: https://wiki.fogproject.org/wiki/index.php?title=ProxyDHCP_with_dnsmasq

But be warned: Some modems still send half of the PXE information and really do confuse the clients with that. So give it a try but don’t blame us if it’s not working out of the box.

[palermo]

@sebastian-roth

i installed fog server v0.32 before
he worked

the new version is not working

[palermo]

I reinstalled

• Detected Linux Distribution: Ubuntu
• Server IP Address: 192.168.2.25
• Server Subnet Mask: 255.255.255.0
• Interface: ens32
• Installation Type: Normal Server
• Internationalization: 0
• Image Storage Location: /images
• Using FOG DHCP: Yes
• DHCP router Address: 192.168.2.25

I got this error.

[Sebastian Roth]

@palermo Ok, so this time you decided to let FOG be the DHCP server which should be fine. But this time the client does get an answer pointing to 192.168.2.1 as being the next server why FOG is on 192.168.2.25… So I am wondering if there is another DHCP server again. As you seem to use virtual box (sorry I didn’t talk about this earlier) I am wondering how your virtual network setup in virtualbox looks like. Is it set to bridged, NAT, host-only?

i installed fog server v0.32 before
he worked

FOG is a set of tools put together as imaging solution. So it’s kind of a complex setup and it does sometimes work out of the box but you can’t ask for this being the case all the time. Especially using a virtual environment there are too many variables in the equation so it’s very likely to go wrong especially if you don’t have much experience with DHCP, PXE and such things.

[palermo]

@sebastian-roth

bridge network
ping and internet active

[Sebastian Roth]

@palermo Please post the contents of your /etc/dhcp/dhcpd.conf file.

[palermo]

@sebastian-roth

thank you
dnsmasg install
I solved the problem