Problems on Alix 2.0 RC will not start DHCP server on LAN interface
-
I upgraded to the latest 2.0 RC snapshot. 2.0 RC did not recognize
my pppoe interface at first until I reset all settings to factory defaults.My OPT1 interface will not issue DHCP leases.
Moreover, I do not even think clients can see Pfsesne
because static ips assigned to clients do not work.My Network:
vr2 WAN ppoe0 –--- vr1 OPT1 ----- vr0 LAN
| | |
WAN 192.168.2.1 192.168.1.1
| |
dhcp server dhcp server==========OS==============
Name pfSense.localdomain
Version 2.0-RC1 (i386)
built on Sat Feb 26 16:33:51 EST 2011Platform nanobsd (2g)
NanoBSD Boot Slice pfsense1 / ad0s2
CPU Type Geode(TM) Integrated Processor by AMD PCS==========LOG=============
dhcpd: For info, please visit https://www.isc.org/software/dhcp/
Mar 1 11:01:45 dhcpd: All rights reserved.
Mar 1 11:01:45 dhcpd: Copyright 2004-2010 Internet Systems Consortium.
Mar 1 11:01:45 dhcpd: Internet Systems Consortium DHCP Server 4.1.1-P1
Mar 1 19:01:43 check_reload_status: syncing firewall
Mar 1 11:01:04 dhcpd: For info, please visit https://www.isc.org/software/dhcp/
Mar 1 11:01:04 dhcpd: All rights reserved.
Mar 1 11:01:04 dhcpd: Copyright 2004-2010 Internet Systems Consortium.
Mar 1 11:01:04 dhcpd: Internet Systems Consortium DHCP Server 4.1.1-P1
Mar 1 19:01:03 check_reload_status: syncing firewall
Mar 1 10:52:11 dhcpd: For info, please visit https://www.isc.org/software/dhcp/
Mar 1 10:52:11 dhcpd: All rights reserved.
Mar 1 10:52:11 dhcpd: Copyright 2004-2010 Internet Systems Consortium.
Mar 1 10:52:11 dhcpd: Internet Systems Consortium DHCP Server 4.1.1-P1
Mar 1 18:52:10 check_reload_status: syncing firewall
Mar 1 10:51:50 dhcpd: For info, please visit https://www.isc.org/software/dhcp/
Mar 1 10:51:50 dhcpd: All rights reserved.
Mar 1 10:51:50 dhcpd: Copyright 2004-2010 Internet Systems Consortium.
Mar 1 10:51:50 dhcpd: Internet Systems Consortium DHCP Server 4.1.1-P1
Mar 1 18:51:49 check_reload_status: syncing firewall
Mar 1 18:51:34 check_reload_status: syncing firewall
Mar 1 10:51:34 syslogd: kernel boot file is /boot/kernel/kernel
Mar 1 10:51:34 syslogd: exiting on signal 15
Mar 1 10:39:32 syslogd: kernel boot file is /boot/kernel/kernel
Mar 1 10:39:32 syslogd: exiting on signal 15
Mar 1 10:37:33 kernel: vr2: link state changed to UP
Mar 1 18:37:33 check_reload_status: Linkup starting vr2
Mar 1 10:34:20 php: : Hotplug event detected for lan but ignoring since interface is configured with static IP (192.168.1.1)
Mar 1 10:34:19 kernel: vr0: link state changed to UP
Mar 1 18:34:19 check_reload_status: Linkup starting vr0
Mar 1 10:33:48 php: : Hotplug event detected for lan but ignoring since interface is configured with static IP (192.168.1.1)
Mar 1 10:33:47 kernel: vr0: link state changed to DOWN
Mar 1 18:33:47 check_reload_status: Linkup starting vr0
Mar 1 10:33:33 kernel: vr2: link state changed to DOWN
Mar 1 18:33:33 check_reload_status: Linkup starting vr2
Mar 1 10:32:56 php: : Hotplug event detected for lan but ignoring since interface is configured with static IP (192.168.1.1)
Mar 1 10:32:55 kernel: vr0: link state changed to UP
Mar 1 18:32:55 check_reload_status: Linkup starting vr0
Mar 1 10:32:48 php: : Hotplug event detected for lan but ignoring since interface is configured with static IP (192.168.1.1)
Mar 1 10:32:47 kernel: vr0: link state changed to DOWN
Mar 1 18:32:47 check_reload_status: Linkup starting vr0
Mar 1 18:25:59 check_reload_status: reloading filter
Mar 1 18:25:56 check_reload_status: syncing firewall
Mar 1 10:25:33 kernel: vr2: link state changed to UP
Mar 1 18:25:33 check_reload_status: Linkup starting vr2
Mar 1 10:21:33 kernel: vr2: link state changed to DOWN
Mar 1 18:21:33 check_reload_status: Linkup starting vr2 -
Hard to say from that, first guess your OPT interface isn't enabled?
-
I enabled the OP1 interface and added a firewall rule through the GUI.
Still no go.
I guess a settings for the dhcp server is not being set in the xml.
Robert
-
What do the settings for the DHCP server look like for opt1? What does /var/dhcpd/etc/dhcpd.conf look like?
-
option domain-name "localdomain";
option ldap-server code 95 = text;
option domain-search-list code 119 = text;default-lease-time 7200;
max-lease-time 86400;
log-facility local7;
ddns-update-style none;
one-lease-per-client true;
deny duplicates;
ping-check true;
authoritative;
subnet 192.168.1.0 netmask 255.255.255.0 {
pool {
range 192.168.1.11 192.168.1.22;
}
option routers 192.168.1.1;
option domain-name-servers 192.168.1.1;}
subnet 192.168.2.0 netmask 255.255.255.0 {
pool {
range 192.168.2.22 192.168.2.25;
}
option routers 192.168.2.1;
option domain-name-servers 192.168.2.1;}
-
Looks normal to me… Anything blocked in the firewall logs on that interface?
-
/var/dhcpd/var/db/
-
The one ending in ~ is a backup, not the real leases file.
Are you low on space on /var maybe?
-
Filesystem Size Used Avail Capacity Mounted on
/dev/ufs/pfsense1 913M 136M 704M 16% /
devfs 1.0K 1.0K 0B 100% /dev
/dev/md0 38M 270K 35M 1% /tmp
/dev/md1 58M 7.7M 46M 14% /var
/dev/ufs/cf 49M 287K 45M 1% /cf
devfs 1.0K 1.0K 0B 100% /var/dhcpd/dev -
Packet capture on the OPT1 interface, see if the traffic for either statically assigned hosts, or DHCP requests, gets to it. Check the dhcpd process's command line arguments for the interfaces.
-
Heres the DHCP process's command line arguments;
I'll do a packet capture.dhcpd 18718 0.0 1.6 6752 4024 ?? Ss 1:48PM 0:00.81 /usr/local/sbin/dhcpd -user dhcpd -group _dhcp -chroot /var/dhcpd -cf /etc/dhcpd.conf vr0 vr1
Strange, I select OPT1 in the Packet Cap GUI and seems like its selecting the WAN interface.
Just rename the file to .pcap
Robert
-
Strange, I select OPT1 in the Packet Cap GUI and seems like its selecting the WAN interface.
that's your WAN traffic, if you picked OPT1 your OPT1 has to be plugged into WAN somehow or bridged to it or something.
-
I never setup a bridge, My wan is connected to vr2 and is working. vr2 (OP1) is working and handing out leases.
Just my vr1 (LAN) will not hand over leases. I might have to revert back to pfSense 1.2.3. If I cant figure this out tonight.
Robert