Autor Tópico: Ubuntu server não sobe DHCP (Lida 18809 vezes)

jonatanrader · « **Online:** 29 de Setembro de 2016, 15:33 »

Pessoal, mudei o firewall da rede para o Ubuntu, ele conecta e acessa a rede Windows, mas o problema vem agora ao compartilhar a rede e internet com os clientes, ele não sobe as informações, as mauinas clientes não conseguem pegar os IPs do DHCP, e muito menos identificam a rede. Fiz uma configuração básica para ver se iria subir a rede e nada, postarei as configs do server.

INTEFACES
auto lo
iface lo inet loopback

#REDE EXTERNA - NET
auto enp2s0
iface enp2s0 inet static

address 192.168.1.50
netmask 255.255.255.0
broadcast 192.168.1.255
network 192.168.1.0
gateway 192.168.1.3

#REDE LOCAL

auto enp3s0
iface enp3s0 inet dhcp (JÁ UTILIZEI IP FIXO E NÃO RESOLVEU)

DHCP.CONF

#atualização do DNS: nenhuma
   ddns-update-style none;
   log-facility local7;

   default-lease-time 800;
   max-lease-time 1200;
   authoritative;
   option domain-name-servers 8.8.4.4,8.8.8.8;
   #option subnet-mask 255.255.255.0;

#escopo DHCP

   subnet 192.168.0.0 netmask 255.255.255.0 {
      range 192.168.0.15 192.168.0.254;
      option broadcast-address 192.168.1.255;
      option routers 192.168.0.1;

      default-lease-time 800;
      max-lease-time 1200;
}

RC.LOCAL
modprobe iptable_nat
echo 1 > /proc/sys/net/ipv4/ip_forward
iptables -t nat -A POSTROUTING -o enp2s0 -j MASQUERADE

iptables -A INPUT -p icmp --icmp-type echo-request -j DROP
echo 1 > /proc/sys/net/ipv4/conf/default/rp_filter
iptables -A INPUT -m state --state INVALID -j DROP
iptables -A INPUT -i lo -j ACCEPT
iptables -A INPUT -i enp3s0 -j ACCEPT
iptables -A INPUT -p tcp --dport 22 -j ACCEPT
iptables -A INPUT -p tcp --syn -j DROP

IFCONFIG
enp2s0 Link encap:Ethernet Endereço de HW 50:e5:49:XXXXX
inet end.: 192.168.1.50 Bcast:192.168.1.255 Masc:255.255.255.0
endereço inet6: fe80::52e5:49ff:fef6:9445/64 Escopo:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Métrica:1
pacotes RX:137954 erros:0 descartados:8633 excesso:0 quadro:0
Pacotes TX:26241 erros:0 descartados:0 excesso:0 portadora:1
colisões:0 txqueuelen:1000
RX bytes:29648128 (29.6 MB) TX bytes:3436717 (3.4 MB)

enp3s0 Link encap:Ethernet Endereço de HW 1c:7e:e5XXXX
endereço inet6: fe80::1e7e:e5ff:fe2d:262a/64 Escopo:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Métrica:1
pacotes RX:933 erros:0 descartados:0 excesso:0 quadro:0
Pacotes TX:379 erros:0 descartados:0 excesso:0 portadora:0
colisões:0 txqueuelen:1000
RX bytes:129896 (129.8 KB) TX bytes:97582 (97.5 KB)

lo Link encap:Loopback Local
inet end.: 127.0.0.1 Masc:255.0.0.0
endereço inet6: ::1/128 Escopo:Máquina
UP LOOPBACK RUNNING MTU:65536 Métrica:1
pacotes RX:23 erros:0 descartados:0 excesso:0 quadro:0
Pacotes TX:23 erros:0 descartados:0 excesso:0 portadora:0
colisões:0 txqueuelen:1
RX bytes:1215 (1.2 KB) TX bytes:1215 (1.2 KB)

zekkerj · « **Resposta #1 Online:** 29 de Setembro de 2016, 16:15 »

Olá jonatanrader, vi alguns erros na sua configuração.

1. Se sua conexão internet é NetVirtua, sua placa de rede externa tem que ser configurada como DHCP, não ip fixo. Se bem que pelo IP que vc usou, vc está se conectando a um roteador, o que pode mudar muito o funcionamento da coisa.

2. Se vc tem um servidor, a placa de rede interna tem que ter, obrigatoriamente, IP fixo, em um faixa diferente da usada na rede externa. Isso inclusive é determinante para o funcionamento do serviço DHCP. Uma boa dica é que seu servidor provavelmente será o gateway da rede interna, então a placa de rede interna deve receber o endereço do gateway da rede interna (192.168.0.1/24).

3. Não mexa no "rc.local". Coloque seus comandos de firewall em um script próprio.

4. Nunca se desabilita PING em um servidor em teste. E não é recomendável desabilitar ping pra rede interna.

5. Há um arquivo de configuração adicional, que é o /etc/default/dhcp, onde vc precisa especificar em quais placas de rede o servidor DHCP vai trabalhar. Sem essa configuração, o serviço não sobe nem com reza braba.

jonatanrader · « **Resposta #2 Online:** 30 de Setembro de 2016, 10:49 »

Olá zekkerj, atualmente me conecto pelo roteador sim, por conta disto fixei o ip da placa da rede externa. E a rede interna esta com ip diferente dda rede externa, e pretendo sim utilizar ele como Gateway da rede, quanto as regras do firewall eu deixei mesmo no rc.local por conta de ser um teste ainda, meu problema é subir a rede e o dhcp enviar os ips para as maquinas windows, eu estava utilizando o centOS e estava rodando beleza....mas deu pau na maquina e resolvi mudar...... e sim eu setei a enp3s0 (rede interna) para trabalhar com o dhcp.

Fiz as mudanças que vc citou, mas ainda não subiu a rede para os clientes. O que poderia esta ocorrendo minhas confis das placas estão iguais. Não mudou após subir o serviço novamente.

zekkerj · « **Resposta #3 Online:** 30 de Setembro de 2016, 12:18 »

Citar

e sim eu setei a enp3s0 (rede interna) para trabalhar com o dhcp.

Tem que ser fixo.

Citar

eu deixei mesmo no rc.local por conta de ser um teste ainda

Você está fazendo testes num arquivo que tem potencial de estragar sua máquina. Mova seus comandos pra um script separado. Deixe o carregamento manual, mesmo. Depois que estiver funcionando, vc vê uma forma de automatizar a carga.

Citar

Fiz as mudanças que vc citou, mas ainda não subiu a rede para os clientes. O que poderia esta ocorrendo minhas confis das placas estão iguais. Não mudou após subir o serviço novamente.

Colocou o nome da interface interna (enp3s0) no arquivo /etc/default/dhcp?
Colocou um IP fixo na faixa 192.168.0.0/24 nessa interface?
Parou de bloquear ping na rede interna?

Se já fez isso, então execute os comandos abaixo e cole o resultado aqui pra gente analisar porque seu serviço não sobe.

sudo service dhcpd start
grep dhcpd /var/log/messages | tail -20

jonatanrader · « **Resposta #4 Online:** 30 de Setembro de 2016, 17:25 »

Citar

Colocou o nome da interface interna (enp3s0) no arquivo /etc/default/dhcp?
Colocou um IP fixo na faixa 192.168.0.0/24 nessa interface?
Parou de bloquear ping na rede interna?

Sim para todas as perguntas acima. Os comandos que vc passou não roda no Ubuntu Server.

ps wax | grep dhcp
20286 pts/17 S+ 0:00 grep --color=auto dhcpd

Syslog
Sep 29 07:36:38 FIREWALL anacron[21049]: Job `cron.daily' terminated
Sep 29 07:36:38 FIREWALL anacron[21049]: Normal exit (1 job run)
Sep 29 07:40:44 FIREWALL dhclient[7816]: DHCPREQUEST of 192.168.0.16 on enp3s0 to 192.168.0.14 port 67 (xid=0x1955e26)
Sep 29 07:41:57 FIREWALL dhclient[7816]: message repeated 9 times: [ DHCPREQUEST of 192.168.0.16 on enp3s0 to 192.168.0.14 port 67 (xid=0x1955e26)]
Sep 29 07:42:05 FIREWALL systemd[1]: Started CUPS Scheduler.
Sep 29 07:42:07 FIREWALL dhclient[7816]: DHCPREQUEST of 192.168.0.16 on enp3s0 to 192.168.0.14 port 67 (xid=0x1955e26)
Sep 29 07:45:26 FIREWALL dhclient[7816]: message repeated 15 times: [ DHCPREQUEST of 192.168.0.16 on enp3s0 to 192.168.0.14 port 67 (xid=0x1955e26)]
Sep 29 07:45:38 FIREWALL dhclient[7816]: DHCPREQUEST of 192.168.0.16 on enp3s0 to 255.255.255.255 port 67 (xid=0x1955e26)
Sep 29 07:45:38 FIREWALL dhcpd[7479]: DHCPREQUEST for 192.168.0.16 from 1c:7e:e5:2d:26:2a via enp3s0
Sep 29 07:45:38 FIREWALL dhcpd[7479]: DHCPACK on 192.168.0.16 to 1c:7e:e5:2d:26:2a (FIREWALL) via enp3s0
Sep 29 07:45:50 FIREWALL dhclient[7816]: DHCPREQUEST of 192.168.0.16 on enp3s0 to 255.255.255.255 port 67 (xid=0x1955e26)
Sep 29 07:45:50 FIREWALL dhcpd[7479]: reuse_lease: lease age 12 (secs) under 25% threshold, reply with unaltered, existing lease
Sep 29 07:45:50 FIREWALL dhcpd[7479]: DHCPREQUEST for 192.168.0.16 from 1c:7e:e5:2d:26:2a (FIREWALL) via enp3s0
Sep 29 07:45:50 FIREWALL dhcpd[7479]: DHCPACK on 192.168.0.16 to 1c:7e:e5:2d:26:2a via enp3s0
Sep 29 07:45:58 FIREWALL dhclient[7816]: DHCPREQUEST of 192.168.0.16 on enp3s0 to 255.255.255.255 port 67 (xid=0x1955e26)
Sep 29 07:45:58 FIREWALL dhcpd[7479]: reuse_lease: lease age 20 (secs) under 25% threshold, reply with unaltered, existing lease
Sep 29 07:45:58 FIREWALL dhcpd[7479]: DHCPREQUEST for 192.168.0.16 from 1c:7e:e5:2d:26:2a via enp3s0
Sep 29 07:45:58 FIREWALL dhcpd[7479]: DHCPACK on 192.168.0.16 to 1c:7e:e5:2d:26:2a via enp3s0
Sep 29 07:46:08 FIREWALL dhclient[7816]: DHCPREQUEST of 192.168.0.16 on enp3s0 to 255.255.255.255 port 67 (xid=0x1955e26)
Sep 29 07:46:08 FIREWALL dhcpd[7479]: reuse_lease: lease age 30 (secs) under 25% threshold, reply with unaltered, existing lease

syslog.1

Sep 30 10:04:00 FIREWALL dbus[773]: [system] Successfully activated service 'org.freedesktop.hostname1'
Sep 30 10:04:00 FIREWALL systemd[1]: Started Hostname Service.
Sep 30 10:05:42 FIREWALL systemd[1]: Stopped ISC DHCP IPv4 server.
Sep 30 10:05:42 FIREWALL systemd[1]: Started ISC DHCP IPv4 server.
Sep 30 10:05:42 FIREWALL dhcpd[16720]: Internet Systems Consortium DHCP Server 4.3.3
Sep 30 10:05:42 FIREWALL dhcpd[16720]: Copyright 2004-2015 Internet Systems Consortium.
Sep 30 10:05:42 FIREWALL sh[16720]: Internet Systems Consortium DHCP Server 4.3.3
Sep 30 10:05:42 FIREWALL sh[16720]: Copyright 2004-2015 Internet Systems Consortium.
Sep 30 10:05:42 FIREWALL sh[16720]: All rights reserved.
Sep 30 10:05:42 FIREWALL sh[16720]: For info, please visit https://www.isc.org/software/dhcp/
Sep 30 10:05:42 FIREWALL dhcpd[16720]: All rights reserved.
Sep 30 10:05:42 FIREWALL dhcpd[16720]: For info, please visit https://www.isc.org/software/dhcp/
Sep 30 10:05:42 FIREWALL dhcpd[16720]: Config file: /etc/dhcp/dhcpd.conf
Sep 30 10:05:42 FIREWALL dhcpd[16720]: Database file: /var/lib/dhcp/dhcpd.leases
Sep 30 10:05:42 FIREWALL sh[16720]: Config file: /etc/dhcp/dhcpd.conf
Sep 30 10:05:42 FIREWALL sh[16720]: Database file: /var/lib/dhcp/dhcpd.leases
Sep 30 10:05:42 FIREWALL sh[16720]: PID file: /run/dhcp-server/dhcpd.pid
Sep 30 10:05:42 FIREWALL dhcpd[16720]: PID file: /run/dhcp-server/dhcpd.pid
Sep 30 10:05:42 FIREWALL sh[16720]: Wrote 2 leases to leases file.
Sep 30 10:05:42 FIREWALL dhcpd[16720]: Internet Systems Consortium DHCP Server 4.3.3

Creio que era estes os logs que vc pediu.......e muito obrigado por estar ajudando.

zekkerj · « **Resposta #5 Online:** 30 de Setembro de 2016, 18:10 »

Teu serviço DHCP tá rodando normalmente, pelos logs que vc postou. Essas mensagens são dele:

Citação de: jonatanrader em 30 de Setembro de 2016, 17:25

Sep 29 07:45:38 FIREWALL dhcpd[7479]: DHCPREQUEST for 192.168.0.16 from 1c:7e:e5:2d:26:2a via enp3s0
Sep 29 07:45:38 FIREWALL dhcpd[7479]: DHCPACK on 192.168.0.16 to 1c:7e:e5:2d:26:2a (FIREWALL) via enp3s0
Sep 29 07:45:50 FIREWALL dhcpd[7479]: reuse_lease: lease age 12 (secs) under 25% threshold, reply with unaltered, existing lease
Sep 29 07:45:50 FIREWALL dhcpd[7479]: DHCPREQUEST for 192.168.0.16 from 1c:7e:e5:2d:26:2a (FIREWALL) via enp3s0
Sep 29 07:45:50 FIREWALL dhcpd[7479]: DHCPACK on 192.168.0.16 to 1c:7e:e5:2d:26:2a via enp3s0
Sep 29 07:45:58 FIREWALL dhcpd[7479]: reuse_lease: lease age 20 (secs) under 25% threshold, reply with unaltered, existing lease
Sep 29 07:45:58 FIREWALL dhcpd[7479]: DHCPREQUEST for 192.168.0.16 from 1c:7e:e5:2d:26:2a via enp3s0
Sep 29 07:45:58 FIREWALL dhcpd[7479]: DHCPACK on 192.168.0.16 to 1c:7e:e5:2d:26:2a via enp3s0
Sep 29 07:46:08 FIREWALL dhcpd[7479]: reuse_lease: lease age 30 (secs) under 25% threshold, reply with unaltered, existing lease

Mas as mensagens de "dhclient" rodando na mesma máquina me preocupam. Você tem certeza de que fixou o IP da placa interna (enp3s0)

Pq esse processo "dhclient" que está logando mensagens não poderia estar ativo...

Mostre de novo o conteúdo de seu arquivo /etc/network/interfaces, por favor.

Citação de: jonatanrader em 30 de Setembro de 2016, 17:25

Sim para todas as perguntas acima. Os comandos que vc passou não roda no Ubuntu Server.

Rodam sim. Só errei o arquivo de log, que não é "/var/log/messages", e sim "/var/log/syslog".

grep -i dhcpd /var/log/syslog | tail -20

jonatanrader · « **Resposta #6 Online:** 03 de Outubro de 2016, 16:10 »

Opa....Obrigado pela ajuda antes de tudo. E sim o Dhcp esta rodando beleza, mas este é o problema, a interface de rede não esta pegando a configuração, anteriormente achei que fosse a propria placa mas não é; E o interessante é que ao reiniciar o serviço de rede, ele da um erro mas depois sobe normal, tipo isto;

Citar

root@FIREWALL:/home/spark# /etc/init.d/isc-dhcp-server restart
[ ok ] Restarting isc-dhcp-server (via systemctl): isc-dhcp-server.service.
root@FIREWALL:/home/spark# /etc/init.d/networking restart
[....] Restarting networking (via systemctl): networking.serviceJob for networking.service failed because a timeout was exceeded. See "systemctl status networking.service" and "journalctl -xe" for details.
failed!

INTERFACE
auto lo
iface lo inet loopback

#REDE EXTERNA - NET

auto enp2s0
iface enp2s0 inet dhcp

#REDE LOCAL
auto enp3s0
iface enp3s0 inet static

address 192.168.0.2
netmask 255.255.255.0
network 192.168.0.0
gateway 192.168.0.1
broadcast 192.168.0.255

>>>>>LOGS
journalctl | grep -Ei 'dhcp'
Out 03 15:14:26 FIREWALL dhclient[699]: Internet Systems Consortium DHCP Client 4.3.3
Out 03 15:14:26 FIREWALL sh[682]: Internet Systems Consortium DHCP Client 4.3.3
Out 03 15:14:26 FIREWALL sh[682]: For info, please visit https://www.isc.org/software/dhcp/
Out 03 15:14:26 FIREWALL dhclient[699]: For info, please visit https://www.isc.org/software/dhcp/
Out 03 15:14:26 FIREWALL dhclient[741]: Internet Systems Consortium DHCP Client 4.3.3
Out 03 15:14:26 FIREWALL sh[700]: Internet Systems Consortium DHCP Client 4.3.3
Out 03 15:14:26 FIREWALL sh[700]: For info, please visit https://www.isc.org/software/dhcp/
Out 03 15:14:26 FIREWALL dhclient[741]: For info, please visit https://www.isc.org/software/dhcp/
Out 03 15:14:26 FIREWALL root[906]: /etc/dhcp/dhclient-enter-hooks.d/avahi-autoipd returned non-zero exit status 1
Out 03 15:14:26 FIREWALL sh[700]: DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 3 (xid=0xd476c178)
Out 03 15:14:26 FIREWALL dhclient[741]: DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 3 (xid=0xd476c178)
Out 03 15:14:26 FIREWALL root[913]: /etc/dhcp/dhclient-enter-hooks.d/avahi-autoipd returned non-zero exit status 1
Out 03 15:14:26 FIREWALL sh[682]: DHCPDISCOVER on enp2s0 to 255.255.255.255 port 67 interval 3 (xid=0x24ef705b)
Out 03 15:14:26 FIREWALL dhclient[699]: DHCPDISCOVER on enp2s0 to 255.255.255.255 port 67 interval 3 (xid=0x24ef705b)
Out 03 15:14:26 FIREWALL dhclient[699]: DHCPREQUEST of 192.168.1.134 on enp2s0 to 255.255.255.255 port 67 (xid=0x5b70ef24)
Out 03 15:14:26 FIREWALL dhclient[699]: DHCPOFFER of 192.168.1.134 from 192.168.1.3
Out 03 15:14:26 FIREWALL sh[682]: DHCPREQUEST of 192.168.1.134 on enp2s0 to 255.255.255.255 port 67 (xid=0x5b70ef24)
Out 03 15:14:26 FIREWALL sh[682]: DHCPOFFER of 192.168.1.134 from 192.168.1.3
Out 03 15:14:27 FIREWALL dhclient[699]: DHCPACK of 192.168.1.134 from 192.168.1.3
Out 03 15:14:27 FIREWALL sh[682]: DHCPACK of 192.168.1.134 from 192.168.1.3
Out 03 15:14:27 FIREWALL root[924]: /etc/dhcp/dhclient-enter-hooks.d/avahi-autoipd returned non-zero exit status 1
Out 03 15:14:27 FIREWALL root[926]: /etc/dhcp/dhclient-enter-hooks.d/samba returned non-zero exit status 1
Out 03 15:14:29 FIREWALL dhclient[741]: DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 4 (xid=0xd476c178)
Out 03 15:14:29 FIREWALL sh[700]: DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 4 (xid=0xd476c178)
Out 03 15:14:31 FIREWALL NetworkManager[834]: <info> [1475518471.3354] Using DHCP client 'dhclient'
Out 03 15:14:33 FIREWALL dhclient[741]: DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 10 (xid=0xd476c178)
Out 03 15:14:33 FIREWALL sh[700]: DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 10 (xid=0xd476c178)
Out 03 15:14:43 FIREWALL dhclient[741]: DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 21 (xid=0xd476c178)
Out 03 15:14:43 FIREWALL sh[700]: DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 21 (xid=0xd476c178)
Out 03 15:15:04 FIREWALL dhclient[741]: DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 19 (xid=0xd476c178)
Out 03 15:15:04 FIREWALL sh[700]: DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 19 (xid=0xd476c178)
.....
Out 03 15:19:24 FIREWALL systemd[1]: Started ISC DHCP IPv4 server.
Out 03 15:19:24 FIREWALL dhcpd[1550]: Internet Systems Consortium DHCP Server 4.3.3
Out 03 15:19:24 FIREWALL sh[1550]: Internet Systems Consortium DHCP Server 4.3.3
Out 03 15:19:24 FIREWALL sh[1550]: For info, please visit https://www.isc.org/software/dhcp/
Out 03 15:19:24 FIREWALL dhcpd[1550]: Copyright 2004-2015 Internet Systems Consortium.
Out 03 15:19:24 FIREWALL dhcpd[1550]: All rights reserved.
Out 03 15:19:24 FIREWALL dhcpd[1550]: For info, please visit https://www.isc.org/software/dhcp/
Out 03 15:19:24 FIREWALL dhcpd[1550]: Config file: /etc/dhcp/dhcpd.conf
Out 03 15:19:24 FIREWALL dhcpd[1550]: Database file: /var/lib/dhcp/dhcpd.leases
Out 03 15:19:24 FIREWALL sh[1550]: Config file: /etc/dhcp/dhcpd.conf
Out 03 15:19:24 FIREWALL sh[1550]: Database file: /var/lib/dhcp/dhcpd.leases
Out 03 15:19:24 FIREWALL sh[1550]: PID file: /run/dhcp-server/dhcpd.pid
Out 03 15:19:24 FIREWALL dhcpd[1550]: PID file: /run/dhcp-server/dhcpd.pid
Out 03 15:19:24 FIREWALL dhcpd[1550]: Internet Systems Consortium DHCP Server 4.3.3
Out 03 15:19:24 FIREWALL dhcpd[1550]: Copyright 2004-2015 Internet Systems Consortium.
Out 03 15:19:24 FIREWALL dhcpd[1550]: All rights reserved.
Out 03 15:19:24 FIREWALL dhcpd[1550]: For info, please visit https://www.isc.org/software/dhcp/
Out 03 15:19:24 FIREWALL dhcpd[1550]: Wrote 2 leases to leases file.
Out 03 15:19:24 FIREWALL dhcpd[1550]:
Out 03 15:19:24 FIREWALL dhcpd[1550]: No subnet declaration for enp3s0 (no IPv4 addresses).
Out 03 15:19:24 FIREWALL sh[1550]: in your dhcpd.conf file for the network segment
Out 03 15:19:24 FIREWALL dhcpd[1550]: ** Ignoring requests on enp3s0. If this is not what
Out 03 15:19:24 FIREWALL systemd[1]: isc-dhcp-server.service: Main process exited, code=exited, status=1/FAILURE
Out 03 15:19:24 FIREWALL dhcpd[1550]: you want, please write a subnet declaration
Out 03 15:19:24 FIREWALL systemd[1]: isc-dhcp-server.service: Unit entered failed state.
Out 03 15:19:24 FIREWALL dhcpd[1550]: in your dhcpd.conf file for the network segment
Out 03 15:19:24 FIREWALL systemd[1]: isc-dhcp-server.service: Failed with result 'exit-code'.
Out 03 15:19:24 FIREWALL dhcpd[1550]: to which interface enp3s0 is attached. **
Out 03 15:19:24 FIREWALL dhcpd[1550]:
Out 03 15:19:24 FIREWALL dhcpd[1550]:
Out 03 15:19:24 FIREWALL dhcpd[1550]: Not configured to listen on any interfaces!
Out 03 15:19:24 FIREWALL dhcpd[1550]:
Out 03 15:19:24 FIREWALL dhcpd[1550]: If you think you have received this message due to a bug rather
Out 03 15:19:24 FIREWALL dhcpd[1550]: than a configuration issue please read the section on submitting
Out 03 15:19:24 FIREWALL dhcpd[1550]: bugs on either our web page at www.isc.org or in the README file
Out 03 15:19:24 FIREWALL dhcpd[1550]: before submitting a bug. These pages explain the proper
Out 03 15:19:24 FIREWALL dhcpd[1550]: process and the information we find helpful for debugging..

.......
ut 03 15:19:28 FIREWALL dhclient[741]: No DHCPOFFERS received.
Out 03 15:19:28 FIREWALL sh[700]: No DHCPOFFERS received.
Out 03 15:23:47 FIREWALL dhclient[1996]: DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 3 (xid=0x5affc177)
Out 03 15:23:50 FIREWALL dhclient[1996]: DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 7 (xid=0x5affc177)
Out 03 15:23:57 FIREWALL dhclient[1996]: DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 8 (xid=0x5affc177)
.....
Out 03 15:54:14 FIREWALL dhclient[4218]: DHCPRELEASE on enp2s0 to 192.168.1.3 port 67 (xid=0x14cd58c3)
Out 03 15:54:14 FIREWALL ifdown[4116]: DHCPRELEASE on enp2s0 to 192.168.1.3 port 67 (xid=0x14cd58c3)
Out 03 15:54:14 FIREWALL root[4228]: /etc/dhcp/dhclient-enter-hooks.d/avahi-autoipd returned non-zero exit status 1
Out 03 15:54:14 FIREWALL root[4265]: /etc/dhcp/dhclient-enter-hooks.d/samba returned non-zero exit status 1
Out 03 15:54:14 FIREWALL dhclient[4343]: Internet Systems Consortium DHCP Client 4.3.3
Out 03 15:54:14 FIREWALL ifup[4298]: Internet Systems Consortium DHCP Client 4.3.3
Out 03 15:54:14 FIREWALL ifup[4298]: For info, please visit https://www.isc.org/software/dhcp/
Out 03 15:54:14 FIREWALL dhclient[4343]: For info, please visit https://www.isc.org/software/dhcp/
Out 03 15:54:14 FIREWALL root[4347]: /etc/dhcp/dhclient-enter-hooks.d/avahi-autoipd returned non-zero exit status 1
Out 03 15:54:14 FIREWALL ifup[4298]: DHCPDISCOVER on enp2s0 to 255.255.255.255 port 67 interval 3 (xid=0xe1c5633a)
Out 03 15:54:14 FIREWALL dhclient[4343]: DHCPDISCOVER on enp2s0 to 255.255.255.255 port 67 interval 3 (xid=0xe1c5633a)
Out 03 15:54:14 FIREWALL dhclient[4343]: DHCPREQUEST of 192.168.1.134 on enp2s0 to 255.255.255.255 port 67 (xid=0x3a63c5e1)
Out 03 15:54:14 FIREWALL ifup[4298]: DHCPREQUEST of 192.168.1.134 on enp2s0 to 255.255.255.255 port 67 (xid=0x3a63c5e1)
Out 03 15:54:14 FIREWALL ifup[4298]: DHCPOFFER of 192.168.1.134 from 192.168.1.3
Out 03 15:54:14 FIREWALL dhclient[4343]: DHCPOFFER of 192.168.1.134 from 192.168.1.3
Out 03 15:54:15 FIREWALL dhclient[4343]: DHCPACK of 192.168.1.134 from 192.168.1.3
Out 03 15:54:15 FIREWALL ifup[4298]: DHCPACK of 192.168.1.134 from 192.168.1.3
Out 03 15:54:15 FIREWALL root[4353]: /etc/dhcp/dhclient-enter-hooks.d/avahi-autoipd returned non-zero exit status 1
Out 03 15:54:15 FIREWALL root[4355]: /etc/dhcp/dhclient-enter-hooks.d/samba returned non-zero exit status 1
Out 03 15:54:28 FIREWALL dhclient[1996]: DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 15 (xid=0xec055103)

root@FIREWALL:/home/spark# tail -f /var/log/syslog
root@FIREWALL:/home/spark# tail -f /var/log/syslog
Oct 3 16:03:01 FIREWALL dhclient[1996]: DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 8 (xid=0x69d1cd5d)
Oct 3 16:03:09 FIREWALL dhclient[1996]: DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 20 (xid=0x69d1cd5d)
Oct 3 16:03:29 FIREWALL dhclient[1996]: DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 17 (xid=0x69d1cd5d)
Oct 3 16:03:46 FIREWALL dhclient[1996]: DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 12 (xid=0x69d1cd5d)
Oct 3 16:03:58 FIREWALL dhclient[1996]: DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 14 (xid=0x69d1cd5d)
Oct 3 16:04:12 FIREWALL dhclient[1996]: DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 9 (xid=0x69d1cd5d)
Oct 3 16:04:21 FIREWALL dhclient[1996]: DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 9 (xid=0x69d1cd5d)
Oct 3 16:04:30 FIREWALL dhclient[1996]: DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 13 (xid=0x69d1cd5d)
Oct 3 16:04:43 FIREWALL dhclient[1996]: DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 11 (xid=0x69d1cd5d)
Oct 3 16:04:54 FIREWALL dhclient[1996]: DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 12 (xid=0x69d1cd5d)
Oct 3 16:05:18 FIREWALL dhclient[1996]: message repeated 2 times: [ DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 12 (xid=0x69d1cd5d)]
Oct 3 16:05:30 FIREWALL dhclient[1996]: DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 18 (xid=0x69d1cd5d)
Oct 3 16:05:48 FIREWALL dhclient[1996]: No DHCPOFFERS received.
Oct 3 16:05:48 FIREWALL dhclient[1996]: No working leases in persistent database - sleeping.
Oct 3 16:05:48 FIREWALL root: /etc/dhcp/dhclient-exit-hooks.d/zzz_avahi-autoipd returned non-zero exit status 1

root@FIREWALL:/home/spark# grep -i dhcpd /var/log/syslog | tail -20
Oct 3 16:00:55 FIREWALL dhclient[1996]: DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 13 (xid=0x69d1cd5d)
Oct 3 16:01:08 FIREWALL dhclient[1996]: DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 20 (xid=0x69d1cd5d)
Oct 3 16:01:28 FIREWALL dhclient[1996]: DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 17 (xid=0x69d1cd5d)
Oct 3 16:01:45 FIREWALL dhclient[1996]: DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 16 (xid=0x69d1cd5d)
Oct 3 16:02:01 FIREWALL dhclient[1996]: DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 17 (xid=0x69d1cd5d)
Oct 3 16:02:18 FIREWALL dhclient[1996]: DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 21 (xid=0x69d1cd5d)
Oct 3 16:02:39 FIREWALL dhclient[1996]: DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 7 (xid=0x69d1cd5d)
Oct 3 16:02:46 FIREWALL dhclient[1996]: DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 15 (xid=0x69d1cd5d)
Oct 3 16:03:01 FIREWALL dhclient[1996]: DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 8 (xid=0x69d1cd5d)
Oct 3 16:03:09 FIREWALL dhclient[1996]: DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 20 (xid=0x69d1cd5d)
Oct 3 16:03:29 FIREWALL dhclient[1996]: DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 17 (xid=0x69d1cd5d)
Oct 3 16:03:46 FIREWALL dhclient[1996]: DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 12 (xid=0x69d1cd5d)
Oct 3 16:03:58 FIREWALL dhclient[1996]: DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 14 (xid=0x69d1cd5d)
Oct 3 16:04:12 FIREWALL dhclient[1996]: DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 9 (xid=0x69d1cd5d)
Oct 3 16:04:21 FIREWALL dhclient[1996]: DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 9 (xid=0x69d1cd5d)
Oct 3 16:04:30 FIREWALL dhclient[1996]: DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 13 (xid=0x69d1cd5d)
Oct 3 16:04:43 FIREWALL dhclient[1996]: DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 11 (xid=0x69d1cd5d)
Oct 3 16:04:54 FIREWALL dhclient[1996]: DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 12 (xid=0x69d1cd5d)
Oct 3 16:05:18 FIREWALL dhclient[1996]: message repeated 2 times: [ DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 12 (xid=0x69d1cd5d)]
Oct 3 16:05:30 FIREWALL dhclient[1996]: DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 18 (xid=0x69d1cd5d)

zekkerj · « **Resposta #7 Online:** 03 de Outubro de 2016, 16:51 »

Citar

address 192.168.0.2
netmask 255.255.255.0
network 192.168.0.0
gateway 192.168.0.1
broadcast 192.168.0.255

Essa máquina não é o gateway da rede? Então ela própria deveria receber o endereço "192.168.0.1".
Além disso, se o ela já tem uma saída pra internet pela placa externa, ela não precisa de outro gateway. Remova ou desative ("comente") essa linha.

zekkerj · « **Resposta #8 Online:** 03 de Outubro de 2016, 16:55 »

Ainda tem algum erro na tua configuração. Gostaria que você mostrasse novamente os arquivos /etc/default/dhcp, /etc/dhcp/dhcpd.conf, e a saída do comando "ifconfig enp3s0".

jonatanrader · « **Resposta #9 Online:** 04 de Outubro de 2016, 10:10 »

Aqui esta as informações:

enp3s0 Link encap:Ethernet Endereço de HW 1c:7e:e5xxxx
inet end.: 192.168.0.16 Bcast:192.168.0.255 Masc:255.255.255.0
endereço inet6: fe80::1e7e:e5ff:fe2d:262a/64 Escopo:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Métrica:1
pacotes RX:2518 erros:0 descartados:0 excesso:0 quadro:0
Pacotes TX:10722 erros:0 descartados:0 excesso:0 portadora:0
colisões:0 txqueuelen:1000
RX bytes:187712 (187.7 KB) TX bytes:1074998 (1.0 MB)

/etc/default/dhcp

# Path to dhcpd's config file (default: /etc/dhcp/dhcpd.conf).
#DHCPD_CONF=/etc/dhcp/dhcpd.conf

# Path to dhcpd's PID file (default: /var/run/dhcpd.pid).
#DHCPD_PID=/var/run/dhcpd.pid

# Additional options to start dhcpd with.
#   Don't use options -cf or -pf here; use DHCPD_CONF/ DHCPD_PID instead
#OPTIONS=""

# On what interfaces should the DHCP server (dhcpd) serve DHCP requests?
#   Separate multiple interfaces with spaces, e.g. "eth0 eth1".
INTERFACES="enp3s0"

#atualização
   ddns-update-style none;
   log-facility local7;

   default-lease-time 800;
   max-lease-time 1200;
   authoritative;
   option domain-name-servers 8.8.4.4,8.8.8.8;
   #option subnet-mask 255.255.255.0;

#escopo DHCP

   subnet 192.168.0.0 netmask 255.255.255.0 {
      range 192.168.0.15 192.168.0.254;
      option broadcast-address 192.168.0.255;
      option routers 192.168.0.1;

      default-lease-time 800;
      max-lease-time 1200;

}

Mais uma vez obrigado por ajudar.

zekkerj · « **Resposta #10 Online:** 04 de Outubro de 2016, 10:14 »

Por algum motivo que eu ainda não consegui entender, sua placa 'enp3s0' está pegando um IP dinâmico, apesar de ter sido configurada com um IP estático.

Vc instalou interface gráfica nesse servidor? $:-\$

jonatanrader · « **Resposta #11 Online:** 04 de Outubro de 2016, 11:54 »

Opa, não instalei. E tem mais uma coisa com a placa enp3so, Criei um script para o iptable, porém a placa de rede não sobe, da um erro:
oot@FIREWALL:/home/spark# systemctl status networking.service
● networking.service - Raise network interfaces
Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled)
Drop-In: /run/systemd/generator/networking.service.d
└─50-insserv.conf-$network.conf
Active: failed (Result: exit-code) since Ter 2016-10-04 11:27:38 BRT; 18min ago
Docs: man:interfaces(5)
Process: 24545 ExecStop=/sbin/ifdown -a --read-environment (code=exited, status=0/SUCCESS)
Process: 26461 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=1/FAILURE)
Process: 26456 ExecStartPre=/bin/sh -c [ "$CONFIGURE_INTERFACES" != "no" ] && [ -n "$(ifquery --read-environment --list --exclude=lo)" ] && udevadm se
Main PID: 26461 (code=exited, status=1/FAILURE)

Out 04 11:27:38 FIREWALL ifup[26461]: Failed to bring up enp3s0.
Out 04 11:27:38 FIREWALL ifup[26461]: Bad argument `sudo'
Out 04 11:27:38 FIREWALL ifup[26461]: Error occurred at line: 5
Out 04 11:27:38 FIREWALL ifup[26461]: Try `iptables-restore -h' or 'iptables-restore --help' for more information.
Out 04 11:27:38 FIREWALL ifup[26461]: run-parts: /etc/network/if-up.d/iptables exited with return code 2
Out 04 11:27:38 FIREWALL ifup[26461]: /sbin/ifup: post-up script failed.
Out 04 11:27:38 FIREWALL systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE
Out 04 11:27:38 FIREWALL systemd[1]: Failed to start Raise network interfaces.
Out 04 11:27:38 FIREWALL systemd[1]: networking.service: Unit entered failed state.
Out 04 11:27:38 FIREWALL systemd[1]: networking.service: Failed with result 'exit-code'.

Iptables
sudo iptables -P INPUT ACCEPT
sudo iptables -F INPUT
sudo iptables -P OUTPUT ACCEPT
sudo iptables -F OUTPUT
sudo iptables -P FORWARD DROP
sudo iptables -F FORWARD
sudo iptables -t nat -F

sudo iptables -A FORWARD -i enp2s0 -o enp3s0 -m state --state ESTABLISHED,RELATED -j ACCEPT
sudo iptables -A FORWARD -i enp3s0 -o enp2s0 -j ACCEPT
sudo iptables -A FORWARD -j LOG

sudo iptables -t nat -A POSTROUTING -o enp2s0 -j MASQUERADE

Script do iptable

#!/bin/sh
# script: iptables
/sbin/iptables-restore /etc/network/iptables.rules

zekkerj · « **Resposta #12 Online:** 04 de Outubro de 2016, 12:43 »

O comando "sudo" não pode ser usado em scripts de serviço, pois estes não estão associados a um terminal (necessário pra ler a senha). Nem precisa: o script de serviço, por definição, já é executado pelo root.

O lance da interface gráfica seria a possibilidade de vc ter o NetworkManager ativo nessa interface --- mesmo sabendo que quando o NM encontra a interface configurada no /etc/network/interfaces, ele a coloca em modo "não-gerenciado" e sai do caminho.

Outra possibilidade... há alguns dias eu tive problemas com uma máquina Kubuntu 16.04, que não estava configurando corretamente a interface cabeada. Como a autenticação dessa máquina é por LDAP, eu ficava sem poder usá-la até ativar a interface manualmente. Isso foi resolvido com uma atualização do comando "ifup".

Você está com todas as atualizações instaladas? Pode verificar isso?

jonatanrader · « **Resposta #13 Online:** 04 de Outubro de 2016, 15:14 »

Este é o problema, por conta disto eu já havia trocado a placa de rede, e reinstalado o sistema...

Ao tentar subir a interface acontece:

root@FIREWALL:/home/spark# ifup enp3s0
RTNETLINK answers: File exists
Failed to bring up enp3s0.

Dados do sistema
root@FIREWALL:/home/spark# uname -a ##
Linux FIREWALL 4.4.0-41-generic #61-Ubuntu SMP Tue Sep 27 17:27:48 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

root@FIREWALL:/home/spark# lsb_release -a
No LSB modules are available.
Distributor ID:   Ubuntu
Description:   Ubuntu 16.04.1 LTS
Release:   16.04
Codename:   xenial

O sistema esta atualizado, refiz as configs novamente, pois poderia ter esquecido algo, mas a interface ainda da erro
Irei limpar as regras do Iptables

● networking.service - Raise network interfaces
Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled)
Drop-In: /run/systemd/generator/networking.service.d
└─50-insserv.conf-$network.conf
Active: failed (Result: exit-code) since Ter 2016-10-04 15:09:13 BRT; 24s ago
Docs: man:interfaces(5)
Process: 5727 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=1/FAILURE)
Process: 5723 ExecStartPre=/bin/sh -c [ "$CONFIGURE_INTERFACES" != "no" ] && [ -n "$(ifquery --read
Main PID: 5727 (code=exited, status=1/FAILURE)

Out 04 15:09:12 FIREWALL ifup[5727]: Failed to bring up enp2s0.
Out 04 15:09:12 FIREWALL ifup[5727]: RTNETLINK answers: File exists
Out 04 15:09:12 FIREWALL ifup[5727]: Failed to bring up enp3s0.
Out 04 15:09:12 FIREWALL ifup[5727]: iptables-restore: line 1 failed
Out 04 15:09:12 FIREWALL ifup[5727]: run-parts: /etc/network/if-up.d/iptables exited with return code
Out 04 15:09:12 FIREWALL ifup[5727]: /sbin/ifup: post-up script failed.
Out 04 15:09:12 FIREWALL systemd[1]: networking.service: Main process exited, code=exited, status=1/F
Out 04 15:09:13 FIREWALL systemd[1]: Failed to start Raise network interfaces.
Out 04 15:09:13 FIREWALL systemd[1]: networking.service: Unit entered failed state.
Out 04 15:09:13 FIREWALL systemd[1]: networking.service: Failed with result 'exit-code'.

zekkerj · « **Resposta #14 Online:** 04 de Outubro de 2016, 15:24 »

Como está seu arquivo /etc/network/interfaces, neste momento?

EDIT: Vc está reiniciando seu servidor após as mudanças, ou apenas reiniciando a interface?

Notícias:

Autor Tópico: Ubuntu server não sobe DHCP (Lida 18809 vezes)

jonatanrader

Ubuntu server não sobe DHCP

zekkerj

Re:Ubuntu server não sobe DHCP

jonatanrader

Re:Ubuntu server não sobe DHCP

zekkerj

Re:Ubuntu server não sobe DHCP

jonatanrader

Re:Ubuntu server não sobe DHCP

zekkerj

Re:Ubuntu server não sobe DHCP

jonatanrader

Re:Ubuntu server não sobe DHCP

zekkerj

Re:Ubuntu server não sobe DHCP

zekkerj

Re:Ubuntu server não sobe DHCP

jonatanrader

Re:Ubuntu server não sobe DHCP

zekkerj

Re:Ubuntu server não sobe DHCP

jonatanrader

Re:Ubuntu server não sobe DHCP

zekkerj

Re:Ubuntu server não sobe DHCP

jonatanrader

Re:Ubuntu server não sobe DHCP

zekkerj

Re:Ubuntu server não sobe DHCP