Messages

it's broken..has been for a while... ;) ;D

ok instlaled the et telemetry plugin and it's there..thanks folks for the tip I just missed it..:)

aha i didn't know telemetry was a separate plugin..i missed that part in the documentation lt me look.

et?  none.  did the update thing and it's still not there..

yeah it's not there in my opnsense. 

I have been reading the docs and I cannot find a place to install my et pro telem token.  I know I am missing something..i just can't find it..:)

 Internal (igb1_vlan10) -> v4: 192.168.255.1/24
LAN (igb1)      -> v4: 192.168.1.1/24
WAN (igb2)      -> v4/DHCP4: 98.218.75.122/23
                    v6/DHCP6: 2001:558:6003:8:a53d:e2e2:250a:db88/128
sickcomputer (igb1_vlan30) -> v4: 192.168.253.1/24
wguest (igb1_vlan20) -> v4: 192.168.254.1/24

it works fine when i do the initial live install...before it gets connected to disk.  once i get it loaded and do the vlans it stops working.  It's been this way for years with both opn and pfsense...Linux based firewalls, however work fine...without having to manually assign ipv6 subnets to the vlan interfaces.

yes i am using comcast..and i have everything setup at /55 and tried /54.  it works under Linux, windows, if i plug my laptop directly into the modem.  It works on the hardware that is currently running on if i install Linux on it so it's not my hardware.  both pfsense and opnsense both refuse to work with ipv6.  I've tried different modems as well.  It's not Comcast, the modem, the hardware i have opnsense on and other firewalls NOT BSD base work fine.  If i install opnsense anew..and let it run Live then the internal gets ipv6 and wan does.  Once i build my vlans then ipv6 breaks. 

So what logs does Opnsense want to try to troubleshoot this?

   Internal      1000baseT <full-duplex>   192.168.255.1
track6
   LAN      1000baseT <full-duplex>   192.168.1.1
   WAN      1000baseT <full-duplex>   98.218.75.122
2001:558:6003:8:a53d:e2e2:250a:db88
   sickcomputer      1000baseT <full-duplex>   192.168.253.1
   wguest      1000baseT <full-duplex>   192.168.254.1


I have tried multiple modems and nics.  I simply cannot get ipv6 to get sent to the internal vlans.  This has been ongoing for a long time.  Any ideas where to start?

it's an ongoing issue..you are one of many that have commented on ipv6 being broken in OpnSense.

IIRC ddclient is supposed to be the version opnsense is switching to?  i tired it and I get constant cnanot  determine external IP address errors.  the "legacy" dyndns client works fine for me at no-ip.

I had the legacy installed and it works fine in terms of ddns...however, the new version was not updating and the logs say unable to determine IP address.  Not sure why it's refusing to latch on correctly.

except my internal interfaces get....nothing.  I have noticed when I switch modems the BSD based firewalls then do ipv6 correctly but then I lose connectivity every 3-5 minutes for about 5-20 seconds.  When I plug a laptop or desktop directly into the modem however everything works fine.  it's only opn(and PF)sense that have this weird behavior.  This latest version it went from partially working to nothing at all.

If you are on comcast business, and have static /56, one of the /64's is going to be on your wan interface.  Try requesting /59 on your wan interface, and then try assigning 0x1 to one of your internal interfaces and "track interface" of your wan connection.  This is working for me.

yeppers..tried that..no dice with the latest version  my ipv6 is dynamic..but again it works fine if I plug a machine directly into the cable modem..and my linux based firewalls work fine..it's only OPNSense that is having this issue.

except my internal interfaces get....nothing.  I have noticed when I switch modems the BSD based firewalls then do ipv6 correctly but then I lose connectivity every 3-5 minutes for about 5-20 seconds.  When I plug a laptop or desktop directly into the modem however everything works fine.  it's only opn(and PF)sense that have this weird behavior.  This latest version it went from partially working to nothing at all.

If you are on comcast business, and have static /56, one of the /64's is going to be on your wan interface.  Try requesting /59 on your wan interface, and then try assigning 0x1 to one of your internal interfaces and "track interface" of your wan connection.  This is working for me.

static ipv6 in my area with comcrap business doesn't work due to known firmware issues with their CPE in my area:  https://etc-md.com/2021/07/28/the-comcast-business-ipv6-issue-resolved/
Also comcast is now requiring you sue their cpe for ALL installs or they charge you what's know as the rack rate which is roughly double what you'll pay under a "promotion"