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

IPv6 not working, radvd core dumping

IPv6
2
2
1.5k
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.
  • B
    bastian
    last edited by Nov 14, 2017, 12:20 PM

    Hi,

    I was trying to setup IPv6 SLAAC on my Netgate SG-3100 (running 2.4.1-RELEASE). However, client devices were not receiving any IPv6 advertisements. After quite some time of debugging I found out that the Router Advertisement Daemon (radvd) was not coming up. Trying to start it manually using the Status > Services page resulted in the following error messages in system.log:

    
    Nov 14 12:55:58 sense kernel: pid 53306 (radvd), uid 0: exited on signal 10 (core dumped)
    Nov 14 12:55:59 sense UNKNOWN[54359]: Process 53306 died: No such process; trying to remove PID file. (/var/run/radvd.pid)
    Nov 14 12:56:00 sense kernel: pid 54359 (radvd), uid 0: exited on signal 10 (core dumped)
    Nov 14 12:56:36 sense UNKNOWN[60366]: Process 54359 died: No such process; trying to remove PID file. (/var/run/radvd.pid)
    Nov 14 12:56:37 sense kernel: pid 60366 (radvd), uid 0: exited on signal 10 (core dumped)
    Nov 14 12:56:59 sense UNKNOWN[92490]: Process 60366 died: No such process; trying to remove PID file. (/var/run/radvd.pid)
    
    

    As the following output suggests, however, the syntax of the configuration file /var/etc/radvd.conf seems to be OK:

    
    /usr/local/sbin/radvd -c -C /var/etc/radvd.conf
    Syntax OK
    
    

    Starting radvd from the console with debugging enabled results in the following output:

    
    /usr/local/sbin/radvd -d 5 -p /var/run/radvd.pid -C /var/etc/radvd.conf -m stderr
    [Nov 14 13:15:01] radvd: version 1.9.1 started
    [Nov 14 13:15:01] radvd: mtu for mvneta1 is 1500
    [Nov 14 13:15:01] radvd: link layer token length for mvneta1 is 48
    [Nov 14 13:15:01] radvd: prefix length for mvneta1 is 64
    [Nov 14 13:15:01] radvd: interface definition for mvneta1 is ok
    [Nov 14 13:15:01] radvd: mvneta1: if_index 2
    [Nov 14 13:15:01] radvd: setting LinkMTU (1500) for mvneta1 is not supported
    [Nov 14 13:15:01] radvd: setting CurHopLimit (64) for mvneta1 is not supported
    [Nov 14 13:15:01] radvd: sending RA on mvneta1
    [Nov 14 13:15:01] radvd: adding prefix 2003:x:xxxx:xxxx:: to advert for mvneta1
    Bus error (core dumped)
    
    

    It seems that the radvd implementation is flawed. Please find the automatically generated configuration below:

    
    cat /var/etc/radvd.conf
    # Automatically Generated, do not edit
    # Generated for DHCPv6 Server lan
    interface mvneta1 {
    	AdvSendAdvert on;
    	MinRtrAdvInterval 5;
    	MaxRtrAdvInterval 20;
    	AdvLinkMTU 1500;
    	AdvDefaultPreference medium;
    	prefix 2003:x:xxxx:xxxx::/64 {
    		DeprecatePrefix on;
    		AdvOnLink on;
    		AdvAutonomous on;
    		AdvRouterAddr on;
    		AdvValidLifetime 86400;
    		AdvPreferredLifetime 14400;
    	};
    	route ::/0 {
    		RemoveRoute on;
    	};
    	RDNSS 2003:a:xxxx:xxx:xxx:xxxx:xxxx:xxxx { };
    	DNSSL localdomain  { };
    };
    
    

    Any recommendations?

    1 Reply Last reply Reply Quote 0
    • B
      bmeeks
      last edited by Nov 14, 2017, 12:35 PM

      This is a known issue with radvd.  The bug is fixed in the next release of pfSense (2.4.2).  It only happens on ARM hardware like the SG-3100.  Here is the bug report and documentation of the upcoming fix from the pfSense Redmine bug site:  https://redmine.pfsense.org/issues/8022#change-35066.

      Bill

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