possible workaround: overprovisioning (saferase, then only use <=80% of the ssd at install time)

The friday after easter-weekend would be perfect and memorable ;)

For those who can't/won't upgrade to 45.0.1: Hold "Shift" while starting Firefox. Clean settings. Reinstall/Configure Plugins also solves the Problem whatever it was ;)

I will make a post there. I didn't notice this problem prior to 2.3 so didn't know if there was a connection.

https://wiki.freebsd.org/dev/ath_hal(4)/HardwareSupport

All of the docs everywhere have used ">" for quite a long time, to indicate Menu Name > Menu Item, in this case the breadcrumb trail is using more of a "directory path" style which doesn't always translate to Menu Name / Menu Item since there are also tab names and so on that go deeper than the menu. So the ">" is a direction to the user, while the "/" is a visual depiction of the structure. The "/" could be changed to a ">" but I'm not sure it really helps or hurts anything significantly enough at this point to do so.

There isn't a way to manually specify that address, it uses whichever address is closest to the target. You can set the option under System > Advanced, Networking tab to have the system prefer IPv4 if that would help you out.

That worked! Thanks much!

beau·ti·ful !

just found this as well, so I guess it's an ongoing thing: https://www.abuseipdb.com/report-history/40.76.59.167 https://www.google.com/search?q=40.76.59.167

To be clear, it is Acropolis …  KVM using Nutanix CE. It absolutely isn't Hyper-V. I did notice the the Hyper-V reference in the output, completely confused as to where that comes from. If other people are running it on KVM then I'm prepared to accept that there's some nuance with Acropolis that's tripping this up. The same happens with the latest free BSD release as well so its not pfsense specific. I'll chat to Nutanix. Thanks for your time.

I'm thinking it is too now… after leaving a couple of my systems on for a couple of days, it seems like only one is really having IPv6 issues after a while, the others must have been temporary issues before. It's Windows 10 on all. I don't think this is a pfSense issue at this point.

Thank you Chris, much appreciated. The reason I want to look at dhcp6c is the logging is a bit naf, so I would like to tidy that up.

We always have RC. Soon.

Netflix seems to have opened quite a can of worms with their recent changes. Not sure how many legit users are impacted, but it's likely many. Netflix stopped working out of our office recently on some devices. The iOS and Android Netflix apps don't work, and Firefox doesn't work, with that proxy detected garbage when the traffic isn't being proxied. Same machines where Firefox doesn't work, Chrome does. Couldn't see anything apparently different between them. Their support was useless. Something along the lines of DNS needing to take the same path as the HTTP/HTTPS requests was the best answer we got out of Netflix support, but that makes no sense at all when the same PC works with one browser and not another. We're BGP multi-homed across multiple providers with a full Internet routing table, so no, our traffic isn't necessarily going to take the same path every time, and traffic to IP A may not have the same path as IP B. But if that were the only issue, it wouldn't differ from one browser to another on the same machine.

They all have to share the same channel, it can only run one radio

Hmm ok, I guess gitsync was missed and not runned. After gitsync all is fine now.

Hi! Use non-local gateway through interface specific route, this option enabled and I get only 2 warnings during bootup and that`s it, no more. What I think is happening: I use pppoe ipv6 and when device boots it sets default gateway to fe80::2c1:64ff:fed8:3f00 but errors, because pppoe is not yet fully initialised (first ipv4 and then ipv6). Also fe80::2c1:64ff:fed8:3f00 is not on the same subnet as IPv6 address on pppoe iface so that is why I was getting errors, and use non local gateway checked shut it up.

I would imagine that just as it is set now, the Firmware Branch setting (System > Updates > Update Settings) will likely need to be set to "Development" to get the pre-release builds. The final release build will likely have it defaulted to "Stable".