Categories

• TNSR

  Discussions about TNSR

  • TNSR Announcements
  • TNSR Feedback
  • Problems Installing or Upgrading TNSR Software
  381 Topics

  1k Posts

  M

  Following up on this.. EVPN at the control plane with a anycast gateway would help here....
• pfSense® Software

  Discussions about pfSense Software, click a category below

  • Messages from the pfSense Team
  • General pfSense Questions
  • Netgate Nexus
  • Problems Installing or Upgrading pfSense Software
  • Firewalling
  • NAT
  • HA/CARP/VIPs
  • L2/Switching/VLANs
  • Routing and Multi WAN
  • Traffic Shaping
  • DHCP and DNS
  • IPv6
  • IPsec
  • OpenVPN
  • Captive Portal
  • webGUI
  • Wireless
  • SNMP
  • Documentation
  • Development
  • Gaming
  • Virtualization
  • Hardware
  • Bounties
  • Retired
  122k Topics

  785k Posts

  J

  make sure creating alias to block/reject 192.168.100 if you have guest network so your friend phone cannot access your dish [image: 1788605723379-rejec.png]
• pfSense Packages

  Discussions about pfSense software packages

  • Cache/Proxy
  • IDS/IPS
  • Traffic Monitoring
  • pfBlockerNG
  • UPS Tools
  • ACME
  • FRR
  • Tailscale
  • WireGuard
  21k Topics

  130k Posts

  J

  @daro said in Import Let's Encrypt Certificates to my Netgate for use in HAProxy: text record every few months on my ISP's domain config. What would your isp have to do with it? Who is providing the dns for your domains? Do they not have an api to automate the dns method? You understand you could move your domains dns to some other service - example I host some of my domains dns on cloudflare (free). I use dns to get validate and get new certs via acme on pfsense. edit: also there a new method coming from acme "DNS-PERSIST-01" this will not require a api where the txt for the dns challenge has to be different every time you renew. But can be added manually, and be perm. This will be much easier method for dns validation, because who you use for dns will not have to have an api, and you will not have to create a token or key that gives acme ability to change records. https://letsencrypt.org/2025/12/02/from-90-to-45#making-automation-easier-with-a-new-dns-challenge-type edit2: btw - your post got me thinking about the upcoming 45 day change - and while sure we have time.. I think 2028 is when it really kicks in on acme.. I just changed the profile to tlsserver, so its pulling 45 days certs and did a renew.. And yup got only 45 day cert. Validity Not Before Sat, 05 Sep 2026 10:11:31 GMT Not After Tue, 20 Oct 2026 10:11:30 GMT I am using wildcard btw as well.
• pfSense International Support

  Discuss pfSense in other languages

  • Chinese
  • Deutsch
  • Español
  • Français
  • Indonesian
  • Italiano
  • Russian
  • Nederlands
  • Norwegian
  • Portuguese
  • Polish
  • Romanian
  • Swedish
  • Turkish
  43k Topics

  268k Posts

  C

  Hallo zusammen, ich habe ein merkwürdiges Verhalten mit dem Traffic Shaper (ALTQ / HFSC) unter pfSense Plus 26.07 festgestellt. Meine Internetleitung unterstützt 150 Mbit/s Upload. Wenn ich im Traffic Shaper bei der WAN-Root-Queue qInternet folgende Werte eintrage: Bandwidth: 100000 Kbit/s → ca. 100 Mbit/s Upload Bandwidth: 150000 Kbit/s → nur ca. 75 Mbit/s Upload Bandwidth: 200000 Kbit/s → ca. 100 Mbit/s Upload Bandwidth: 300000 Kbit/s → ca. 150 Mbit/s Upload Das Verhalten ist damit praktisch: bis 100 Mbit/s → korrekt über 100 Mbit/s → tatsächlicher Durchsatz ≈ eingestellter Wert / 2 Beispiel: Shaper: 150000 Kbit/s Resultat: ~75 Mbit/s Shaper: 300000 Kbit/s Resultat: ~150 Mbit/s Der Anschluss selbst kann die 150 Mbit/s problemlos liefern. Das lässt sich daran erkennen, dass ich mit einem Shaper-Wert von 300000 Kbit/s tatsächlich ungefähr 150 Mbit/s erreiche. Konfiguration Ich verwende ALTQ / HFSC. WAN: WAN └── qInternet ├── qACK ├── qDefault ├── qVoIP ├── qOthersHigh └── qOthersLow Die WAN-Root-Queue qInternet ist beispielsweise so konfiguriert: Bandwidth: 300000 Kbit/s Upper Limit: 300000 Kb Link Share: 300000 Kb Damit erreiche ich ca. 150 Mbit/s Upload. Die entsprechenden Werte bei 150000 Kbit/s führen dagegen nur zu ca. 75 Mbit/s. Interessanterweise scheint der Effekt nicht einfach durch die Child-Queues verursacht zu werden, da sich die Halbierung reproduzierbar an der 100-Mbit-Grenze zeigt. Frage Ist dieses Verhalten bei pfSense Plus 26.07 / ALTQ / HFSC bekannt? Gibt es möglicherweise eine 100-Mbit-Grenze, Integer-/Unit-Problematik oder einen Bug bei der Berechnung der HFSC-Bandbreite? Hat jemand mit einer Leitung >100 Mbit/s und HFSC ein ähnliches Verhalten? Als Workaround muss ich momentan für gewünschte 150 Mbit/s Upload einen Wert von 300000 Kbit/s eintragen. Vielen Dank!
• Official Netgate® Hardware

  Information about hardware available from Netgate
  3k Topics

  21k Posts

  S

  I'm not aware of any other cases with ports presenting like that. So I doubt it's a temperature/time issue. There are a lot of 4100s out there that will have seen many more hours at higher temps.
• Netgate Announcements

  Information about hardware available from Netgate
  44 Topics

  211 Posts

  A

  It looks like unified web management could be coming soon. It would be great if it means easier control and management of all web services in one place. Let's see if any companies announce more details about it!
• Off-Topic & Non-Support Discussion

  Feel free to talk about anything and everything here

  • Forum Feedback
  • Community Job Board
  4k Topics

  19k Posts

  M

  Thank you very much!