Project

General

Profile

Actions

Bug #2477

closed

router advertisement daemon (radvd) no longer starts

Added by Johannes Ullrich over 9 years ago. Updated over 9 years ago.

Status:
Resolved
Priority:
High
Assignee:
-
Category:
DHCP (IPv6)
Target version:
Start date:
06/08/2012
Due date:
% Done:

0%

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

Description

as of today's update, radvd no longer starts. No obvious error message I can see so far, but the config file looks bad (missing interface names, only one interface even though I got multiple). The dhcpv6 server appears to be running.

from system.log:

Jun 8 14:09:54 pfsense php: /services_dhcpv6.php: The command '/usr/local/sbin/radvd -C /var/etc/radvd.conf -m syslog' returned exit code '1', the output was ''

/var/etc/radvd.conf

  1. Automatically Generated, do not edit
  2. Generated for DHCPv6 Server opt1
    interface {
    AdvSendAdvert on;
    MinRtrAdvInterval 5;
    MaxRtrAdvInterval 20;
    AdvLinkMTU 1280;
    AdvDefaultPreference medium;
    prefix 2001:470:d846:0:0:0:0:0/64 {
    DeprecatePrefix on;
    AdvOnLink on;
    AdvAutonomous on;
    AdvRouterAddr on;
    };
    route ::/0 {
    RemoveRoute on;
    };
    DNSSL localdomain { };
    };

2.1-BETA0 (amd64)
built on Thu Jun 7 16:35:54 EDT 2012
FreeBSD 8.3-RELEASE-p2

Actions #1

Updated by Johannes Ullrich over 9 years ago

just found additional logs in routing.log confirming the issue with the configuration file:

Jun 8 14:11:50 pfsense radvd28121: version 1.8.5 started
Jun 8 14:11:50 pfsense radvd28121: syntax error in /var/etc/radvd.conf, line 3: {
Jun 8 14:11:50 pfsense radvd28121: error parsing or activating the config file: /var/etc/radvd.conf
Jun 8 14:11:50 pfsense radvd28121: Exiting, failed to read config file.

manually adding the interface name will at least start radvd

Actions #2

Updated by Jim Pingle over 9 years ago

  • Status changed from New to Feedback

I believe Seth had said this was because the snapshot was missing something that should be in the next new snapshot. The snapshot server ran out of space yesterday so it couldn't upload the fixed one, and a new one should be building now or up shortly.

If this is still a problem on a snapshot dated the 8th or later, let us know and this can be reopened.

Actions #3

Updated by Seth Mos over 9 years ago

I think I may have fixed the snapshot. Otherwise please reopen.

Although I understand you file the ticket as high, we are not all full time paid developers or in the position to fix on the go.

Actions #4

Updated by Johannes Ullrich over 9 years ago

Resolved! Thanks

Although I understand you file the ticket as high, we are not all full time paid developers or in the position to fix on the go.

Sorry. any guidance on what is "high"? Will split my big QA tester paycheck with you ;-)

Actions #5

Updated by Chris Buechler over 9 years ago

That's fine Johannes, not sure of the context for that in this case, generally comments like that would be reserved for clue-deficient people who report a "bug" as "urgent" that's nothing more than them not having a clue what they're doing and just not setting up something right. :) This case is definitely legitimately high priority.

Actions #6

Updated by Jim Pingle over 9 years ago

  • Status changed from Feedback to Resolved
Actions

Also available in: Atom PDF