@rdsmith24 also, use /boot/loader.conf.local as /boot/loader.conf gets overwritten.

@travelmore yeah that would be the new default fqdn.

If you access via IP, just make sure you add IP you use as a SAN. But you can start accessing it via the fqdn if you want as well.

I had created mine way before home.arpa was a thing.. And I use local.lan as my domain, kind of in the process of changing over.. I access my nas with home.arpa

homearpa.jpg

See my browser trusts it, and using different domain... Once you trust the ca, you can create certs it trust for any fqdn, any IP, etc.

@dobby_ from what I've dealt with and seen so far. Looks like it's going to be a while before this gets fixed. One cant fix an issue until they acknowledge it's an issue. and thus far @jimp has spent more time denying that this is an issue jumping to conclusions without enquiry
Screenshot 2023-02-26 175306.jpg .

@stephenw10 yea the WAN 4G router should no be doing any bridging as it is not in bridged mode.

I'll run a cap next time, I might have actually grabbed a cap I'll check

@mr-castoro -- No problems with my SG-1100 and DNS but I use the "Forwarder" and not the "Resolver" and I point the Forwarder to my two Pi-hole IPs. Works great that way!

Also, instead of pointing it to a Pi-hole, you could just use: 9.9.9.9, 1.1.1.1 or 8.8.8.8 or some other external DNS.

Reimaging a system (beit from a USB image for a Netgate device or reinstalled OS) will overwrite all past data including BEs.

Upgrades, factory resets, etc. will not.

@zululander you’ll have to create it as a new interface
https://docs.netgate.com/pfsense/en/latest/vlan/configuration.html#web-interface-vlan-configuration

Then use that instead of WAN. I haven’t done that myself…see if you can find a thread for your ISP. Might be better to start another thread too, so people find it by title.

@gwaitsi They can and it depends on need…we usually limit logging unless debugging something.

@stephenw10 said in pfSense Plus Home:

We have had various support models over the years. At one time we did have incidents like that but was not really viable. What counts as an 'incident' is hard to define accurately.

True, can understand that. I would have suggested some sort of "up-front" agreement and then least path to fulfill that, but way easier said than done.

@stephenw10 I think I have 250 down, so yes, should be plenty of bandwidth left. And the passin-traffic, I checked this while watching Youtube, and well, it comes really close. So don't think the 2.7Mb is what made things stutter... Almost as if someone pressed pause/play really fast (which I hope is not the case)
Once I sat on my remote, but don't think that was it this time... :D

@josephchrzempiec
Check my backup box in my sig. Has worked great for several years but just replaced by actual hardware. I use 2 cores in the VM, just figuring if one's busy, there's always the other. With only one, the GUI is way too slow. Running on a 2008 vintage quad core (my main server/workstation, lol). My new FW is an i7 (lol x2).

@steveits Thank you for your reply. If I take our pfsense out of the setup and only using their modem and router (with DHCP), everything works. I can get in/out traffic and IPs all pingable. Only when we put RAC2V1K router in bridge mode and trying to put pfsense behind it, we can't ping outside of our gateway.

I solved setting dns in dhcp relay setting

thanks

@jimp

thank you for your help, problem solved (reboot did fix it)

I am guessing it only happened for certain UPS models and connection types, my old SmartUPS 1000 is using modbus protocol over serial (with a usb rs232 dongle)

Most people are probably using a direct USB connection with the usbhid driver but I never got that to work reliably with my UPS, it would stop responding to polling from apcupsd after a couple days or weeks. Maybe the temperature parsing acts differently depending on the UPS type and connection method, or maybe some UPSes don't report a temperature at all.

@stephenw10 said in Can't Save LAN Interface Settings - IPV6 Configuration Type set to None:

It's possible to get into a chicken/egg situation with the IPv6 DHCPv6/RA server. It can only run on an interface configured with IPv6 so if it's enabled you can't set LAN v6 type to none. However if that does somehow get set to none the tab where you would disable those services is hidden.
Hence you have enable v6 on LAN in order to disable it!

It used to be possible to hit this if you set the interface at the CLI but that should be fixed:
https://redmine.pfsense.org/issues/11609

Steve

Thank you for posting this where I finally found a solution via search.

I had the exact same issue as the OP, discovered when going through each and every page to verify I did not have an error somewhere in my settings. This issue came up and it has been driving me crazy. Long ago I had ipV6 enabled but abandoned it since I don't see that I need it at this time.

Your solution guided me, with much effort (I had to find an ipV6 addr to enter to enable) then I found on the RA page of dhcpV6 server the 'enabled' toggle for RA.

This has been a long, frustrating journey and thanks again for your comment.

I get 49 kw/s, and I'm using pfblockerNG (not logging DNS replies) and remote syslog (with logging to the firewall disabled).
Based on the other thread, the count would be: 49 x 60 x 60 x 24 x 365 = 1545264000
Which is 1.5 TB per year.
My SSD, ADATA M.2 SATA SU650 120GB can write 70TBW, so based on that, I would be able to use it for around 45 years.

I wound up getting a new image from support. I tried to recover from the autobackup thing but I didn't have my device ID, so make sure to save that along with your password. Luckily, I had backed up config.xml manually as well. All is working again but I wish I knew why it broke. I may only be a home user but this caused some chaos in my household today.