I think this log is telling me that I have enabled the username and password, then looks for the tunnel ID and server. I didn't know that you can have one or the other and not both. When the system looked for a tunnel ID, it reported that the IP is in use already (soft reboot!!).
I removed the tunnel ID and have not seen another reboot with IPv6.
Is this in the manual anywhere? I would highly recommend adding this information to the manual. It's really easy to get confused.
Alright.....it happened again regardless what I done. I then separated the interfaces (one for IPv4 and another for IPv6). I added the new interface to all rules and settings. I will check in the morning, but so far.....no reboots. It looks like the UTM doesn't like having both protocols on the same interface.
According to the log, to me it looks like you have native IPv6 already on eth0. Is that your WAN interface, configured as 'Ethernet DHCP / Cable Modem'? If yes, please just disable the tunnel broker as it's not needed anymore.
Hi Smith The IPv6 reboot issue existed only when IPv6 was turned off from global tab with Hurricane Electric or turning off hurricane electric. But for your case as you mentioned the reboot occurs after enabling IPv6.
I did not quite understand you last comment. Can you please explain the setup.
Also do you have WAN interface for both IPv4 and IPv6 via eth0 ?
Yes, for I am using COMCAST and they provide it natively. The issue that I had was the clients will not receive it. I have it set up on the WAN. The LAN uses the IPv6 Tunnel Broker over Hurricane Electric. Normally, I can keep them both (IPv4 and IPv6) on the LAN, but in this case the LAN had issues. When I disabled it, all of the clients could not properly resolve IPv6 (through tests over IPv6 testing web sites). I can do the same with it natively and create a DHCPv6 and attach it to the separate interface for IPv6. I just didn't realize that the DHCPv6 and the use of the prefix delegation over the LAN interface was causing the machine to perform a soft reboot. This led me to create a separate interface and the results are.....no reboots. That is still a problem, because Sophos (formerly Astaro) designed the interfaces to run both IPv4 and IPv6 on the same interface.
gari,
My last comment was about creating another interface (I have additional unused interfaces) for IPv6 only. The LAN and IPv6 interfaces connect directly into my Netgear router and the WAN is directly into my modem (for better security; not like using only a router and wireless combination with no way of deterring attacks). I have a WAN interface (eth0) for IPv4 and IPv6 (DHCP and marked as the Gateway), because it provides the DNS resolution from COMCAST.
