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

brick41

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.

Veni

@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.

firestar7

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

Firestar.

cmb

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).

SomeGuyInSandy

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!

brick41

@SomeGuyInSandy:

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

How do I run a save on my NICs?

pigbrother

@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

Supermule

It worked!

Thanks guys!

Evad

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....

thinkofit

still there on 2.2.6

http://lists.pfsense.org/pipermail/list/2016-January/009511.html

–
antonio

thinkofit

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

fixed in 2.3
–
antonio