Great news logbuilder!

Yeah. Just put them behind something else that NATs for them if they need internet access. Otherwise just put them on a blank VLAN or a host-only vswitch. You are going to have to really be careful if you want to access one 192.168.193 network from the "real" 192.168.193 network. And you won't be able to just tell a host on the "real" 192.168.193 network to access something on the test 192.168.193 network using that address. I know of no way that can be done while also maintaining separation between the two.

@stephenw10: That panic is the result of booting the upgraded drive? What happens when you try to boot the memstick install image? What image did you use exactly. Steve It was actually bad USB drive…, i put everything on different usb drive and load it with memstick and restored everything.

Yeah, verifying the sha256 sum of the public key is an important step but so is verifying the sha256 sum  and signature of the actual signed data. My understanding of the chain of trust is that the "fingerprint" ie sha256 sum of the public key used for signing is included in the distribution. That's step 1. Step 2 is using the public key to verify the signature, digests.sig.  That's what the command "openssl rsautl -pubin -inkey digests.pub -verify -in digests.sig -asn1parse" did. The fact that it returned an asn1 encoded sha256 hash tells me the signature was valid. The problem arises with step 3. Step 3 is verifying the asn1 encoded hash matches the sha256 sum of the actual digests file. That's where the mismatch occurs. See this link. https://lists.freebsd.org/pipermail/freebsd-ports/2014-February/089751.html

I have a windows server 2012R2 hyper-v with pfsense, among other things. I suggest you use the following setup: Create two virtual switches. Call one WAN and the other LAN. For the WAN switch, use external network, since it's an external NIC. Do not select allow the management operating system to share this nic. For the LAN switch, use external network, since it's also an external NIC. However, do select allow the management operating system to share this nic, so you can access the hyper-v from within the LAN. When you create the guest for pfsense, create it with two network adapters, one connected to each of the switches. When you install pfsense, you will need to know the MAC addresses of the two adapters so you can select hn0 and hn1, accordingly.

Tried Ctrl+F ? Or you want to search in multiple aliases if a IP exists in any of them with a single search action.?.

You can ping 2.1 from your laptop because that's the interface IP in pfSense so traffic never has to leave the firewall on VLAN 10. That IP would be reachable even if it were on an unplugged physical interface. There is a layer 2 problem between the firewall and the hosts. We would need to see how the interface is configured in pfSense and how the switch is configured to know more. Steve

just an update, after trying many builds I tried yet another hdd (drive 3) and that worked fine…. I can guess that the initial drive might have been dying, the second one worked fine in other device and would accept the install files so pass on that one. anyway its back up and running on 2.3.4-RELEASE (i386)

Thanks for your reply. In the first case once without internet I was able to update it. Change the path of the repository in /usr/local/share/pfSense/pkg/repos/pfSense-repo.conf and download the entire repository from the internet and copy it to a local folder to which I point the pfsense and manage to update it. But it was in an earlier version of PFsense. Now it does not work for me. In the second case in previous versions there was an option in PFsense to be able to change the download path and existed to add a proxy if we were behind one. I can not put myself in front of the proxy because it is very above my company. Thank you I will continue testing until it works

glad you got it solved. for future reference, issue might be the USB. Try using an old 1 or 2GB USB

Ok, I wouldn't anticipate any problems doing that. You can certainly bridge two interfaces and have NAT from a third interface. As described in that thread it would be common to assign the bridge interface and put the WAN on that complete with one of the public IPs. Steve

I would not expect to have to add anything to allow this. By default the LAN interface allows out all traffic from LAN side clients. However if you've added a VPN client you may be policy routing some traffic. That might apply whether or not the VPN is up. I assume this breaks streaming even when you;re not using the VPN? Steve

Seems like you have the right idea. Your 'modem' is already passing the public IP to the current router so it will do the same with pfSense there. The idea with blocking 192.168.100.1 as a dhcp source is to prevent the modem giving you a private IP if it looses its cable connection for nay reason. They do that to allow you easy access to it in that situation but it can prevent pfSense receiving a real IP when the connection comes back up. You can still access the modem anyway. https://doc.pfsense.org/index.php/Accessing_modem_from_inside_firewall Steve

Hey, support team gave me available the link to download ADI Factory OS, solving within 30 mins. Firewall was up and running 15 minutes later. Thanks all

@belt9: For a fanless setup I'd recommend an Apollo Lake mini-itx board. J3455 is similar in performance to your current CPU on passmark. J3355 is dual core, similar clock speed to what you already have. Try the M300 w/ picoPSU for a case & PSU. http://www.mini-box.com/M300-Enclosure-w-Bootable-CF-Reader_2 http://www.mini-box.com/picoPSU-80-60W-power-kit You'll need a pci riser to fit it all in that little case, the J3455 will require an x1 to x4+ riser to fit your current NIC. Thanks for the input. I'm running a unifi lite ap and thinking of a second one so that why I was thinking of getting a unifi security gateway

Happy to report that the VPN router has been stable since the update. So if you are experiencing issues on a device that has seen multiple updates over the years, consider a bare metal rebuild.  It does not take long and can export and import all of the settings easily.

Looks to me like that second disk (ada1) has failed. There probably won't be any way around that without physically replacing the drive.

I will be keeping an eye out for 2.4.1 with 11.1. Thanks again for the info, though  It was helpful. –DT

@Derelict: Yeah the management VLAN to unifi gear can be any VLAN but it has to be untagged (the PVID) to the APs/cloud key/"controller" app/etc. There doesn't have to be a wireless SSID on it at all. When you set an SSID to have a VLAN traffic on that SSID will be tagged to and from the switch. If you do not set a VLAN it will be untagged along with the management traffic. Found the appropriate link to this - it makes sense now, but it didn't when I read it before setup: https://help.ubnt.com/hc/en-us/articles/219654087-UniFi-Using-VLANs-with-UniFi-Wireless-Routing-Switching-Hardware Initially you need to adopt your UniFi access points or switches over the native untagged VLAN, and this will be the continued requirement. That being said, they do support L3 management, so your controller can be on a different L3 network (or remote, etc.). I didn't realise that "adopt" was a Unifi "reserved" word. Thanks again Derelict