And how do you do that? Since they are two different things.. Look forward to your PR ;) Maybe if they changed the label from bandwidth in out, to "to" "from" in the table? Would that clear it up for you? That would be from the perspective of pfsense.

@jimp Ok thanks. I get that a lot of things are in flux right now. I hope 2021 will be remembered as The Year Of Stabilization.

@tquade Thanks for this! Worked for me.

You can go into the GUI and set the update branch to 2.6.0 snapshots, then use the console to actually run the upgrade.

@jimp I would say my setup is pretty vanilla. Extra pakages installed are: acme bandiwdthd iperf openvpn-client-export pfBlockerNG-devel But pfblocker/iperf is disabled and acme not in use. No NAT rules in use. The only oddity is that it runs inside proxmox.

@mfld I see, thanks.

So, it appears, DHCPv6-PD will only work with one interface, not both. Disable IPv6 in one, the other one works and vice versa. Is this by design ?

@jimp said in Cannot update 2.6.0 devel versions anymore: It's OK to tag someone like that when they are already participating in a thread, but the problem is calling someone out who isn't involved in the thread already. Not everyone has time to monitor the forum constantly and participate, and there are multiple developers and other employees around the forum who can help, not just one person who gets tagged. As for the 2.6.0 issue, the other thread covers how to get back to 2.5.0-RC, 2.6.0 is not ready for general use yet, nobody is actively testing it until after 2.5.0 is released. Thank you for explaining, I tagged you due to your response on the other thread, so I though you are inline with what the issue was. So I think for 2.6.0 I should wait for you or other devs to announce the start of the development on the next version, although I see some snapshots here https://snapshots.netgate.com/amd64/pfSense_master/installer/ But I will trust your word for it. And again, sorry to have bothered you.

Hello please check below link for the following error https://www.youtube.com/watch?v=kIFD3u7s0os

Thank you for your response. I also tried this on pfsense 2.4.5-p1 and I did not encountered the issue. But, reinstalling pfsense 2.5-RC using ZFS solved the issue. Thank you for your help.

@mcury [2.5.0-DEVELOPMENT][root@pf25.lab.int]/root: squid --version Squid Cache: Version 4.13