@NogBadTheBad @stephenw10 thanks guys!

Then I'm not really sure where you are getting the traffic data from currently. The logs don't record that. You need Netflow data to see session bytes remotely. Steve

You can reply here any time. There is no time limit on threads currently.

@stephenw10 Just as a side note: still seeing that phenomenom in current snapshots / dev versions of the package. Install seems fine I guess (no immediate DNS/dpinger problem) but after upgrading/reinstalling the package you'll get it again.

@castle You positively run both. I use pfSense as my edge router and Mikrotik (RB450x2) for my LAN, the best of both world and love it. The downside is it could be expensive having two devices plus the learning curve.

That seemed likely since it's specific to starlink but you would see something in the routing log. And it has to actually receive a new dhcp lease to get that and your issue looks to be during the timeout where it's failing to pull a lease. So you have no IPv6 configured on any interface? They are all set as 'none'?

Hmm I expect that to be entered in the extended query options if you need it: https://docs.netgate.com/pfsense/en/latest/usermanager/ldap.html?highlight=extended query

@sl3390 said in WEBCONFIGURATOR WRONG CERT, NO LOGIN POSSIBLE: Webconfigurator See tip number 4. edit : Before posting, I actually tried out the command myself. [22.05-RELEASE][admin@pfSense.xxxxx.net]/root: pfSsh.php playback generateguicert Generating a new self-signed SSL/TLS certificate for the GUI...Done. Restarting webConfigurator...Done. But I saw a : pfsense.xxxxxx.net has a security policy called HTTP Strict Transport Security (HSTS), which means that Firefox can only connect to it securely. You can’t add an exception to visit this site. because I was 'stupid' enough to activate HSTS for the cert I use for the GUI access. So, Plan B: Console/ssh option 15, and restore a previous config. And then option 11 for good manners. That did it for me.

@periko Notifications will get dispatches over all available notification destinations. See /etc/notices.inc : ..... /* Notify via remote methods only - not via GUI. */ function notify_all_remote($msg) { notify_via_smtp($msg); notify_via_telegram($msg); notify_via_pushover($msg); notify_via_slack($msg);

Cool. Yeah you'd need a rule to pass traffic from 192.168.2.X to any on that interface. Not just v4 ICMP as shown in that screenshot. Steve

@gertjan said in Ver 22.05 - Unable to check for updates, pkg info reports invalid url: Does this implies that, ones a bad /usr/local/etc/pkg/repos/pfSense.conf ( /usr/local/share/pfSEnse/pkg/repos/pfSense.conf) has been pulled in, update requests are impossible as long as admin doesn't correct things ? Yes, though that file is only a sym-link to the repo files in /usr/local/share/pfSense/pkg/repos/. Those files are provided by the repo pkg and that's what was broken for a short time. Steve

There is an open feature request for it here you can add comments to: https://redmine.pfsense.org/issues/8694 Steve

Hello together, What version is shown here.... (picture below) [image: 1664893171641-5.jpg] ... should be matching to the chosen "branch"; In the dashboard shown version and the current chosen Branch should be matching together (Shown in the picture below) [image: 1664893207298-4.jpg] Show the installed packets in thew dashboard and scroll down until you reach the point "System patches", be sure there is a small hook shown and not a small plus (+) sign (Last position on the picture shown below) [image: 1664893353924-1.jpg] If there is a plus sign (+) you could click on the name of the shown patch and you will be directed to the to the pfSense section "Recommended System Patches" (As shown in the picture below, as an example) [image: 1664893498344-2.jpg] If you have applied this patch (or not, like you need it) you will be able to go back to the dashboard and click on the two bowed arrows to have a look again over the available updates. Now all should be fine there.

Yup, the DNS for that site is broken. <insert it was dns meme> But at least now you know it's broken and how so you can use any of the 3 workarounds to allow access again until it's fixed. Steve

At work, will run memory checker tonight. Thanks for the suggestion!

@periko According the manual @ https://docs.netgate.com/pfsense/en/latest/config/advanced-notifications.html : [image: 1664870490371-d4adca7b-310a-4413-8d64-b4e8273fc301-image.png] But, it was a no go as I can't access : https://core.telegram.org/bots#creating-a-new-bot so, I guess Telegram has some temporary issues.

That particular CVE does not affect pfSense because it only applies to strongswan when acting as an EAP client which pfSense cannot be configured to do. That is often the case, FreeBSD vulnerabilities do not necessarily apply to pfSense. If it was affected we would either make a point release to address it or build an updated pkg in our repo which you could 'pkg upgrade' to depending on the level of assessed risk. Steve

I use FreeBSD as a daily driver on one of my machines and im falling in love with it. [image: 1664806629239-a6063969-adb0-44cd-9b82-b11765f66b47-image.png] Its so robust and unbreakable. Native ZFS support is just a cherry on top of all that. And yes. It has nothing to to with broken and bloated Linux kernel. Not only its not Linux based, you actually need to emulate Linux with projects like Linuxlator to be able to run Linux applications. Not that i recommend it, just want to point out how different it is compared to billions of Linux distros out there.

@stephenw10 I leave the dash board web page open on my desktop. Thank you for the reply.