Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - lazydaze

#1
General Discussion / Re: 2 Problems: IPsec and IPv6
August 26, 2015, 03:18:08 AM
Cool, I'll be looking forward to 15.7.10 and future releases!

Thanks for all the help and explaining PowerD.  ;D
#2
General Discussion / Re: 2 Problems: IPsec and IPv6
August 25, 2015, 03:19:47 AM
Rebooted and IPv6 was down. I rand that command...

Output read: OK

Tested and got 10/10.

Rebooted again and IPv6 went down.

On another note, I started to use PowerD on Adaptive and after about 2 hours it will put serious load on the CPU. 1.01, 1.14, 1.03... and the graph will read at 51%. I turn off PowerD and it goes back to a normal range.
Kinda weird, just thought I'd bring it up.
#3
General Discussion / Re: 2 Problems: IPsec and IPv6
August 22, 2015, 07:11:41 PM
The error I get after a restart is:
opnsense: /usr/local/etc/rc.newwanipv6: rc.newwanipv6: Failed to update WAN[wan] IPv6, restarting...

After I restart I have to go to my WAN interface and turn off DHCP6 then turn it back on for IPv6 to work.

It then works perfectly fine. I get 10/10 on Comcast IPv6 test site.

I used the site, which you linked on twitter, to do my IPv6 setup:
https://www.kirkg.us/posts/setting-up-ipv6-with-opnsense-and-comcast/
#4
General Discussion / 2 Problems: IPsec and IPv6
August 22, 2015, 04:17:09 AM
Absoltuley love OPNsense!

But, after the recent update to 15.7.9 I get an IPsec error (openvpn/ipsec):
Warning: Illegal string offset 'enable' in /usr/local/www/vpn_ipsec.php on line 258
Warning: Illegal string offset 'phase1' in /usr/local/www/vpn_ipsec.php on line 287 Warning: Invalid argument supplied for foreach() in /usr/local/www/vpn_ipsec.php on line

Which in turn gives me a:
OPNsense has detected a crash report or programming bug

Now with IPv6, everything works great until I reboot. It will then disable IPv6 on all devices until I turn DHCPv6 on and off in the WAN settings.

I don't know if this is just something I'm doing wrong or a bug? Any help would be nice. Thanks!