Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Could this be a bug? Radvd cannot start.

    IPv6
    2.6.0 ipv6 virtualization configuration radvd
    1
    2
    1.1k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • NightlySharkN
      NightlyShark
      last edited by

      Hi! I have a TrueNAS host, running a PfSense 2.6.0 VM (HW checks out). After completing my IPv6 config (56 prefix from ISP, LAN IFs set to track WAN and get a 64 subnet, RAs set to unmanaged) I try to start radvd from the widget and nothing happens. I then find in the logs:
      General log:

      Aug 14 01:29:15	root	90434	Bootup complete
      Aug 14 01:29:16	nginx		2022/08/14 01:29:16 [error] 57205#100583: send() failed (54: Connection reset by peer)
      Aug 14 01:35:11	php-fpm	84146	/status_services.php: The command '/usr/local/sbin/radvd -p /var/run/radvd.pid -C /var/etc/radvd.conf -m syslog' returned exit code '1', the output was '/var/etc/radvd.conf:17 error: syntax error'
      

      Routing log:

      (after reboot)
      Aug 13 23:50:37	radvd	37352	version 2.19 started
      Aug 13 23:50:37	radvd	37352	exiting, failed to read config file
      .
      .
      .
      Aug 13 23:53:10	radvd	14610	version 2.19 started
      Aug 13 23:53:10	radvd	14610	exiting, failed to read config file
      Aug 13 23:55:09	radvd	42303	version 2.19 started
      Aug 13 23:55:09	radvd	42303	warning: AdvRDNSSLifetime <= 2*MaxRtrAdvInterval would allow stale DNS servers to be deleted faster
      Aug 13 23:55:09	radvd	42303	warning: (/usr/local/etc/radvd.conf:111) AdvRDNSSLifetime <= 2*MaxRtrAdvInterval would allow stale DNS servers to be deleted faster
      Aug 13 23:55:09	radvd	42303	warning: AdvDNSSLLifetime <= 2*MaxRtrAdvInterval would allow stale DNS suffixes to be deleted faster
      Aug 13 23:55:09	radvd	42638	lo not found: Device not configured
      Aug 13 23:55:09	radvd	42638	lo not found: Device not configured
      Aug 13 23:55:19	radvd	42638	lo not found: Device not configured
      Aug 13 23:55:30	radvd	42638	lo not found: Device not configured
      Aug 13 23:55:42	radvd	42638	exiting, 1 sigterm(s) received
      Aug 13 23:55:42	radvd	42638	sending stop adverts
      Aug 13 23:55:42	radvd	42638	lo not found: Device not configured
      Aug 13 23:55:42	radvd	42638	removing /var/run/radvd.pid
      Aug 13 23:55:42	radvd	42638	returning from radvd main
      Aug 13 23:55:49	radvd	45261	version 2.19 started
      Aug 13 23:55:49	radvd	45261	exiting, failed to read config file
      Aug 13 23:58:35	radvd	60723	version 2.19 started
      Aug 13 23:58:35	radvd	60723	exiting, failed to read config file
      .
      .
      .
      Aug 14 01:35:11	radvd	85920	version 2.19 started
      Aug 14 01:35:11	radvd	85920	exiting, failed to read config file
      

      Can anyone help with this?

      1 Reply Last reply Reply Quote 0
      • NightlySharkN
        NightlyShark
        last edited by NightlyShark

        So, I found a GUI "bug". I had correctly set the prefix ID's in the "Tracked Interface" for each VLAN, but at the RA page, I mistakenly reinserted the prefix ID in the fields that are for static (full, not delegated) prefixes. Removed the static prefixes and everything now works. GUI should not let you enter static prefixes on a tracked interface, aside from fc00 or fd. And if it does, it should check if they are correct. One of the prefixes was ::1/64.

        1 Reply Last reply Reply Quote 0
        • First post
          Last post
        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.