HELP Problem DHCP - Ubuntu 18.04

[george1421]

@ultralivre I think maybe you missed step #2 in the tutorial. I did not give the exact command to install dnsmasq because each distro is a little different. You need to run this command to install dnsmasq in ubuntu apt install dnsmasq

Then run the command dnsmasq -V to get the version of dnsmasq. It must be 2.75 or later

[ultralivre]

@george1421

Desculpe, eu havia rodando o comando “sudo dnsmasq -v” e havia obtido resposta, me equivoquei quanto a instalação.

Agora deu certo.

Vou testar aqui !

[george1421]

@ultralivre ok no problem I make a mistake not -V but -v. What version number did it the command make?

[ultralivre]

@george1421

gnuuser@gnuuser:~$ sudo dnsmasq -v
Dnsmasq version 2.79  Copyright (c) 2000-2018 Simon Kelley
Compile time options: IPv6 GNU-getopt DBus i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth nettlehash DNSSEC loop-detect inotify

This software comes with ABSOLUTELY NO WARRANTY.
Dnsmasq is free software, and you are welcome to redistribute it
under the terms of the GNU General Public License, version 2 or 3.
gnuuser@gnuuser:~$

Fiz toda configuração do dnsmasq conforme o seu artigo, reiniciei meu server FOG tudo certo ! vou aguardar mais alguns testes, a principio tudo funcionando

Você poderia explicar um pouco mais detalhado o que faz o dnsmasq nesse caso ?

Obrigado !

[george1421]

@ultralivre How it works, easy and hard to explain.

DNSMASQ in this configuration is setup to function as proxydhcp configuration. It will not give out IP address only pxe booting information. If you put a computer with wireshark on same subnet as fog server (to watch the communications). Set the capture filter to port 67 or port 68 or port 4011 You will see what is called the DORA process for dhcp (DISCOVER, OFFER, REQUEST, ACK == DORA)

PXE booting computer sends out DISCOVER packet. Every DHCP server that hears the DISCOVER will then send an OFFER. Wireshark will show two offers with dnsmasq is running. One will be from your main dhcp server and second from dnsmasq with dhcp option 60 set. This is a flag for a proxydhcp OFFER. PXE client knows to ask for IP address from real dhcp server then asks proxydhcp (dnsmasq) for pxe boot info after the ACK packet.

OK your version of dnsmasq is good. The configuration will support both bios and uefi computers pxe booting.

[ultralivre]

@george1421

Boa noite !!

Servidor FOG a todo vapor por aqui
Uma duvida, Criando uma Vlan roteavel isolada somente para o FOG o servidor PXE irá funcionar?

A duvida é por que vao estar em dominios de broadcast diferentes !

[george1421]

@ultralivre I’m not sure I understand 100% of what you said. I can tell you that FOG will image correctly on a fully routable network with vlans. For DNSMASQ to work across VLANs, you need to update your subnet router and put the FOG’s IP address as the last server in the dhcp-helper/dhcp-relay service on your router. Then you can image across the subnets.

Now there are reasons to turn this option on and reasons to keep fog imaging isolated. You make the settings that work best for your company.

[ultralivre]

@george1421 Boa noite !
A aplicação FOG funciona na rede através do protocolo DHCP?
cliente vs servidor trocam informações primeiramente com DHCP?

Estou tentando procurar a documentação para descobrir como o FOG funciona.

Obrigado.

[george1421]

@ultralivre FOG doesn’t use or interact with dhcp directly. The PXE booting client computer uses dhcp to get its IP address and the hint how to find the FOG server. This is via dhcp options 66 and 67. The client computer then connects to the fog server using the tftp protocol to download the network boot loader (iPXE). That is where the FOG server firsts connects to the workflow.

[ultralivre]

@george1421

Boa tarde,

Trocando de assunto !

É possível movimentar imagens criadas em diferentes servidores FOG ?

[george1421]

@ultralivre Yes its possible.

There are two parts

1. Raw data stored in /images/<image_name> directory
2. Meta data that is stored in the database. You can export this info using the web ui

Move the /images files to your new server
Export the metadata from old server then import into new server all using the web ui.

[ultralivre]

@george1421

Você consegue mostrar o que são estes metadados?

[george1421]

@ultralivre said in HELP Problem DHCP - Ubuntu 18.04:

Você consegue mostrar o que são estes metadados?

Anything stored in the FOG database. From the web ui you can export and import this metadata.

[ultralivre]

@george1421
Boa noite !

Recentemente recebi uma quantidade grande de equipamentos da Dell optplex 5000 e ao tentar utilizar o servidor FOG recebi a seguinte mensagem:

[george1421]

@ultralivre If you make a new FOG server then be sure to update the FOS Linux kernel to 5.15.x version. FOG Web UI -> FOG Configuration -> Kernel update.

[ultralivre]

@george1421
Bom dia,
Executei a atualização do kernel, porém fiquei na duvida se: a atualização precisar aparecer no fog?

Como pode ver eu atualizei mas continua aparecendo a versão 4.19.145

Esta certo?

[george1421]

@ultralivre Yes you are still running on the old FOS linux kernel and that is causing the error message you see.

When you select the buttons for 5.15.71 (or whatever version) it should download and install in FOG.

If the auto update is not working for you, then you can get the kernels from here: https://github.com/FOGProject/fos/releases

They need to be renamed as bzImage and bzImage32 and placed in the following directory on the fog server. /var/www/html/fog/service/ipxe directory. You can also run this command to verify the version of the kernel from the FOG server’s linux command prompt file bzImage it will print the kernel version.

[ultralivre]

@george1421

Bom dia,

Perfeito

Vou aproveitar o contato e perguntar:

Tenho muitos computadores e pouca memória ram no meu servidor fog, porém gostaria de colocar todos ao mesmo tempo mas que o servidor fog fosse administrando a clonagem, de 5 em 5 ou de 4 em 4, para não sobrecarregar o meu servidor físico. É possível ?

Obrigado

[george1421]

@ultralivre I’ve never really looked at ram usage during a single unicast deployment to know how many you can send at one time for a limit.

I have done testing with how many unicast images can I send at one time without impacting performance of the 1GbE network connection. The answer is 3. Above 3 you can saturate a 1GbE network connection.

How much ram do you have in your fog server?

There is another method to deploy many computers at one time with FOG its called multicast imaging. This method configures the target computer with a receiver program and then FOG server sends out a single image to all computers running the receiver program. This method you can image 25 computers using no more fog server resources than a single unicast image. The multicast deployments require more configuration on the network side and all target computers must be on the same IP subnet as the FOG server.

[ultralivre]

@george1421
Muito bem, você consegue me dar um exemplo de como utilizar o cliente multicast ?