Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 0 replies
  • Subscribers 3 subscribers
  • Views 2248 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

IPv6 watchdog causing CPU spikes

Ben

so the IPv6 watchdog keeps giving me headaches:

i am running a Site2Site SSL over IPv6 connection since 9.4 beta and now getting issue with CPU beeing occupied by ipv6 watchdog, issue will be resolved by disabling and reenabling ipv6. it seems that just before the spike that my ISP resets my connection (or at least does something with their routing)

overall one might think it would be best to ditch IPv6.

funny thing is that IPv6 Log stops right before the CPU spikes happens. i dont have a single byte in my IPv6 log for April 7th. Log resumes when i dis- and reenabled ipv6 on april 8th. This is what my log says in the last entrys.

2016:04:06-17:20:47 utm radvd[7465]: resuming normal operation
2016:04:06-17:20:49 utm ipv6_watchdog[4398]: Start of monitoring interface ppp0 (18)
2016:04:06-17:20:49 utm ipv6_watchdog[4398]: Installing default route via fe80::f2f7:55ff:fe55:f300 (18)
2016:04:06-17:20:49 utm ipv6_watchdog[4398]: Installing address XXXX:XXXX:200:16:cee:e5e8:2e0d:f0f7/64 (18)
2016:04:06-17:20:49 utm ipv6_watchdog[4398]: JSON "ppp0", "unknown", "up", { "address6": "XXXX:XXXX:200:16:cee:e5e8:2e0d:f0f7", "netmask6": "64", "network6":"1" }
2016:04:06-17:20:50 utm ipv6_watchdog[4398]: Interface eth4 (6) changed RA flags: NONE -> SENT,RCVD,OTHER,MANAGED,READY
2016:04:06-17:20:50 utm ipv6_watchdog[4398]: Interface eth4 (6) changed type to DHCPv6 with Prefix Delegation
2016:04:06-17:20:50 utm ipv6_watchdog[4398]: Interface ppp0 (18) changed RA flags: NONE -> SENT,RCVD,OTHER,MANAGED,READY
2016:04:06-17:20:50 utm ipv6_watchdog[4398]: Interface ppp0 (18) changed type to DHCPv6 with Prefix Delegation
2016:04:06-17:20:50 utm ipv6_watchdog[4398]: JSON "ppp0", "unknown", "up", { "gateway6": "fe80::f2f7:55ff:fe55:f300", "network6":"1"}
2016:04:06-17:21:22 utm radvd[7465]: attempting to reread config file
2016:04:06-17:21:22 utm radvd[7465]: resuming normal operation
2016:04:06-17:21:25 utm radvd[7465]: attempting to reread config file
2016:04:06-17:21:25 utm radvd[7465]: resuming normal operation
2016:04:06-17:21:39 utm radvd[7465]: attempting to reread config file
2016:04:06-17:21:39 utm radvd[7465]: resuming normal operation
2016:04:06-17:21:39 utm radvd[7465]: attempting to reread config file
2016:04:06-17:21:39 utm radvd[7465]: resuming normal operation
2016:04:06-17:21:45 utm radvd[7465]: attempting to reread config file
2016:04:06-17:21:45 utm radvd[7465]: resuming normal operation
2016:04:06-17:21:50 utm radvd[7465]: attempting to reread config file
2016:04:06-17:21:50 utm radvd[7465]: resuming normal operation
2016:04:06-17:21:53 utm radvd[7465]: attempting to reread config file
2016:04:06-17:21:53 utm radvd[7465]: resuming normal operation
2016:04:06-17:21:53 utm radvd[7465]: attempting to reread config file
2016:04:06-17:21:53 utm radvd[7465]: resuming normal operation
2016:04:06-17:22:53 utm radvd[7465]: attempting to reread config file
2016:04:06-17:22:53 utm radvd[7465]: resuming normal operation
2016:04:06-17:23:05 utm radvd[7465]: attempting to reread config file
2016:04:06-17:23:05 utm radvd[7465]: resuming normal operation
2016:04:06-17:23:18 utm radvd[7465]: attempting to reread config file
2016:04:06-17:23:18 utm radvd[7465]: resuming normal operation
2016:04:06-17:23:22 utm radvd[7465]: attempting to reread config file
2016:04:06-17:23:22 utm radvd[7465]: resuming normal operation

funny though IPv6 Site2Site seems to still work but getting crazy connects/disconnects

2016:04:06-19:39:12 utm openvpn[4922]: MANAGEMENT: Client disconnected
2016:04:06-19:39:12 utm openvpn[7073]: MANAGEMENT: Client disconnected
2016:04:06-19:54:02 utm openvpn[4922]: MANAGEMENT: Client connected from /var/run/openvpn_mgmt_REF_SslCliUtmPhpfrIpv6
2016:04:06-19:54:02 utm openvpn[4922]: MANAGEMENT: CMD 'state'
2016:04:06-19:54:02 utm openvpn[7073]: MANAGEMENT: Client connected from /var/run/openvpn_mgmt
2016:04:06-19:54:02 utm openvpn[7073]: MANAGEMENT: CMD 'status -1'
2016:04:06-19:54:02 utm openvpn[4922]: MANAGEMENT: CMD 'state'
2016:04:06-19:54:02 utm openvpn[7073]: MANAGEMENT: CMD 'status -1'
2016:04:06-19:54:12 utm openvpn[4922]: MANAGEMENT: Client disconnected
2016:04:06-19:54:12 utm openvpn[7073]: MANAGEMENT: Client disconnected
2016:04:06-20:09:02 utm openvpn[4922]: MANAGEMENT: Client connected from /var/run/openvpn_mgmt_REF_SslCliUtmPhpfrIpv6
2016:04:06-20:09:02 utm openvpn[4922]: MANAGEMENT: CMD 'state'
2016:04:06-20:09:02 utm openvpn[7073]: MANAGEMENT: Client connected from /var/run/openvpn_mgmt
2016:04:06-20:09:02 utm openvpn[7073]: MANAGEMENT: CMD 'status -1'
2016:04:06-20:09:02 utm openvpn[4922]: MANAGEMENT: CMD 'state'
2016:04:06-20:09:02 utm openvpn[7073]: MANAGEMENT: CMD 'status -1'
2016:04:06-20:09:12 utm openvpn[4922]: MANAGEMENT: Client disconnected
2016:04:06-20:09:12 utm openvpn[7073]: MANAGEMENT: Client disconnected
2016:04:06-20:24:02 utm openvpn[4922]: MANAGEMENT: Client connected from /var/run/openvpn_mgmt_REF_SslCliUtmPhpfrIpv6
2016:04:06-20:24:02 utm openvpn[4922]: MANAGEMENT: CMD 'state'
2016:04:06-20:24:02 utm openvpn[7073]: MANAGEMENT: Client connected from /var/run/openvpn_mgmt
2016:04:06-20:24:02 utm openvpn[7073]: MANAGEMENT: CMD 'status -1'
2016:04:06-20:24:03 utm openvpn[4922]: MANAGEMENT: CMD 'state'
2016:04:06-20:24:03 utm openvpn[7073]: MANAGEMENT: CMD 'status -1'
2016:04:06-20:24:13 utm openvpn[4922]: MANAGEMENT: Client disconnected
2016:04:06-20:24:13 utm openvpn[7073]: MANAGEMENT: Client disconnected
2016:04:06-20:39:01 utm openvpn[4922]: MANAGEMENT: Client connected from /var/run/openvpn_mgmt_REF_SslCliUtmPhpfrIpv6


This thread was automatically locked due to age.
Unfiltered HTML