OPNsense Forum
Archive => 17.7 Legacy Series => Topic started by: gothbert on December 12, 2017, 08:32:40 pm
-
Hi,
I do not know since when this occurs and if it was already there before the update to 17.7.9. My routing.log gets spilled with messages. This is how the log looks like after a reboot:
Dec 12 20:05:41 opnsense rtsold: Starting dhcp6 client for interface wan(igb0)
Dec 12 20:05:45 opnsense rtsold: Starting dhcp6 client for interface wan(igb0)
Dec 12 20:05:54 opnsense radvd[12509]: version 1.15 started
Dec 12 20:07:57 opnsense radvd[12772]: sendmsg: Permission denied
Dec 12 20:08:06 opnsense radvd[12772]: sendmsg: Permission denied
Dec 12 20:08:13 opnsense radvd[12772]: sendmsg: Permission denied
Dec 12 20:08:22 opnsense radvd[12772]: sendmsg: Permission denied
Dec 12 20:08:26 opnsense radvd[12772]: sendmsg: Permission denied
Dec 12 20:08:31 opnsense radvd[12772]: sendmsg: Permission denied
Dec 12 20:08:37 opnsense radvd[12772]: sendmsg: Permission denied
Dec 12 20:08:46 opnsense radvd[12772]: sendmsg: Permission denied
Dec 12 20:08:55 opnsense radvd[12772]: sendmsg: Permission denied
Dec 12 20:09:01 opnsense radvd[12772]: sendmsg: Permission denied
Dec 12 20:09:09 opnsense radvd[12772]: sendmsg: Permission denied
Dec 12 20:09:16 opnsense radvd[12772]: sendmsg: Permission denied
Dec 12 20:09:19 opnsense radvd[12772]: sendmsg: Permission denied
Dec 12 20:09:24 opnsense radvd[12772]: sendmsg: Permission denied
Dec 12 20:09:30 opnsense radvd[12772]: sendmsg: Permission denied
Dec 12 20:09:32 opnsense radvd[12772]: Exiting, sigterm or sigint received.
Dec 12 20:09:32 opnsense radvd[12772]: sending stop adverts
Dec 12 20:09:32 opnsense radvd[12772]: sendmsg: Permission denied
Dec 12 20:09:32 opnsense radvd[12772]: removing /var/run/radvd.pid
Dec 12 20:09:36 opnsense rtsold: Starting dhcp6 client for interface wan(igb0)
Dec 12 20:09:40 opnsense radvd[64346]: version 1.15 started
Dec 12 20:09:40 opnsense radvd[64868]: sendmsg: Permission denied
Dec 12 20:09:40 opnsense radvd[64868]: sendmsg: Can't assign requested address
Dec 12 20:09:40 opnsense radvd[64868]: Exiting, sigterm or sigint received.
Dec 12 20:09:40 opnsense radvd[64868]: sending stop adverts
Dec 12 20:09:40 opnsense radvd[64868]: sendmsg: Can't assign requested address
Dec 12 20:09:40 opnsense radvd[64868]: sendmsg: Can't assign requested address
Dec 12 20:09:40 opnsense radvd[64868]: removing /var/run/radvd.pid
Dec 12 20:09:41 opnsense radvd[78492]: version 1.15 started
Dec 12 20:09:41 opnsense radvd[78845]: sendmsg: Can't assign requested address
Dec 12 20:09:41 opnsense radvd[78845]: sendmsg: Can't assign requested address
Dec 12 20:09:41 opnsense rtsold: Starting dhcp6 client for interface wan(igb0)
Dec 12 20:09:45 opnsense radvd[78845]: Exiting, sigterm or sigint received.
Dec 12 20:09:45 opnsense radvd[78845]: sending stop adverts
Dec 12 20:09:45 opnsense radvd[78845]: sendmsg: Permission denied
Dec 12 20:09:45 opnsense radvd[78845]: removing /var/run/radvd.pid
Dec 12 20:09:45 opnsense radvd[96804]: version 1.15 started
Dec 12 20:09:45 opnsense radvd[98771]: sendmsg: Permission denied
Dec 12 20:09:46 opnsense radvd[98771]: Exiting, sigterm or sigint received.
Dec 12 20:09:46 opnsense radvd[98771]: sending stop adverts
Dec 12 20:09:46 opnsense radvd[98771]: sendmsg: Permission denied
Dec 12 20:09:46 opnsense radvd[98771]: sendmsg: Can't assign requested address
Dec 12 20:09:46 opnsense radvd[98771]: removing /var/run/radvd.pid
Dec 12 20:09:46 opnsense radvd[25046]: version 1.15 started
Dec 12 20:09:46 opnsense radvd[25054]: sendmsg: Permission denied
Dec 12 20:09:46 opnsense radvd[25054]: sendmsg: Can't assign requested address
Dec 12 20:09:46 opnsense radvd[25054]: Exiting, sigterm or sigint received.
Dec 12 20:09:46 opnsense radvd[25054]: sending stop adverts
Dec 12 20:09:46 opnsense radvd[25054]: sendmsg: Can't assign requested address
Dec 12 20:09:46 opnsense radvd[25054]: sendmsg: Can't assign requested address
Dec 12 20:09:46 opnsense radvd[25054]: removing /var/run/radvd.pid
Dec 12 20:09:46 opnsense radvd[36299]: version 1.15 started
Dec 12 20:09:46 opnsense radvd[36965]: sendmsg: Can't assign requested address
Dec 12 20:09:46 opnsense radvd[36965]: sendmsg: Can't assign requested address
Dec 12 20:09:46 opnsense radvd[36965]: Exiting, sigterm or sigint received.
Dec 12 20:09:46 opnsense radvd[36965]: sending stop adverts
Dec 12 20:09:46 opnsense radvd[36965]: sendmsg: Can't assign requested address
Dec 12 20:09:46 opnsense radvd[36965]: sendmsg: Can't assign requested address
Dec 12 20:09:46 opnsense radvd[36965]: removing /var/run/radvd.pid
Dec 12 20:09:47 opnsense rtsold: Starting dhcp6 client for interface wan(igb0)
Dec 12 20:09:48 opnsense radvd[69684]: version 1.15 started
Dec 12 20:09:48 opnsense radvd[69906]: sendmsg: Permission denied
Dec 12 20:09:48 opnsense radvd[69906]: sendmsg: Can't assign requested address
Dec 12 20:09:48 opnsense radvd[69906]: Exiting, sigterm or sigint received.
Dec 12 20:09:48 opnsense radvd[69906]: sending stop adverts
Dec 12 20:09:48 opnsense radvd[69906]: sendmsg: Can't assign requested address
Dec 12 20:09:48 opnsense radvd[69906]: sendmsg: Can't assign requested address
Dec 12 20:09:48 opnsense radvd[69906]: removing /var/run/radvd.pid
Dec 12 20:09:48 opnsense radvd[77485]: version 1.15 started
Dec 12 20:09:48 opnsense radvd[78132]: sendmsg: Can't assign requested address
Dec 12 20:09:48 opnsense radvd[78132]: sendmsg: Can't assign requested address
Dec 12 20:09:48 opnsense rtsold: Starting dhcp6 client for interface wan(igb0)
Dec 12 20:09:53 opnsense radvd[78132]: Exiting, sigterm or sigint received.
Dec 12 20:09:53 opnsense radvd[78132]: sending stop adverts
Dec 12 20:09:53 opnsense radvd[78132]: sendmsg: Permission denied
Dec 12 20:09:53 opnsense radvd[78132]: removing /var/run/radvd.pid
Dec 12 20:09:54 opnsense radvd[63529]: version 1.15 started
Dec 12 20:09:54 opnsense radvd[64432]: sendmsg: Permission denied
Dec 12 20:10:04 opnsense radvd[64432]: sendmsg: Permission denied
Dec 12 20:10:08 opnsense radvd[64432]: sendmsg: Permission denied
Dec 12 20:10:16 opnsense radvd[64432]: sendmsg: Permission denied
Dec 12 20:10:21 opnsense radvd[64432]: sendmsg: Permission denied
Dec 12 20:10:27 opnsense radvd[64432]: sendmsg: Permission denied
Dec 12 20:10:31 opnsense radvd[64432]: sendmsg: Permission denied
Dec 12 20:10:40 opnsense radvd[64432]: sendmsg: Permission denied
Dec 12 20:10:48 opnsense radvd[64432]: sendmsg: Permission denied
Dec 12 20:10:56 opnsense radvd[64432]: sendmsg: Permission denied
Dec 12 20:11:01 opnsense radvd[64432]: sendmsg: Permission denied
Dec 12 20:11:10 opnsense radvd[64432]: sendmsg: Permission denied
Dec 12 20:11:16 opnsense radvd[64432]: sendmsg: Permission denied
Dec 12 20:11:20 opnsense radvd[64432]: sendmsg: Permission denied
Dec 12 20:11:29 opnsense radvd[64432]: sendmsg: Permission denied
Dec 12 20:11:36 opnsense radvd[64432]: sendmsg: Permission denied
Dec 12 20:11:45 opnsense radvd[64432]: sendmsg: Permission denied
And from there on the message repeats all over every 4 to 6 seconds. I did not touch anything in the first 10 minutes after the reboot to let the system settle. IPv6 works well.
Anything I can do to track the cause?
Best regards,
Boris
-
Hi Boris,
Seems that an interface disappears and comes back up, but radvd isn't restarted.
Where are you using interface tracking? Do you have manual router advertisements set up on other interfaces as well?
Cheers,
Franco
-
Hi Franco,
this is the interface setup:
interface WAN, igb0 gets IPv6 from Fritzbox
interface HOME, igb1, IPv6 tracks interface
interface LET, igb2, IPv6 tracks interface
interface DMZ, igb3, -
OpenVPN, ovpbc1, -
Regards,
Boris
-
Hi,
this issue is still present in OPNsense 18.1.9-amd64. Anything I can do about it?
Best regards
Boris
-
Can I ask what hardware you are using?
-
Can I ask what hardware you are using?
It is a Supermicro X11SBA-LN4F board with 4 Intel i210 Ethernet Controllers on board. It sits behind a Fritz!Box 6490 Cable that connects me to the internet via cable modem.
-
Checking back through the archives there seems to be several users running these boards, no-one else has reported this issue.
Have you tried a clean install and configuring from scratch?
I know I have had problems in the past where a config has got corrupted in some way and just copying it from an old installation to a new one did not help. A clean install and a new config fixed my issues. I know it's a pain, but that would be the first thing I'd try.
-
I know I have had problems in the past where a config has got corrupted in some way and just copying it from an old installation to a new one did not help. A clean install and a new config fixed my issues. I know it's a pain, but that would be the first thing I'd try.
That appeared such a painful workaround for me, given alone the large amount of hostnames configured in unbound, that I continued to search the internets and found this: https://forum.netgate.com/topic/58316/no-dhcpv6-on-internal-net-radvd-issue-sendmsg-permission-denied (https://forum.netgate.com/topic/58316/no-dhcpv6-on-internal-net-radvd-issue-sendmsg-permission-denied)
With some further trial-and-error work, I found out that the message appears if and only if the only configured zone in the captive portal is active. Zone turned off: no message, zone turned on: message.
Further inspired by the cited article, I disabled all firewall rules on the local net the captive portal was assigned to. But this did not make the message disappear. DHCPv6 is off. Disabling DHCPv4 on this local net did nothing to the message. Neither does removing this local net from forward proxying through Squid.
Maybe this gives some ideas where to further search for the culprit.
Best regards,
Boris
-
Hello,
Not sure if related, but on PPPoE radvd isn't reconfigured when "Use IPv4 connectivity" is set and DHCPv6 or SLAAC is used as the WAN IPv6 config type.
https://github.com/opnsense/core/commit/baf292e91a
Cheers,
Franco
-
As soon as we've finished with dhclient/dhcp6c stuff I'll be pushing on with the ability to edit dhcpd6 and radvd when in that mode, that may fix this issue as you'll be able to configure it.
-
Is there any issue on GitHub I can subscribe to and at some stage contribute to as a tester if needed?
-
There's only my own local code at present, there will be a PR later this week with any luck.
-
It could be https://github.com/opnsense/core/issues/2314 ?
Cheers,
Franco
-
subscribed
-
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.
Once that is complete you'll need to update the core by doing this, open a shell and issue the following commands:
# opnsense-code core
# cd /usr/core
# make upgrade
That will bring you bang up to date with where the code is at for 18.7.b*
Next, you'll need to patch my commit.. do this by issuing the following command.
# opnsense-patch -a marjohn56 40fb7e8
Now, you'll need to enable the option to manually adjust dhcpd6 and RADVD, do this by going to system->Settings->General and enable “Manual IPv6 DHCPD and RA”
Have a play, there is still work to be done, for example if the prefix changes then the config needs to be re-written and dhcpd restarted.
If it doesn't work for you or you have issues, then issue the same command
# opnsense-patch -a marjohn56 40fb7e8
to revert it. If that fails then a
# cd /usr/core
# make upgrade
will restore things to original.
Good Luck, and let me know how you get on.
-
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 (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.
-
Hi,
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.
-
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. :)
-
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.
-
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. ::)
-
Please note the commit ID has now changed..
Always check the commit ID on the PR. :)
-
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.
-
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.