Firmware from 1.2.1 to 1.3
-
Installing via "firmware update" page Firmware from 1.2.1 to 1.3 pfSense-Full-Update-1.3-ALPHA-ALPHA-20080804-0137
I get on the "Services" page…
Warning: file_get_contents(/var/run/openvpn_server0.pid): failed to open stream: No such file or directory in /etc/inc/service-utils.inc on line 146 Warning: file_get_contents(/var/run/openvpn_client0.pid): failed to open stream: No such file or directory in /etc/inc/service-utils.inc on line 146
and no DHCP service running...
Aug 3 23:32:56 dhcpd: Configuration file errors encountered -- exiting
Aug 3 23:32:56 dhcpd: Configuration file errors encountered -- exiting
Aug 3 23:32:56 dhcpd: ^
Aug 3 23:32:56 dhcpd: ^
Aug 3 23:32:56 dhcpd: option host-name Access Point;
Aug 3 23:32:56 dhcpd: option host-name Access Point;
Aug 3 23:32:56 dhcpd: /var/dhcpd/etc/dhcpd.conf line 84: semicolon expected.
Aug 3 23:32:56 dhcpd: /var/dhcpd/etc/dhcpd.conf line 84: semicolon expected.
Aug 3 23:32:56 dhcpd: ^
Aug 3 23:32:56 dhcpd: ^
Aug 3 23:32:56 dhcpd: option host-name Voipo ATA;
Aug 3 23:32:56 dhcpd: option host-name Voipo ATA;
Aug 3 23:32:56 dhcpd: /var/dhcpd/etc/dhcpd.conf line 29: semicolon expected.
Aug 3 23:32:56 dhcpd: /var/dhcpd/etc/dhcpd.conf line 29: semicolon expected.
Aug 3 23:32:56 dhcpd: For info, please visit http://www.isc.org/sw/dhcp/
Aug 3 23:32:56 dhcpd: All rights reserved.
Aug 3 23:32:56 dhcpd: Copyright 2004-2006 Internet Systems Consortium.
Aug 3 23:32:56 dhcpd: Internet Systems Consortium DHCP Server V3.0.5edit= version date added.
-
dhcpd host names cannot contain spaces. did that just start occurring after upgrading to 1.3?
OpenVPN is currently a work in progress and has a number of issues.
-
@cmb:
dhcpd host names cannot contain spaces. did that just start occurring after upgrading to 1.3?
OpenVPN is currently a work in progress and has a number of issues.
Yes only after an attempt to update firmware to 1.3. I have yet to try a fresh install for 1.3
Ill fix those two items and try again…
:)
-
We must have stripped out spaces automatically in 1.2 and don't in 1.3, that never would have worked. ticket opened, thanks for the report.
-
No "stupid mistake autofix" coding completed yet eh?
Wonder what other network issues I caused myself with those errors… ::)
Thanks! ;D
