Modify

Ticket #2098 (closed defect: worksforme)

Opened 3 years ago

Last modified 8 months ago

DHCP won't stay running

Reported by: j.scott.gwin@… Owned by: jamor@…
Milestone: 3.0 Component: dhcp
Severity: trivial Keywords:
Cc:

Description

on Ubuntu Server 10.04 w/all current updates, ebox ver. 1.5.

DHCP won't stay running longer than 1-2 minutes. I can restart in the dashboard and watch it stop very quickly. Nothing shows up in the ebox logging system. But when I tail syslog:

Aug 13 04:03:14 ebox dhcpd: Not configured to listen on any interfaces! Aug 13 04:03:14 ebox init: ebox.dhcpd3 main process (19142) terminated with status 1 Aug 13 04:03:14 ebox init: ebox.dhcpd3 main process ended, respawning Aug 13 04:03:14 ebox dhcpd: Wrote 0 leases to leases file. Aug 13 04:03:14 ebox dhcpd: Aug 13 04:03:14 ebox dhcpd: No subnet declaration for virbr0 (192.168.122.1). Aug 13 04:03:14 ebox dhcpd: Ignoring requests on virbr0. If this is not what Aug 13 04:03:14 ebox dhcpd: you want, please write a subnet declaration Aug 13 04:03:14 ebox dhcpd: in your dhcpd.conf file for the network segment Aug 13 04:03:14 ebox dhcpd: to which interface virbr0 is attached. Aug 13 04:03:14 ebox dhcpd: Aug 13 04:03:14 ebox dhcpd: Aug 13 04:03:14 ebox dhcpd: No subnet declaration for wlan0 (192.168.2.1). Aug 13 04:03:14 ebox dhcpd: Ignoring requests on wlan0. If this is not what Aug 13 04:03:14 ebox dhcpd: you want, please write a subnet declaration Aug 13 04:03:14 ebox dhcpd: in your dhcpd.conf file for the network segment Aug 13 04:03:14 ebox dhcpd: to which interface wlan0 is attached. Aug 13 04:03:14 ebox dhcpd: Aug 13 04:03:14 ebox dhcpd: Aug 13 04:03:14 ebox dhcpd: No subnet declaration for eth1 (192.168.1.2). Aug 13 04:03:14 ebox dhcpd: Ignoring requests on eth1. If this is not what Aug 13 04:03:14 ebox dhcpd: you want, please write a subnet declaration Aug 13 04:03:14 ebox dhcpd: in your dhcpd.conf file for the network segment Aug 13 04:03:14 ebox dhcpd: to which interface eth1 is attached. Aug 13 04:03:14 ebox dhcpd: Aug 13 04:03:14 ebox dhcpd: Aug 13 04:03:14 ebox dhcpd: No subnet declaration for eth0 (192.168.1.35). Aug 13 04:03:14 ebox dhcpd: Ignoring requests on eth0. If this is not what Aug 13 04:03:14 ebox dhcpd: you want, please write a subnet declaration Aug 13 04:03:14 ebox dhcpd: in your dhcpd.conf file for the network segment Aug 13 04:03:14 ebox dhcpd: to which interface eth0 is attached. This isn't something I've ever had to do before and if it needs to be done, why isn't there a place to do it within the web interface?

Attachments

syslog.txt Download (8.9 KB) - added by j.scott.gwin@… 3 years ago.
output of syslog tail

Change History

Changed 3 years ago by j.scott.gwin@…

output of syslog tail

comment:1 in reply to: ↑ description Changed 3 years ago by j.scott.gwin@…

Replying to j.scott.gwin@gmail.com:

I apologize for the mess I posted at first.

on Ubuntu Server 10.04 w/all current updates, ebox ver. 1.5.

DHCP won't stay running longer than 1-2 minutes. I can restart in the dashboard and watch it stop very quickly. Nothing shows up in the ebox logging system. But when I tail syslog I get the output I have attached.>

This isn't something I've ever had to do before and if it needs to be done, why isn't there a place to do it within the web interface?

comment:2 Changed 3 years ago by anonymous

I'm having the same problem with the same output but can't figure out why? have you had any joy with this yet?

This also happens after a fresh install, 2 x NIC's, one external, one internal.

comment:3 Changed 3 years ago by jsoriano@…

  • Status changed from new to closed
  • Resolution set to worksforme

Hi,

To enable DHCP you need at least an internal network interface configured statically. Could you check those settings?

You should also check that there is no other DHCP server in your network.

If the problem persists, please, reopen the ticket describing your network interfaces settings.

Thanks!

comment:4 Changed 19 months ago by anonymous@…

  • priority changed from normal to lowest
  • Severity changed from normal to trivial

Same thing here DHCP broken out of the box. Set eth1 static

Interface IP address: 192.168.0.1 Subnet: 192.168.0.0/24 Available range: 192.168.0.1 - 192.168.0.254

/var/log/daemon.log.

Oct 22 18:27:22 fw1 dhcpd: No subnet declaration for eth1 (192.168.0.1). Oct 22 18:27:22 fw1 dhcpd: Ignoring requests on eth1. If this is not what Oct 22 18:27:22 fw1 dhcpd: you want, please write a subnet declaration Oct 22 18:27:22 fw1 dhcpd: in your dhcpd.conf file for the network segment Oct 22 18:27:22 fw1 dhcpd: to which interface eth1 is attached.

Seems pushing save, saves every module but the intened. Thats neat feature; editing dhcp, or any setting zentyal has to save squid settings? Maybe it should save my cron jobs again?

I came from ClearOS thinking the grass was greener on the other side because CentOS and it's repositories are usually a complete mess. Although a firewall that can't support dhcpd out of the box is pretty useless. Then to find out the backend is perl! Eeek! I'll have to just old school CLI this or buy a real hardware appliance. Also, keep with the trend and leave as closed/trivial.

comment:5 Changed 18 months ago by galaxys2875@…

  • Status changed from closed to reopened
  • Resolution worksforme deleted

I have the same problem . syslog Nov 15 17:37:30 ubuntu dhcpd: No subnet declaration for eth2 (192.168.1.1). Nov 15 17:37:30 ubuntu dhcpd: Ignoring requests on eth2. If this is not what Nov 15 17:37:30 ubuntu dhcpd: you want, please write a subnet declaration Nov 15 17:37:30 ubuntu dhcpd: in your dhcpd.conf file for the network segment Nov 15 17:37:30 ubuntu dhcpd: to which interface eth2 is attached. Nov 15 17:37:30 ubuntu dhcpd: Nov 15 17:37:30 ubuntu dhcpd: Nov 15 17:37:30 ubuntu dhcpd: Not configured to listen on any interfaces!

comment:6 Changed 18 months ago by galaxys2875@…

  • Status changed from reopened to closed
  • Resolution set to fixed

HI I fixed the problem by adding a range

dhcp won't start without adding at least 1 range

comment:7 Changed 11 months ago by me@…

  • Status changed from closed to reopened
  • Resolution fixed deleted

Zentyal does such a great job generally in guiding a user through setting up a network that I think the absence of a clear indication in the UI that adding a range is required should be considered a bug. Zentyal does exactly this kind of hand holding in a number of places and I'm not exactly inexperienced with configuring a DHCP server and this one confounded me for far too long.

comment:8 Changed 11 months ago by jamor@…

  • Status changed from reopened to accepted

comment:9 Changed 11 months ago by jacalvo@…

  • Milestone set to 3.0

comment:10 Changed 9 months ago by jacalvo@…

  • Owner changed from ejhernandez@… to jamor@…

comment:11 Changed 8 months ago by jacalvo@…

  • Status changed from accepted to closed
  • Resolution set to worksforme

This should be fixed already in Zentyal 3.0 RC2, please reopen if you still can provide detailed steps on how to reproduce it. Thanks!

View

Add a comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
The resolution will be deleted. Next status will be 'reopened'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.