Thanks for the info.  I'll try a live linux distro of some sort and see if I can get the card to respond.

I don't know what happened to you, but I can verify that it worked with 2.3.2-RELEASE. Regards Nagilum

@kpa: As far as I know the boot loader serial port parameters have always been customizable via a /boot.config file. Has this really changed recently? In NanoBSD since 2.3, this file resets to defaults every time you reboot, and it has been told us in these forums that this is by design like so. i had to switch to full install on embedded hardware because of this.

Thanks for the quick response. What mSata SSD/flash should I get ? What do you guys recommend ?

Thank you!! That was exactly what I was looking for! I was Googling around and never found that (didn't think to try 'serial console') Thanks again!!!

nevermind it's a base64 encode

What is the IP address, netmask, and gateway being assigned by DHCP? What are the IP addresses you are trying to assign to IP Alias VIPs? PM them if you want.

Please see: https://forum.pfsense.org/index.php?topic=119934.0

@firefly: Linode does not officially provide support for any OS other than Linux. Some guides for installation of FreeBSD do exist and the install does work. I'm installing pfSense v2.3.2 on Linode (KVM) VM in paravirtualized mode (have also tried full virtualized). The installation completes. Linode VMs are provided a public IP (WAN) and and optional private IP. The problem is that a single network interface is used (single MAC). On Linux the public and private IPs are configured as "eth0" network interface and "eth0:1" sub interface. When pfSense boots on Linode VM only a single network interface is configured "vtnet0". I can then manually create the sub-interface as follows: "ifconfig vtnet0.1 create" I then configure the private IP address as follows: "ifconfig vtnet0.1 inet 192.168.180.200/17" If I launch the Webconfigurator, I can see both network interfaces, so I know I'm going in the right direction. My questions are: In pfSense, how do I manually restart the network and routing services following the creation of the sub-interface and private IP assignment? How do I save the above sub-interface configuration and private IP assignment so that they persist following a reboot? In Webconfigurator, I can assign the sub-interface "vtnet0.1" as LAN. I disable IPv6 and assign an IP. When I try to ENABLE the sub interface an error comes up the DHCPv6 Service is running. I attempt to disable IPv6 from the WAN interface and the Webconfigurator appears to hang and lose the configuration entirely. Lastly, is use of pfSense with two interfaces where one is actually a sub-interface an security concern (essentially a FW on a stick) - it is not intended for any production use. Any guidance/suggestions appreciated. Hello, I am in the same situation, I need to have a firewall in front of my other vm, but I need two interfaces wan and lan . Have you made any progress? my best regards!

Ironic, I manually rebuilt the config and when I added the Shaper it crashed.  the 2.2.6 Shaper must not be compatible in 2.3. Thanks!!

Hi, Because in my home pfsense have 4 LAN interfaces, I wanted to have all CISCO AP on the same physical interface LAN trunk configured with 2 VLANs for Private-Guests wifi. First I configured 2 interfaces on /25 range but I don't like to have IP changed from one segment to another one when AP is changed. Then I was thinking to bridge the interfaces but is no point to add this load to pfsense, I did not have a managed switch at home, so I made an experiment: I used a dumb switch to connect all AP CISCO configured with 2 VLANs and the LAN trunk interface with the same VLANs of pfsense. Result SUCCESS ! everything work perfect, looks like I don't need a managed VLAN switch just to pass/carry trunk traffic to all ports of the switch; I tested: 1GB switch DLINK GO-SW-5 and 100Mb TP-LINK TL-SF1005D, both work OK to carry trunk traffic.

The web server on pfSense is not intended to be used for anything but pfSense, not for hosting custom pages/code. If you absolutely must host a web server on the firewall, you'll have to setup a separate instance manually with whatever custom config you want. Dig around the forum and you'll find some examples where people have done just that.

Indeed and you should switch now if you're still running 32bit before it becomes an issue. 2.4 is still beta….. for now. Steve

@Jon: Is this some sort of mirror issue or something else? Is the issue still happening?  If so, we'll need some more details and any diags you've already tried It sees to be a connectivity issue, as it's intermittent and only seems to affect pfsense. The only oddity now are the version numbers, as shown in the images above, which is still happening.

It looks like it's having trouble reading from the CD-ROM there but I could be mistaken.