Upgraded from 2.1 to 2.1.1, radvd floods log with sendmsg: Operation not permitt



  • Hello everyone  :D.

    Upgraded yesterday from 2.1-RELASE to 2.1.1-RELEASE.
    Running as i386 on a ESXi 5.0 U1.
    Open-VM-Tools from "Packages".
    One LAN and a WAN over a Huawei 3G modem.
    Only IPv4. Disabled IPv6.

    Right away after upgrade my syslog got flooded  :P with:
    +–--------------------------------------------------------------------------------------------------------------------------------------------------------------------+
    | message                                                                                                                                                              |
    +----------------------------------------------------------------------------------------------------------------------------------------------------------------------+
    | Apr  6 01:37:06 radvd[34100]: sendmsg: Operation not permitted                                                                                                      |
    | Apr  6 01:37:14 radvd[34100]: sendmsg: Operation not permitted                                                                                                      |
    | Apr  6 01:37:18 radvd[34100]: sendmsg: Operation not permitted                                                                                                      |
    | Apr  6 01:37:28 radvd[34100]: sendmsg: Operation not permitted                                                                                                      |
    | Apr  6 01:37:34 radvd[34100]: sendmsg: Operation not permitted                                                                                                      |
    | Apr  6 01:37:41 radvd[34100]: sendmsg: Operation not permitted                                                                                                      |
    | Apr  6 01:37:44 radvd[34100]: sendmsg: Operation not permitted                                                                                                      |
    | Apr  6 01:37:52 radvd[34100]: sendmsg: Operation not permitted                                                                                                      |
    +–--------------------------------------------------------------------------------------------------------------------------------------------------------------------+

    It's like every 3-10 seconds that message gets logged.
    Tried today to reboot. No difference.

    Reverted to backup(2.1-RELEASE) taken by the upgrade program at the point before the upgrade yesterday.
    Now i do not see any radvd: sendmsg: Operation not permitted in the log.

    What can i do to use 2.1.1 but fix the problem with the message above?

    Thanks in advance for any hints and please do ask if there is more information needed.

    P.s: I put this in the IPv6 place because google told me that this radvd is a IPv6 Router advertisment Daemon.
    Please move this to the correct forum part if it's not in the right place.

    Sincerely
    Veni



  • I encountered this problem is due to this miss-configured auto generated file /var/etc/radvd.conf. I have IPv6 disabled in my network so when the file is generated it should terminate radvd but in some cases it seems it doesn't terminate and continues to run with a bad config which spams syslog. I was able to solve this problem with a reboot of the router which lead to a proper termination of radvd. The other option would be to kill it from the terminal or over ssh if you don't use IPv6.

    The only other thing I can see leading to this problem is a miss-configuration of an IPv6 setting that is used to generate the file. I am not familiar with the script that generates the radvd.conf so someone else may be able to shed more light on this then I.



  • Hi deadnull.

    Thanks for the hint. I'll be looking in to this this weekend or maybe already today.
    Sounds like something maybe wrong in the conf file at my end.
    But I really feel that pfSense should not start this daemon at all in my case.

    The response "Operation not permitted" sounds to me in this case that the radvd is trying to use a IPv6 but my pfSense has none, thus it will be denied.



  • This is what i found in /var/etc/radvd.conf:

    # Automatically Generated, do not edit
    # Generated config for  delegation from wan on lan
    interface em0 {
    	AdvSendAdvert on;
    	MinRtrAdvInterval 3;
    	MaxRtrAdvInterval 10;
    	AdvLinkMTU 1500;
    	AdvOtherConfigFlag on;
    		prefix ::/64 {
    		AdvOnLink on;
    		AdvAutonomous on;
    		AdvRouterAddr on;
    	};
    	DNSSL local.domain { };
    };
    

    I've checked my LAN and WAN settings.
    LAN is em0 and IPv6 Configuration Type is set to None.
    WAN is PPP0 and IPv6 Configuration Type is set to None.

    Killing radvd fixes the issue but it comes back on after reboot.

    I'll later today or tomorrow give it a try with a fresh install instead of a upgrade.



  • @Veni:

    I'll later today or tomorrow give it a try with a fresh install instead of a upgrade.

    I have a new pfsense 2.1.2 installation from 2014-04-10 amd64 and I have the same problem and same radvd.conf. I did ifconfig -a and I can see IPv6 addresses even though I don't use IPv6. Did you check your ifconfig? How can I disable IPv6 and is there a persistent way to fix this problem?

    I did find this way to disallow IPv6 but it only blocks packets not a full IPv6 disable.
    System > Advanced > Networking > Allow IPv6

    Really I wouldn't mind leaving it alone except that it's flooding the routing log. I don't really use that log but still.



  • @brick41:

    Did you check your ifconfig?

    Have not yet run a fresh install due to that I forgot it because i killed radvd :)(no more flooding my syslog server).

    But now I checked with ifconfig -a and both em0 and ppp0 have a inet6 address each, but they are almost identical with the exception of the end part of them(one ends with em0 and the other ends with ppp0), and I'm not that familiar with IPv6. So it sounds to me that my assumption earlier was incorrect about radvd trying to bind to a IPv6 address but not able to find one and so the error was triggered.

    I'll do it the pragmatic way and erase radvd from the system :D. That way it will be consistent over future reboots, but will probably return after a upgrade if it's not fixed.



  • The message disappear, if you make "save" on all interfaces.

    Firestar.



  • The log in the subject is what will happen when you have IPv6 disabled (so all v6 traffic is blocked, that's where the "Operation not permitted" comes from), but radvd is trying to run for some reason (likely because you have v6 configured on one of your interfaces).



  • Referencing "firestar7"s tip, I ran a save on each of my NICs and got this:

    radvd[34652]: removing /var/run/radvd.pid
    May 13 20:29:45 radvd[34652]: sending stop adverts
    May 13 20:29:45 radvd[34652]: Exiting, sigterm or sigint received.

    The offending messages have stopped! Excellent!



  • @SomeGuyInSandy:

    Referencing "firestar7"s tip, I ran a save on each of my NICs

    How do I run a save on my NICs?



  • @brick41:

    @SomeGuyInSandy:

    Referencing "firestar7"s tip, I ran a save on each of my NICs

    How do I run a save on my NICs?

    Menu-Interfaces.

    Open each interface, choose\check IPv6 Configuration Type=none and press save button


  • Banned

    It worked!

    Thanks guys!



  • Today I upgraded 2 systems from 2.2 to 2.2.4. Both 32bit. One of them flooded the routing log with
    Aug 23 19:41:39 radvd[22760]: sendmsg: Operation not permitted
    Aug 23 19:41:34 radvd[22760]: sendmsg: Operation not permitted
    Aug 23 19:41:29 radvd[22760]: sendmsg: Operation not permitted

    Using only 2 interfaces on the affected machine and both have 'none' selected for IPv6 Configuration Type

    Doing a Save on each interface as suggested above solved the problem.
    Last few lines were:
    Aug 23 19:44:48 radvd[23962]: removing /var/run/radvd.pid
    Aug 23 19:44:48 radvd[23962]: sendmsg: Operation not permitted
    Aug 23 19:44:48 radvd[23962]: sending stop adverts
    Aug 23 19:44:48 radvd[23962]: Exiting, sigterm or sigint received.

    Glad I found this thread…

    Thanks....





  • filed a bug: https://redmine.pfsense.org/issues/5812

    fixed in 2.3

    antonio


Log in to reply