Messages

While OPNsense and pfsense are from similar base, they are not really interchangeable like that.  You should export your pfsense config only as a reference, do not try to re-import it into OPNsense

interesting topic - this should apply to other non-x86 based archs supported by FreeBSD?  Example:  SPARC64.  I have a couple of Sun Netra T1s, and an Netra X1 could act has routers - the machines already have 2 NICs...

I think the way we have it setup, we are getting IPv6 from the prefix delegation off the WAN.  The way to track the IPv6 IPs assigned would be to configure the OPNsense router box as the DHCPv6 server, then dolling out IPs that way.  Currently I think we are still getting IPv6 IPs from the upstream router beyond the OPNsense box.

btw, I'm still trying to understand this stuff, someone correct me if I am completely wrong...

Use the following configuration:
for the WAN:
IPv6 Configuration Type:  DHCP6
DHCPv6 Prefix Delegation size:  64
Send IPv6 prefix hint:  Checked

NOTE:  Don't thing TWC cares about the last 2 options

for the LAN:
IPv6 Configuration Type:  Track Interface
Track IPv6 Interface > IPv6 Interface:  WAN

Reboot router.
End.

For me, this allows my router to get a /128 for WAN, create a /64 for LAN, and Dole out IPv6 IPs to clients.

any wouldn't you know it... now it's stable.  I'm not sure what was happening.  I wonder if my BIOS clock wandered too far away for NTPd to sync.  But after 3 reboots, it's still holding up now.....

this did infact resolve my issue.  issue on GH has been closed.

Thanks,

Since the upgrade to 15.1.10 NTPd has been completely unstable.  for some reason, it is unable to resolve the first server listed under Services > Network Time Protocol - whatever it may be (pool.ntp.org, north-america.pool.ntp.org, etc.), that is also only if stays running. most of the time, the process will crash with a core dump. 

I have removed all settings, rebooted and verified BIOS clock is set to UTC.  I have gotten it running, but I am afraid to do anything for fear of loosing ntpd again.  I honestly have no idea how to provide you with information you could use.  But wouldn't mind others reporting this issue or not.

for info, this is running the following:  OPNsense 15.1.10-267d589a8 (i386)

for miniupnpd I found the following info under
Status: System logs: Routing

May 4 21:30:41    miniupnpd[60148]: Failed to init redirection engine. EXITING
May 4 21:30:41    miniupnpd[60148]: DIOCGETSTATUS: Operation not supported by device


No amount of restarting the service brings it back up.

edit:  submitted issue #166 for miniupnp  https://github.com/opnsense/core/issues/166

Anyone have any luck setting up TWC cable internet with a modem/router (set in bridge mode), and a working IPv6 on OPNSense?  I cannot get the WAN to pick up an IP from the modem (Arris TG862G).

EDIT:  Issue resolved - it was a PEBKAC problem.... 

Enabled IPv6 in settings
Configured WAN with DHCP6
selected sending PD hint
set PD request of 64

Enabled LAN IPv6 Trackint WAN interface
rebooted it all
and it worked

Somewhere in there, I thought it wasn't working due to apinger not picking up IPv6 gateway, but I think that is a different issue.  but IPv6 connectivity is working.

Marking as Solved - found the issue with the crash reporter being non-function under the following thread:

https://forum.opnsense.org/index.php?topic=303.0

This thread happens to also be the mentioning the exact same error I have come across, and is now fixed.

I'm experiencing a crash to configure miniupnp - Selecting UPnP & NAT-PMP from the Services menu renders an error.  This error does show up under the Crash reporter, however I am not able to actually submit it.  Is the crash reporter not functional?