PfSense VMware-Ready Virtual Firewall Appliance Feedback
-
Are these errors coming from the wizard? Or from System > General Setup and Interfaces > WAN?
-
They're from the wizard when you first connect and config after assigning IP addresses. The first page of the startup wizard (going from memory here) prompts you for hostname and NTP source only, and that's where error #1 happens. Edit the hostname field and you get that error as soon as focus changes from that control. Next is the WAN page, which always has a blank Upstream Gateway field even though it was configged during 2) Set interface(s) IP address at the text menu.
-
@KOM:
- The default hostname is pfSense. As soon as you try to change it to anything, a pop-up informs you that it's an invalid hostname. Even just adding the number 2 to the end gives this error.
I just dismiss the pop-up.
-
More feedback on the virtual appliance, different question from OP.
One thing I notice is that the defuatl disk size is 5Gb. To make this match my production 2.1.5, I need to make this 25Gb. I set this in vmware before booting the appliance, but (as I expected) the appliance doesn't dynamically re-size the volume. Is there a method to re-size the volume after it has been turned on? If I were working form the ISO, I'd reset and go through the initial installation, but of course this defeats the purpose of loading the appliance…
I have my WAN configured to do DCHP. I notice that after running through the first time wizard, the DNS servers are not associated with any gateway, not sure if this is normal or not. I also notice that Status:Dashboard reads 4 DNS servers; the two I entered are at the bottom, the localhost ip 127.0.0.1 is on top, and google's 8.8.8.8 is second. I know that turning off the DNS resolver will get rid of 127.0.0.1, but I can't find where to remove the 8.8.8.8 - I certainly never entered it, and it is not listed under System-> General setup. EDIT - I downloaded a copy of the config.xml, and 8.8.8.8 isn't anywhere in it. So this is even stranger than I thought.
When deloying this, I saw that the defualt Ethernet adaptor was vmxnet3 - good show :) This raises a few questions for me: I see that the VMWare tools are listed as 3rd Party/ Independent in Vcenter. I see that the OpenVMtools package is NOT installed when I look at the packages in the web interface. What tools ARE installed, and how are they kept up to date in this version? SHould I NOT install the Open VM Tools Package? When I look at the Status: Dashboard screen and the Interfaces widget, it shows my speed as "autoselect". I am running 10Gb interfaces in this cluster, should I not see 10 Gb here? Is there a change I need to make? When I go to the speed and duplex setting under either the LAN or WAN interface, the only options are Default and autoselect.
That's it after inital deployment. Thanks for doing this image!
-
One more thing I've discovered. We are running ESxi 5.5, which may or may not beimportant here. After a few minutes, the console in Vcenter stops responding. By that I mean that when I log in form a remote host, it does not scroll the screen. When I click into the consoel window, it does not respond to keyboard input.
If I enable SSH, Ic an log in jsut fine and access the menu. As I am a service provider, I can't havethe console, our accesss of last resort, randomly become unavailaable. So far, the only way I've been ale to fix this is to reboot. From Vcenter, I sissued the "Shutdown Guest" command, and while the console didn't report anything, my SSH session gave me the "System going down IMMEDIATELY" message. That said, the box has not shut down or even rebooted after about 10 minutes of waiting. And I can't re-establish an SSH connection. I finally had to issue a Power Off" from Vcenter, which will likely cause fschk to run on the next reboot as files wouldn't have closed gracefully.
Any ideas on what I can check? Thanks!
-
@KOM:
- The default hostname is pfSense. As soon as you try to change it to anything, a pop-up informs you that it's an invalid hostname. Even just adding the number 2 to the end gives this error.
That appears to be due to the capital letter S in "pfSense". If you put in an all-lower-case hostname it does not complain. That isn't specific to the VMware wizard though. I opened a ticket for it: https://redmine.pfsense.org/issues/4712
@KOM:
- After giving my WAN a gateway when assigning IP addresses to my NICs via text menu option #2, the wizard has a blank entry for upstream gateway during WAN config.
Few people use the console to set a gateway and then hit the wizard, seems an odd edge case but I did confirm it. Added as https://redmine.pfsense.org/issues/4713
-
You can resize the disk as follow in VMware.
- Download gParted, upload this in your ESXi server datastore.
- Shutdown the VM.
- in VM settings grow the disk to required size, save and go back in settings.
- Assign the gParted.iso to the cdrom, and check if power is ticked on, otherwise it won't boot in cd.
- Reboot the VM, make sure it boots with gparted, select in gparted the correct disk…
- Then you can resize the partion, just drag the bar to extend to the new space you assigned to your VM harddisk.
- Apply new settings...
- unmount gParted, in settings remove the iso you assigned, turn power off for cdrom, reboot.
That should do it.
Regards hostnames, best is always to use lowercase.
-
Few people use the console to set a gateway and then hit the wizard, seems an odd edge case but I did confirm it.
:o When you first configure your WAN, it asks for the gateway. I don't know how anyone can miss it unless everyone uses DHCP on WAN.
-
You can resize the disk as follow in VMware.
- Download gParted, upload this in your ESXi server datastore.
- Shutdown the VM.
- in VM settings grow the disk to required size, save and go back in settings.
- Assign the gParted.iso to the cdrom, and check if power is ticked on, otherwise it won't boot in cd.
- Reboot the VM, make sure it boots with gparted, select in gparted the correct disk…
- Then you can resize the partion, just drag the bar to extend to the new space you assigned to your VM harddisk.
- Apply new settings...
- unmount gParted, in settings remove the iso you assigned, turn power off for cdrom, reboot.
That should do it.
Thanks very much!
I grabbed version 0.22.0 of GParted, and booted into it jsut fine. It sees the additional sapce, but I can't expand the file system because it says the File Sytem is "Unknown." Have you had luck with any particular version of GParted? I seem to already have two other copies, on version 0.8.x and the other 0.9.x - very old…. -
I looked in my datastore and found this version, gparted-live-0.20.0-2-i486.iso
-
Have you had luck with any particular version of GParted?
According to gparted doc, it does not support resizing ufs, only move and copy
Attachments seem to be a problem so
http://gparted.org/screens/gparted-file-system-support.pngYou can try a live resize with gpart in pfSense
$ gpart show => 63 16777153 da0 MBR (8.0G) 63 16771797 1 freebsd [active] (8.0G) 16771860 5356 - free - (2.6M) => 0 16771797 da0s1 BSD (8.0G) 0 16 - free - (8.0K) 16 14674629 1 freebsd-ufs (7.0G) 14674645 2097152 2 freebsd-swap (1.0G) -
Thanks again. I grabbed that version from sourceforge, no dice. It doesn't recognize the partition type so it can't work with it. I tried doing this in single user mode using gpart, but that doesn't work either. I'm going to try goinging through the OVA deployment again, and editing the VM before finishing the wizard, see if it will work. I doubt it, but it's worth a shot.
-
I tried doing this in single user mode using gpart, but that doesn't work either.
Care to define gpart doesn't work?
-
Sorry, that was a terible thing to leave hanging, you are right. I actually HAVE manged to get it to work (I think) with gpart, but I was attempting to follow these instructions and having no luck:
http://unix.stackexchange.com/questions/117023/expanding-the-disk-size-on-pfsense-under-vmware-esxi - turns out I was missing the "a" on the end of the growfs command, and there is a reboot that I had to do that is not in those instructions.
Now, I know that growing a live partition is supposed to be possible in freebasd 10 and up, but I haven't found anyone doing it on the pfsense forums yet, so I just booted into single user mode JIC. I make NO promise that this is correct, this is just what worked for me!!! Backup everything! You have been warned!Here is what I ended up doing - I'm going through it again on a second firewall to make sure it wasn't a fluke.
On boot up, hit the space bar as soone as you see the pfsense ascii art "Welcome to pfSense" menu.
Choose option 6 to configure boot option, hit m to turn on safe mode, hit s to turn on single user mode, then hit Enter.The thing boots, and eventually asks you for the full pathname of shell or hit RETURN - just hit return (Enter)
you should now be at a # prompt. cd /sbin to get into the directory with gpart.
do a ./gpart show. This is what I get:
What I took away from this were the names da0 (/dev/da0) and da0s1 (/dev/da0s1a=freebsd-ufs and /dev/da0s1b=freebsd-swap). I honestly don't remember where I saw the da0s1a and s1b, but I have seen it and it becomes importnat later :)
so, the Master Boot Record (MBR) has 20 gigs free. We need to get that combined with the 5G partition listed above it.
./gpart resize -i 1 da0
followed by a
./gpart commit da0s1
like so (minus the mistake where I forgot the ./)
if we do a ./gpart show again, now we see this:
More like it, da0 is now 25 Gigs.
Now, see that all the free sapce in da0s1 is after the swap file. so, we're going to delete the swap partition (and re-create it later):
./gpart delete -i 2 da0s1
results of that and another ./gpart show
EDIT: sory, the source of this screen shot broke :(
now, I have 4 gigs of RAM in my system, and so I wnat an 8Gb swap. I'm going to tell the system to re-size da0s1 to (25G-8G) = 17G
./gpart resize -i 1 -s 17G da0s1 the ./gpart show
Now we have re-sized the partition, and we have got 8G left unallocated at the end for the swap. Before we do that, we need to grow the filesystem:
./growfs /dev/da0s1a
at this point, that command gives me a "operation not permitted", so I type exit and it "finishes" booting into pfsense. I then choose option 5 to reboot.
Once again, as soon as the ASCII art menu comes up, hit the spacebar to prevent further booting. Again choose option6, then hit m and s followed by enter to boot into single user mode.
This is where it might be a little scary - the system won't boot into the shell - instead, you see this:
simply type in
ufs:/dev/da0s1a
and hit enter, then hit enter again to get to the # prompt.I change into /sbin again, and issue ./growfs /dev/da0s1a again:
and a gpart show after:
Now we need a swap file again:
./gpart add -t freebsd-swap da0s1
After that, I activated the swap by issuing ./swapon /dev/da0s1b , but rebooting should take care of it.
I type exit and hit enter to reboot, then do an option 5 once the console menu comes up to reboot again. After a normal boot, choose option 8 to get to the command prompt and do a gpart show (it's in the path now), and you should see your expanded partition.So far, it hasn't given me any trouble. If I've made any obivous mistakes in here, please let me know.
EDIT: now with actual pictures
-
I have tried it myself and you are right, it seems FreeBSD is using UFS and gParted is only able to detect it.
Sorry about giving wrong advice :( It seems Freebsd only has those 2 commands, gpart and growfs.I use sometimes Clonezilla, perhaps you can use it to clone it to bigger disk, but please I am not sure this time.
The 5GB disk seems a bit tidy, not sure how this would work ut on my VMware machines with loads of traffic and additional software in pfSense installed… I am a bit worried about that. Did you find out if you could do something with the .ova file?
-
ok, i added 15GB to the disk, if I recall in right way, I did as follow.
In vmware I added the 15GB extra to the disk.
Login shell in fSense.gpart show
I can see the 15GB extra space but on wrong place da0 instead of da0s1
gpart resize -i1 dao
gpart commit da0s1 [commit the change]
gpart show [now I can see the etra space and correct place, but we need to add it to the ufs partition. sadly in my case the swap is in the way for a nice aligment, so i got rid of the swap partion, then resize i1 [index 1] is the ufs partition we want to extend but we add only the space we want minus the swap as we need that back 2GB it was in my situation…swapoff -a [disable swap]
gpart delete -i2 da0s1
gpart show [now you see the swap gone so, we can extend the partition]
gpart resize -i1 da0s1 -s [your size to add in notation xM xG]Done, add your swap back and reboot.
Hope this helps.
** Don't do this with a mounted file system ;-)
I didn't mind to do it as I wanted to help you.Oops, whilst I was busy to do this you worked it out yourself as well…. well done!
-
Not sure if you really need 8GB swap, with 4GB RAM and 4GB Swap you will run very smoothly.
The rule twice RAM = SWAP is a bit old fassion ;-)
But it might be still good with FreeBSD and pfSense in combination with each other.
-
Heh. You are probably correct there. But the way the image came was with 512Mb of ram configured, and a 1Gb swap partition - so I simply maintained the same ratio.
When i initially created my 2.1.5 image that I use in "production", I had 8 gigs of ram and the setup reserved 5 gigs of disk space for swap, and I simply chose the defualts presented to me.
-
I have no idea why a VMware ready image is so 'limited' in resources, after all when using it in our production servers we want to add quite a lot to it. Just curious how different this image it is in comparing it with a 'normal' VM installation, does it have some intellect on board. I noticed your remark about the NICs and VMXNET3, but for that you need VMware tools and not sure if the open-vm tools can address that. Have you done some proper testing?
-
I have no idea why a VMware ready image is so 'limited' in resources, after all when using it in our production servers we want to add quite a lot to it. Just curious how different this image it is in comparing it with a 'normal' VM installation, does it have some intellect on board. I noticed your remark about the NICs and VMXNET3, but for that you need VMware tools and not sure if the open-vm tools can address that. Have you done some proper testing?
FreeBSD 10.1 includes drivers for vmxnet3, the tools are no longer required for that. The VM appliance comes preconfigured for vmxnet3 interfaces.
5GB is not "limited" for what most people use pfSense for inside or outside a VM. It may not be enough for a large web cache but that is not as common a role as one might think. Adding a second disk to the VM is another option, though also manual, it would likely be less work/fuss than resizing the existing disk/slice. Just partition/newfs the second disk, make a mountpoint, and add it to /etc/fstab
In terms of RAM sizing it has to be fairly low to play to the lowest common denominator but that's simple for people to change.
