1. Home
  2. pfSense® Software

Subcategories

  • Announcements and information about pfSense software posted by the project team

    215 Topics
    3k Posts
    Y
    I do not know if it is related to the 25.07 RC, or not, but I had an ipv6 WAN outage today, that needed a reboot, instead of a dhcp6 client retry a few moment later. On the dashboard, WAN interface was showing 2001:xxxx:xxxx:xxxx:xxxx:: instead of 2001:xxxx:xxxx:xxxx:xxxx:yyyy:yyyy:yyyy:yyyy Here is the offending lines in the DHCP log : Aug 1 16:34:42 dhcp6c 77684 add an address 2001:xxxx:xxxx:xxxx::/128 on ix3 Aug 1 16:34:42 dhcp6c 77684 dhcp6c Received INFO Aug 1 16:34:42 dhcp6c 77684 Sending Renew Aug 1 16:08:11 kea-dhcp6 50779 ERROR [kea-dhcp6.packets.0x319bcd617400] DHCP6_PACKET_SEND_FAIL duid=[00:01:00:01:2d:4c:12:e7:f8:xx:xx:xx:xx:xx], [no hwaddr info], tid=0x3a7239: failed to send DHCPv6 packet: pkt6 send failed: sendmsg() returned with an error: Permission denied By the way, in the web GUI Dashboard, in the Interface Widget, would it be possible to modify it to see the whole ipv6 without horizontal scrolling in the final version or next beta ?

  • Discussions about pfSense software that do not fit into one of the more specific categories below.

    27k Topics
    189k Posts
    N
    @amrogers3 Now really, you are considering the ai driven forum spams? Don't mess with mtu. its not the cause for dropouts.

  • Discussions about Multi-Instance Management.

    14 Topics
    103 Posts
    luckman212L
    With 25.07 imminent, I decided to kick the tires of Nexus on my 6100. I tried to follow the guidance from: Netgate Nexus Controller Setup Netgate Nexus Licensing Netgate Nexus Options in the pfSense Plus WebGUI Instance Registration But, I failed (I think? or maybe I succeeded?). Got a handful of API errors and failure toasts. Is this feature not operational yet, or is something wrong with the buttons I'm pressing? Here are some assorted screenshots: [image: 1754001364872-d7c121de-49df-4ec1-b149-3a598be92d64-image-resized.png] [image: 1754001376184-7574ed30-c6bf-4e4b-b6d9-74f5900919ff-image-resized.png] [image: 1754001382643-b2ac03f9-5828-4061-86ba-405f75c65412-image-resized.png] [image: 1754001388783-d839be60-5e20-4730-adfa-597be0e93eaf-image-resized.png] [image: 1754001395757-65952b3f-cb0c-43ee-9819-6dfbd6a00c55-image-resized.png] [image: 1754001401436-80dbb8ad-9b81-4b0b-9e71-621382e43f0a-image-resized.png]

  • Discussions about installing or upgrading pfSense software

    10k Topics
    62k Posts
    B
    I've got a bit of a weird issue with updating from the GUI right now. It's not a showstopper, but I'm hoping for some help troubleshooting it because I'm hoping it's not indicative of a bigger issue. The machine was running 2.8, I was planning on moving to 2.8.1 BETA for the newer version of Unbound. The GUI shows: [image: 1754066237439-2620e27d-7258-47b7-ab15-cd48235e6ca4-image.png] Moving to the Update screen, I see: [image: 1754066263002-96b714c5-0265-40ac-8b68-f4b37c62ac67-image.png] So I try swapping to the BETA version on the update settings screen, which does nothing to alleviate the problem. I SSH in and hit option 13 so I can see whatever error occurs, but... success! The firewall updates to 2.8.1 BETA and reboots. Logging back into the GUI, the issue still occurs - I'm seeing the "error in version information" and "unable to check for updates." So I go through the Troubleshooting Upgrades docs, up to and including a full reinstall of all packages (this box is on the other side of an ocean from me, so a simple USB stick reinstall isn't going to happen without some heavy lifting). After the full reinstall-and-reboot, which was successful, the issue still occurs - "error in version information" Anyone got any clues as to what's wrong? I'm glad I can SSH in and update things, but this is weird. I can't seem to find anything wrong to focus troubleshooting on.

  • Discussions about firewalling functionality in pfSense software

    10k Topics
    59k Posts
    S
    Thank you @johnpoz and @SteveITS for the super fast reply.

  • Discussions about Network Address Translation (NAT)

    6k Topics
    31k Posts
    H
    I have just deployed pfSense in my institution and my setup is as follow, I have a core switch which handles my vlan, and a default route to pf sense that handles internet traffic. My pfsense has three wan interfaces ISP1 ISP2 and ISP3, in ISP1 I have enabled port forwarding for port 443. now the issue arises when i try to access the website locally, i can only access it when my traffic is routed through ISP2 all other ISPs i cannot access the website locally. what could be the issue any help would be highly appreciated. Regards, Huzefa

  • Discussions about High Availability, CARP, and utilizing additional IP addresses

    3k Topics
    12k Posts
    empbillyE
    @netblues The problem was with the outbound NAT rules. I had disabled our AD's VLAN so that it would connect to the internet using its own IP address rather than CARP, but I didn't realize that this would interfere. After enabling it, it worked correctly. Thanks for your help!

  • Discussions about Layer 2 Networking, including switching and VLANs

    1k Topics
    10k Posts
    C
    Hello, Good day, We have Netgate SG2100, I wanna configure the available LAN, e.g, Ports 3 and 4, the purpose is not to buy a managed switch for expense purposes. I already did the configuration, actually, for VLAN30, I created the rules and enabled the DHCP server. But still no internet connection on LAN4 VLAN30, the status of the LAN is connected. The IP release is from VLAN30, but still no internet. Can anyone here explain to me why it is not working? Thank you

  • Discussions about routing and Multiple WAN uplinks (WAN Failover, WAN Load Balancing, etc.)

    9k Topics
    41k Posts
    E
    I think the best solution is the implementation of a flag "Disable state-policy override for OpenVPN rules", like for IPSec tunnels. I solved only by changing the whole firewall state policy to "Floating States", as explained in my first post.

  • Discussions about traffic shaping and limiters

    3k Topics
    16k Posts
    K
    @maliaga If you can find a way to report bugs in a way that Netgate respond to, let us know!

  • Discussions about DHCP, DNS Resolver (Unbound), DNS Forwarder (dnsmasq), and general DNS issues

    7k Topics
    43k Posts
    C
    @pfsenseuser10293 You might be able to do what you need with bind which should support view clauses,, pfsense has a bind package. So different ip's making the request get routed differently over DNS, you could set localhost to bypass unbound, and put everything else to forward to unbound (dns resolver) and work as you have now configured. I just had a quick look, no patching/hacking needed, views are configurable in the GUI, and you can change the port for unbound in the GUI, so bind is 53, and put unbound on a different port to listen for queries sent to it from bind. pfSense -> bind -> internet LAN -> bind-> dns resolver (unbound) -> (filtered) VPN/domain controller

  • Discussions about IPv6 connectivity and services

    2k Topics
    20k Posts
    E
    @pst said in Router advertisement not sending default gateway: That rule shouldn't be needed, it is part of the automatic rule set added by pfSense. I get those by means of pfSense magic: (check in /tmp/rules.debug) here are some snips from that file (I can see ICMP added automatically, but not UDP): Allow only bare essential icmpv6 packets (NS, NA, and RA, echoreq, echorep) pass out quick inet6 proto ipv6-icmp from fe80::/10 to fe80::/10 icmp6-type {129,133,134,135,136} ridentifier 1000000108 keep state pass out quick inet6 proto ipv6-icmp from fe80::/10 to ff02::/16 icmp6-type {129,133,134,135,136} ridentifier 1000000109 keep state pass in quick inet6 proto ipv6-icmp from fe80::/10 to fe80::/10 icmp6-type {128,133,134,135,136} ridentifier 1000000110 keep state pass in quick inet6 proto ipv6-icmp from ff02::/16 to fe80::/10 icmp6-type {128,133,134,135,136} ridentifier 1000000111 keep state pass in quick inet6 proto ipv6-icmp from fe80::/10 to ff02::/16 icmp6-type {128,133,134,135,136} ridentifier 1000000112 keep state pass in quick inet6 proto ipv6-icmp from :: to ff02::/16 icmp6-type {128,133,134,135,136} ridentifier 1000000113 keep state We use the mighty pf, we cannot be fooled. block log quick inet proto { tcp, udp } from any port = 0 to any ridentifier 1000000114 label "Block traffic from port 0" block log quick inet proto { tcp, udp } from any to any port = 0 ridentifier 1000000115 label "Block traffic to port 0" block log quick inet6 proto { tcp, udp } from any port = 0 to any ridentifier 1000000116 label "Block traffic from port 0" block log quick inet6 proto { tcp, udp } from any to any port = 0 ridentifier 1000000117 label "Block traffic to port 0" Furthermore I can see that I have autoadded config rules for DHCP4 and DHCP6 here: allow access to DHCP server on LAN pass in quick on $LAN proto udp from any port = 68 to 255.255.255.255 port = 67 ridentifier 1000002541 label "allow access to DHCP server" pass in quick on $LAN proto udp from any port = 68 to 192.168.2.3 port = 67 ridentifier 1000002542 label "allow access to DHCP server" pass out quick on $LAN proto udp from 192.168.2.3 port = 67 to any port = 68 ridentifier 1000002543 label "allow access to DHCP server" allow access to DHCPv6 server on LAN pass quick on $LAN inet6 proto udp from fe80::/10 to fe80::/10 port = 546 ridentifier 1000002551 label "allow access to DHCPv6 server" pass quick on $LAN inet6 proto udp from fe80::/10 to ff02::/16 port = 546 ridentifier 1000002552 label "allow access to DHCPv6 server" pass quick on $LAN inet6 proto udp from fe80::/10 to ff02::/16 port = 547 ridentifier 1000002553 label "allow access to DHCPv6 server" pass quick on $LAN inet6 proto udp from ff02::/16 to fe80::/10 port = 547 ridentifier 1000002554 label "allow access to DHCPv6 server" pass in quick on $LAN inet6 proto udp from fe80::/10 to 2001:2042:334b:c300:a236:9fff:fe7a:603f port = 546 ridentifier 1000002555 label "allow access to DHCPv6 server" pass out quick on $LAN inet6 proto udp from 2001:2042:334b:c300:a236:9fff:fe7a:603f port = 547 to fe80::/10 ridentifier 1000002556 label "allow access to DHCPv6 server" But as IPv6 seems to use port 5355 for something called link-local resolution according to google (https://www.google.com/search?q=ipv6+5355) those presets does not help. So adding the rule adds the missing config (probably could be more restrictive to only match 5355): pass in quick on $LAN inet6 from fe80::/10 to ff02::/16 ridentifier 1752488409 keep state label "USER_RULE" label "id:1752488409"

  • Discussions about IPsec VPNs

    6k Topics
    24k Posts
    planedropP
    Opened a Redmine about this since this either A. needs to be explained more clearly, or B. needs to be changed so the docs say "will" instead of "may". https://redmine.pfsense.org/issues/16340

  • Discussions about OpenVPN

    10k Topics
    53k Posts
    A
    Thanks but I'mafraid to say I've had a conversation with chatgpt about it and it didn't take long to find the solution, firstly as you suggested I binded to any interface, then created a dedicated firewall rule in the LAN interface. Then got Connection Attempt write UDPv4: No route to host (fd=6,code=65) in OpenVPN logs Which again chatgpt advised creating a default gateway route back to the UDM in System/Routing Hope this helps someone else in the future.

  • Discussions about Captive Portal, vouchers, and related topics

    4k Topics
    19k Posts
    N
    The experience from an end device is that it will have an IP via dhcp but the captive portal page will not appear. Device then has no internet and cannot ping the gateway. There was one device that had been connected earlier and still had an IP but did not show up as an active user under Status > Captive Portal. The gateway could not ping the device nor vice versa. The device wasn't showing in ARP. After going to Services > Captive Portal and hitting save, all issues were gone. Gateway could ping device and vise versa. Captive portal page came up etc. I tried setting a hard timout (couple of minutes past the voucher expiry) but this did not resolve the issue.

  • Anything that does not fit in other categories related to the webGUI

    2k Topics
    10k Posts
    D
    @SteveITS Thanks, restarting the GUI fixed it and I was able to replace the routers.

  • Discussions about wireless networks, interfaces, and clients

    2k Topics
    11k Posts
    jhmc93J
    @stephenw10 Solved! I'm running pfsense on proxmox so I passed through the wifi adapter but forgot to tick all functions and pci express box. It now works thanks for your help

  • Discussions about monitoring via SNMP

    197 Topics
    609 Posts
    C
    I figured it out . My firewalls had an old unused OpenVPN client connection on it that was unstable and every time it reconnected, it got a new IP address causing pfsense to restart all packages, and since it took down SNMP, we wouldn't get alerted about the interface going down either... So this issue is solved now

  • Discussions about pfSense documentation, including the book

    186 Topics
    1k Posts
    opnwallO
    As a volunteer translator, I suggest that the official website update the template files of the online translation (https://zanata.netgate.com/) in a timely manner, or open the function of uploading po or mo files to replace the translation templates that are still in pfsense 2.50.

  • Topics related to developing pfSense: coding styles, skills, questions etc.
    1k Topics
    7k Posts
    P
    @dennypage said in pfsense-tools.git clang gcc: @phil80 said in pfsense-tools.git clang gcc: portsnap fetch properly fetches freebsd ports collection FWIW, portsnap is very dead as far as the FreeBSD folk are concerned. All references to it were removed from the documentation 5 years ago, and its use is no longer supported. The original announcement is here: [HEADS UP] Planned deprecation of portsnap. Thank you for the reminder. I usually only use Latest. I always use git for collaboration In short life or one use jails, portsnap is way faster to fetch than git for one package compile Based on your linked article, I'll favor git in the future

  • Discussions about playing network-based games behind pfSense from consoles, PCs, etc.

    427 Topics
    3k Posts
    W
    I am on 24.11. I have several consoles at home, PS5, PS4, Nintendo's. No issues at all. I just assigned a fixed IP to them put those IP in the ACL allow list. Outbound NAT with static port for the consoles. The only "issue" is that port mappings remain there for days. I have to manually cancel them. At the moment I did not find any solution to remove them via cron job scripts.

  • Discussions about virtualizing pfSense in hypervisors such as AWS, VMware, Hyper-V, Xen, KVM, qemu, etc

    2k Topics
    12k Posts
    O
    Browsing the qat driver sources for FreeBSD and Linux, it sure looks like there simply isn't a driver for the VF PCI device IDs for c3xxx in the FreeBSD tree, but there is for Linux. Am I reading this correctly? Can pfSense even use all of the QAT engines in the c3xxx silicon at the same time to warrant passing through the entire hardware as is seemingly required? I was thinking it would be useful to leave some VFs for host ZFS use and possibly another guest application. Is it worth the effort to copy&paste the PF driver to make the VF version?

  • Discussions about pfSense hardware support

    8k Topics
    69k Posts
    M
    Has anyone upgraded the CPU on the XG230 Rev2 units, mine runs pfsense nicely, but looking to get a Xeon E3-1240L-V5 chip into it. However unsure re the support. I've done an export of the hardware from the command line. At the top it implies E3-1200 support, but also references H110 chipset. This is the export from BSD, so looks like a H110, but references E3-1200 chip at the top and E3-1500 hostb0@pci0:0:0:0:class=0x060000 rev=0x07 hdr=0x00 vendor=0x8086 device=0x190f subvendor=0x8086 subdevice=0x2015 vendor = 'Intel Corporation' device = 'Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers' class = bridge subclass = HOST-PCI pcib1@pci0:0:1:0:class=0x060400 rev=0x07 hdr=0x01 vendor=0x8086 device=0x1901 subvendor=0x8086 subdevice=0x2015 vendor = 'Intel Corporation' device = '6th-10th Gen Core Processor PCIe Controller (x16)' class = bridge subclass = PCI-PCI vgapci0@pci0:0:2:0:class=0x030000 rev=0x06 hdr=0x00 vendor=0x8086 device=0x1902 subvendor=0x8086 subdevice=0x0000 vendor = 'Intel Corporation' device = 'HD Graphics 510' class = display subclass = VGA xhci0@pci0:0:20:0:class=0x0c0330 rev=0x31 hdr=0x00 vendor=0x8086 device=0xa12f subvendor=0x8086 subdevice=0x7270 vendor = 'Intel Corporation' device = '100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller' class = serial bus subclass = USB pchtherm0@pci0:0:20:2:class=0x118000 rev=0x31 hdr=0x00 vendor=0x8086 device=0xa131 subvendor=0x8086 subdevice=0x7270 vendor = 'Intel Corporation' device = '100 Series/C230 Series Chipset Family Thermal Subsystem' class = dasp none0@pci0:0:22:0:class=0x078000 rev=0x31 hdr=0x00 vendor=0x8086 device=0xa13a subvendor=0x8086 subdevice=0x1999 vendor = 'Intel Corporation' device = '100 Series/C230 Series Chipset Family MEI Controller' class = simple comms ahci0@pci0:0:23:0:class=0x010601 rev=0x31 hdr=0x00 vendor=0x8086 device=0xa102 subvendor=0x8086 subdevice=0x7270 vendor = 'Intel Corporation' device = 'Q170/Q150/B150/H170/H110/Z170/CM236 Chipset SATA Controller [AHCI Mode]' class = mass storage subclass = SATA pcib2@pci0:0:28:0:class=0x060400 rev=0xf1 hdr=0x01 vendor=0x8086 device=0xa114 subvendor=0x8086 subdevice=0x7270 vendor = 'Intel Corporation' device = '100 Series/C230 Series Chipset Family PCI Express Root Port' class = bridge subclass = PCI-PCI pcib3@pci0:0:28:5:class=0x060400 rev=0xf1 hdr=0x01 vendor=0x8086 device=0xa115 subvendor=0x8086 subdevice=0x7270 vendor = 'Intel Corporation' device = '100 Series/C230 Series Chipset Family PCI Express Root Port' class = bridge subclass = PCI-PCI pcib4@pci0:0:28:6:class=0x060400 rev=0xf1 hdr=0x01 vendor=0x8086 device=0xa116 subvendor=0x8086 subdevice=0x7270 vendor = 'Intel Corporation' device = '100 Series/C230 Series Chipset Family PCI Express Root Port' class = bridge subclass = PCI-PCI pcib5@pci0:0:28:7:class=0x060400 rev=0xf1 hdr=0x01 vendor=0x8086 device=0xa117 subvendor=0x8086 subdevice=0x7270 vendor = 'Intel Corporation' device = '100 Series/C230 Series Chipset Family PCI Express Root Port' class = bridge subclass = PCI-PCI pcib6@pci0:0:29:0:class=0x060400 rev=0xf1 hdr=0x01 vendor=0x8086 device=0xa118 subvendor=0x8086 subdevice=0x7270 vendor = 'Intel Corporation' device = '100 Series/C230 Series Chipset Family PCI Express Root Port' class = bridge subclass = PCI-PCI pcib7@pci0:0:29:1:class=0x060400 rev=0xf1 hdr=0x01 vendor=0x8086 device=0xa119 subvendor=0x8086 subdevice=0x7270 vendor = 'Intel Corporation' device = '100 Series/C230 Series Chipset Family PCI Express Root Port' class = bridge subclass = PCI-PCI isab0@pci0:0:31:0:class=0x060100 rev=0x31 hdr=0x00 vendor=0x8086 device=0xa143 subvendor=0x8086 subdevice=0x7270 vendor = 'Intel Corporation' device = 'H110 Chipset LPC/eSPI Controller' class = bridge subclass = PCI-ISA none1@pci0:0:31:2:class=0x058000 rev=0x31 hdr=0x00 vendor=0x8086 device=0xa121 subvendor=0x8086 subdevice=0x7270 vendor = 'Intel Corporation' device = '100 Series/C230 Series Chipset Family Power Management Controller' class = memory hdac0@pci0:0:31:3:class=0x040380 rev=0x31 hdr=0x00 vendor=0x8086 device=0xa170 subvendor=0x8086 subdevice=0x7270 vendor = 'Intel Corporation' device = '100 Series/C230 Series Chipset Family HD Audio Controller' class = multimedia subclass = HDA ichsmb0@pci0:0:31:4:class=0x0c0500 rev=0x31 hdr=0x00 vendor=0x8086 device=0xa123 subvendor=0x8086 subdevice=0x7270 vendor = 'Intel Corporation' device = '100 Series/C230 Series Chipset Family SMBus' class = serial bus subclass = SMBus igb0@pci0:2:0:0:class=0x020000 rev=0x03 hdr=0x00 vendor=0x8086 device=0x1539 subvendor=0x15bb subdevice=0x34e6 vendor = 'Intel Corporation' device = 'I211 Gigabit Network Connection' class = network subclass = ethernet igb1@pci0:3:0:0:class=0x020000 rev=0x03 hdr=0x00 vendor=0x8086 device=0x1539 subvendor=0x15bb subdevice=0x34e6 vendor = 'Intel Corporation' device = 'I211 Gigabit Network Connection' class = network subclass = ethernet igb2@pci0:4:0:0:class=0x020000 rev=0x03 hdr=0x00 vendor=0x8086 device=0x1539 subvendor=0x15bb subdevice=0x34e6 vendor = 'Intel Corporation' device = 'I211 Gigabit Network Connection' class = network subclass = ethernet igb3@pci0:5:0:0:class=0x020000 rev=0x03 hdr=0x00 vendor=0x8086 device=0x1539 subvendor=0x15bb subdevice=0x34e6 vendor = 'Intel Corporation' device = 'I211 Gigabit Network Connection' class = network subclass = ethernet igb4@pci0:6:0:0:class=0x020000 rev=0x03 hdr=0x00 vendor=0x8086 device=0x1539 subvendor=0x15bb subdevice=0x0000 vendor = 'Intel Corporation' device = 'I211 Gigabit Network Connection' class = network subclass = ethernet pcib8@pci0:7:0:0:class=0x060400 rev=0x05 hdr=0x01 vendor=0x12d8 device=0x2404 subvendor=0x0000 subdevice=0x0000 vendor = 'Pericom Semiconductor' device = 'PI7C9X2G404 EL/SL PCIe2 4-Port/4-Lane Packet Switch' class = bridge subclass = PCI-PCI pcib9@pci0:8:1:0:class=0x060400 rev=0x05 hdr=0x01 vendor=0x12d8 device=0x2404 subvendor=0x0000 subdevice=0x0000 vendor = 'Pericom Semiconductor' device = 'PI7C9X2G404 EL/SL PCIe2 4-Port/4-Lane Packet Switch' class = bridge subclass = PCI-PCI pcib10@pci0:8:2:0:class=0x060400 rev=0x05 hdr=0x01 vendor=0x12d8 device=0x2404 subvendor=0x0000 subdevice=0x0000 vendor = 'Pericom Semiconductor' device = 'PI7C9X2G404 EL/SL PCIe2 4-Port/4-Lane Packet Switch' class = bridge subclass = PCI-PCI pcib11@pci0:8:3:0:class=0x060400 rev=0x05 hdr=0x01 vendor=0x12d8 device=0x2404 subvendor=0x0000 subdevice=0x0000 vendor = 'Pericom Semiconductor' device = 'PI7C9X2G404 EL/SL PCIe2 4-Port/4-Lane Packet Switch' class = bridge subclass = PCI-PCI igb5@pci0:9:0:0:class=0x020000 rev=0x03 hdr=0x00 vendor=0x8086 device=0x1539 subvendor=0x15bb subdevice=0x0000 vendor = 'Intel Corporation' device = 'I211 Gigabit Network Connection' class = network subclass = ethernet igb6@pci0:10:0:0:class=0x020000 rev=0x03 hdr=0x00 vendor=0x8086 device=0x1536 subvendor=0x15bb subdevice=0x0000 vendor = 'Intel Corporation' device = 'I210 Gigabit Fiber Network Connection' class = network subclass = ethernet igb7@pci0:11:0:0:class=0x020000 rev=0x03 hdr=0x00 vendor=0x8086 device=0x1536 subvendor=0x15bb subdevice=0x0000 vendor = 'Intel Corporation' device = 'I210 Gigabit Fiber Network Connection' class = network subclass = ethernet

  • Discussions about collaboratively raising money for a feature. To start a thread you must offer a starting price and be very specific on the feature you would like to see.

    457 Topics
    6k Posts
    S
    @winkmichael Thanks so much. I'll look into it some more, but you were a great help. What I meant by a 0 point release is that is it basically an alpha or beta version until it reaches version 1.x This to me has historically been an indication that it shouldn't be deployed in mission critical spaces or commercial spaces, but good to hear it is very active and very reliable. thanks again

  • Categories that are no longer active, but are present for reference

    10k Topics
    63k Posts
    M
    @Patch Yes, I have just confirmed that it is related to early DNS registration
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.