OPNsense Forum
Archive => 18.1 Legacy Series => Topic started by: opnfwb on May 10, 2018, 03:20:08 am
-
Hello, I'm here to see if any other users are also seeing similar activity. I'm using OPNsense X64 OpenSSL 18.1.7_1 with an IPV6 prefix being assigned through my WAN (using Track Interface for LAN DHCP6). I have not previously checked logs on prior versions of OPNsense, and I have not made any configuration changes for months. So I don't suspect a change on my end.
If I check System/Routes/Log File, I see the following data:
May 9 20:08:52 rtsold[22044]: <rtsol_check_timer> there is no timer
May 9 20:08:52 rtsold[22044]: <rtsock_input> rtmsg type 1, len=240
May 9 20:08:49 rtsold[22044]: <rtsol_check_timer> there is no timer
May 9 20:08:49 rtsold[22044]: <rtsol_input> received RA from fe80::1:1 on an unexpected IF(igb3)
May 9 20:08:43 rtsold[22044]: <rtsol_check_timer> there is no timer
May 9 20:08:43 rtsold[22044]: <rtsol_input> received RA from fe80::1:1 on an unexpected IF(igb3)
May 9 20:08:43 rtsold[22044]: <rtsol_check_timer> there is no timer
May 9 20:08:43 rtsold[22044]: <make_rsid> rsid = [igb0:slaac]
May 9 20:08:43 rtsold[22044]: <rtsol_input> ndo->nd_opt_len = 4
May 9 20:08:43 rtsold[22044]: <rtsol_input> ndo->nd_opt_type = 3
May 9 20:08:43 rtsold[22044]: <rtsol_input> ndo = 0x6082a0
May 9 20:08:43 rtsold[22044]: <rtsol_input> ndo->nd_opt_len = 4
May 9 20:08:43 rtsold[22044]: <rtsol_input> ndo->nd_opt_type = 3
May 9 20:08:43 rtsold[22044]: <rtsol_input> ndo = 0x608280
May 9 20:08:43 rtsold[22044]: <rtsol_input> ndo->nd_opt_len = 4
May 9 20:08:43 rtsold[22044]: <rtsol_input> ndo->nd_opt_type = 3
May 9 20:08:43 rtsold[22044]: <rtsol_input> ndo = 0x608260
May 9 20:08:43 rtsold[22044]: <rtsol_input> ndo->nd_opt_len = 4
May 9 20:08:43 rtsold[22044]: <rtsol_input> ndo->nd_opt_type = 3
May 9 20:08:43 rtsold[22044]: <rtsol_input> ndo = 0x608240
May 9 20:08:43 rtsold[22044]: <rtsol_input> ndo->nd_opt_len = 1
May 9 20:08:43 rtsold[22044]: <rtsol_input> ndo->nd_opt_type = 5
May 9 20:08:43 rtsold[22044]: <rtsol_input> ndo = 0x608238
May 9 20:08:43 rtsold[22044]: <rtsol_input> ndo->nd_opt_len = 1
May 9 20:08:43 rtsold[22044]: <rtsol_input> ndo->nd_opt_type = 1
May 9 20:08:43 rtsold[22044]: <rtsol_input> ndo = 0x608230
May 9 20:08:43 rtsold[22044]: <rtsol_input> Processing RA
May 9 20:08:43 rtsold[22044]: <rtsol_input> received RA from fe80::217:10ff:fe8b:9403 on igb0, state is 0
May 9 20:08:43 rtsold[22044]: <rtsol_check_timer> there is no timer
May 9 20:08:43 rtsold[22044]: <rtsock_input> rtmsg type 1, len=240
May 9 20:08:35 rtsold[22044]: <rtsol_check_timer> there is no timer
This data literally fills the log file, it's constantly updating. Is this a normal or intended function? Most of these messages seem related to Router Advertisements as a function of IPV6 but, I'm not sure if this is common or not? I'm hoping to get input from some other users here to see if they are seeing similar data in their logfile.
-
Just wanted to follow up on this. I did some more testing and I think I've got the cause of these log messages somewhat figured out.
First, the constant log spamming is caused by my setting the "Enable Debug" option in Interfaces/WAN. Once I unchecked this option, the log spam stopped.
However, I was much more interested in why this was happening. It seems as though OPNsense is not using the delegated prefix from the ISP as the "default" route. Instead, OPNsense is using a link local FE80 IPV6 address for the WAN gateway as the default route. It is still routing my ISP-provided delegated prefix without issues, and internal LAN clients also pull IPV6 addresses from the ISP delegated prefix just fine. So this doesn't appear to be impacting LAN clients but it is enough to cause a constant router advertisement log spam when using the "debug" feature.
I'm not sure if this is intended function for OPNsense or if it's something with how my ISP is providing the IPV6 addresses to my OPNsense box.