Bug #2936
closed
dhcrelay does not start
0%
Description
With pfsense 2.1-BETA1, dhcrelay fails to start with error :
/services_dhcp_relay.php: The command '/usr/local/sbin/dhcrelay -i bridge1 -i lagg1 -i lo0 -a -m replace 130.120.36.77 130.120.224.121' returned exit code '1', the output was 'Internet Systems Consortium DHCP Relay Agent 4.2.4-P2 Copyright 2004-2012 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Unsupported device type 24 for "lo0" If you did not get this software from ftp.isc.org, please get the latest from ftp.isc.org and install that before requesting help. If you did get this software from ftp.isc.org and have not yet read the README, please read it before requesting help. If you intend to request help from the dhcp-server@isc.org mailing list, please read the section on the README about submitting bug reports and requests for help. Please do not under any circumstances send requests for help directly to the authors of this software - please send them to the appropriate mailing list as described in the README file.
only lagg1 and bridge1 are configured for dhcrelay.
Thanks
Christophe
Updated by Jim Pingle about 12 years ago
- Status changed from New to Rejected
Not enough information here. Please start a thread on the forum to discuss it, but it's most likely a configuration error. The only way lo0 would make it into that list is if you had selected it somehow, or one of the other automatic selections chose it, which could happen if things were not configured properly. We'd need to see a full copy of the configuration file to determine the issue, but it's a discussion best kept in the forum until a cause has been found.
Updated by christophe segui about 12 years ago
How can i even select lo0, loopback interface is not available for dhcrelay !!!!
Updated by Jim Pingle about 12 years ago
As I mentioned, there are other ways that it could happen that are also misconfigurations. We need to see the full config, and have it discussed outside the ticket system, before a bug report is accepted. The logs are not enough information to go on. It tells us what happened, but not why or how, which would be in the config and other info that can come out of a discussion in a more appropriate place.