Project

General

Profile

Actions
Copy link

Bug #16608

open

DHCP Relay sometimes fails to start if Wireguard interface assigned.

Added by Lev Prokofev about 13 hours ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
DHCP Relay
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Default
Affected Version:
Affected Architecture:

Description

Reported for 25.11 software.

Despite the WG interface not selected as the downstream interface, the service fails to start with the following log:

/status_services.php: The command '/usr/local/sbin/dhcrelay -id mvneta0.4091 -iu tun_wg0 192.168.250.10' returned exit code '1', the output was
'Requesting: mvneta0.4091 as upstream: N downstream: Y Requesting: tun_wg0 as upstream: Y downstream: N 
Internet Systems Consortium DHCP Relay Agent 4.4.3-P1 Copyright 2004-2022 Internet Systems Consortium. 
All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Unsupported device type 248 for "tun_wg0"  
If you think you have received this message due to a bug rather than a configuration issue please read the section on 
submitting bugs on either our web page at www.isc.org or in the README file before submitting a bug.  
These pages explain the proper process and the information we find helpful for debugging.  exiting.'

The config file has the following strings:

    <dhcrelay>
        <interface>lan</interface>
        <server>192.168.250.10</server>
        <carpstatusvip>none</carpstatusvip>
        <enable></enable>
    </dhcrelay>

The relay can run after a reboot (I assume because the WG interface is formed after starting the DHCP relay)

No data to display

Actions
Copy link

Also available in: Atom PDF