radvd[...]: sendmsg: Permission denied

Started by gothbert, December 12, 2017, 08:32:40 PM

Previous topic - Next topic
Thank you, marjohn56, for the detailed description to go there and back again.

Currently I am off for some days. I will try this over the weekend. I will report what I managed to achieve.

Kind regards
Boris

I've now issued a PR on this, so if you want to keep up to date follow this:


https://github.com/opnsense/core/pull/2460


Use the commit number on that PR for your test as I made a few changes before I issued the PR.




OPNsense 24.7 - Qotom Q355G4 - ISP - Squirrel 1Gbps.

Team Rebellion Member

Hi,

Quote from: marjohn56 on June 12, 2018, 08:55:00 PM
If you want to try where I have got to so far, and I am not quite ready for a PR yet, but you can try it, you'll need to switch the dev stream. Once you have done that, then update. That will update the binaries as needed.

I followed the instructions. I was not able to apply commit 740bc8c99e6850473d8d9eda0a1c442fcc78c8fd, the patch was partially rejected. I thus used the patch as per your post.

I checked the "dhcpd6 and RADVD" and I also reloaded all services from the command line and did not touch anything else (no idea where to start).

The

Jun 15 19:40:14 opnsense radvd[41741]: sendmsg: Permission denied

messages continue. What bothers me is the following message:


Jun 15 19:37:57 opnsense radvd[41609]: version 1.15 started
Jun 15 19:37:57 opnsense radvd[41609]: no auto-selected prefix on interface igb1, disabling advertisements
Jun 15 19:37:57 opnsense radvd[41609]: no auto-selected prefix on interface igb2, disabling advertisements


igb1 and igb2 are my local LAN networks. I suspect that I will not get a prefix any more for the tracking interfaces igb1 and igb2. Can confirm or reject this assumption only after a reboot of my workstation from which I am currently writing this.

Any further advice?

Kind regards
Boris




Yes, at this point revert...


shell command


#opnsense-revert


or if you want to stay on the beta stream


# cd /usr/core
# opnsense upgrade


Patches should have applied without issue after switching to the dev stream.
OPNsense 24.7 - Qotom Q355G4 - ISP - Squirrel 1Gbps.

Team Rebellion Member

It's

# opnsense-revert opnsense

or

# opnsense-revert opnsense-devel

depending on the installed release type.

And it's

# cd /usr/core
# make upgrade


Cheers,
Franco

PS:

> The [...] messages continue

Martin's patches won't really change that. It's a bit unsure which version you have been running, especially with partial apply failures.

Development master branch is either better or same. :)

June 15, 2018, 08:32:39 PM #21 Last Edit: June 15, 2018, 08:37:36 PM by marjohn56
I've just switched my live system to the dhcp, I have a cool ISP that allows static or dhcp6, took a few minutes for the dhcp6 to kick in as their server gets upset sometimes with dhcp6. Now, I checked my dhcpd6 conf and that is all correct, RADVD is green and looks good too.


I need to add a quick fix to t he PR... that's what testing is for and I found an issue where you have to ensure that dhcp6d is disabled before saving the WAN as dhcp6... However, if you do do that and then start dhcp6d it works...


QUICK NOTE: Enter the start and end ranges like so


::eeee:0000:0000:0001


::eeee:ffff:ffff:ffff


You could enter the full address, but my changes will only accept the last 64 bits anyway.
OPNsense 24.7 - Qotom Q355G4 - ISP - Squirrel 1Gbps.

Team Rebellion Member

Quote from: franco on June 15, 2018, 08:30:24 PM
It's

# opnsense-revert opnsense

or

# opnsense-revert opnsense-devel

depending on the installed release type.

And it's

# cd /usr/core
# make upgrade


Cheers,
Franco


Sorry... trying to do four things at one.  ::)
OPNsense 24.7 - Qotom Q355G4 - ISP - Squirrel 1Gbps.

Team Rebellion Member

Please note the commit ID has now changed..


Always check the commit ID on the PR.  :)
OPNsense 24.7 - Qotom Q355G4 - ISP - Squirrel 1Gbps.

Team Rebellion Member

Alright, reverted to OPNsense 18.1.9. BTW, OPNSense actually did not hand out IPv6 addresses in the devel branch as per yesterday including the patch.

Coming back to the original "Permission denied" issue. How should we proceed? Should I close this topic and file an issue at Github against Captive Portal in 18.1.9?

Best regards
Boris

Did you turn off assisted in RADVD and select managed before deciding it did not hand out leases? Mine did.
OPNsense 24.7 - Qotom Q355G4 - ISP - Squirrel 1Gbps.

Team Rebellion Member

Quote from: marjohn56 on June 16, 2018, 06:22:10 PM
Did you turn off assisted in RADVD and select managed before deciding it did not hand out leases? Mine did.

I only enabled "Manual IPv6 DHCPD and RA" and did not touch any other settings. I do not know whether assisted was on or off per default.

Ahah, that would explain it. You then need to set up dhcpd6 ranges and enable it, as if it was a static system  :)


At present it's definately giving out addresses either by SLAAC or dhcpd6. If you set RADVD to managed then it will dhcpd6 only, but that's no use if you have an android device that only works with SLAAC.


What it will not do at the moment is subnets, and until my new Qotom arrives I am putting that bit on hold; should be in the next week or so.





OPNsense 24.7 - Qotom Q355G4 - ISP - Squirrel 1Gbps.

Team Rebellion Member