a) don't think so, not until this support will be in FreeBSD itself
b) there is would no real benefit in such configuration

https://forum.pfsense.org/index.php?topic=85797.0

Had #2, but #1 fixed it.

Thanks!

hi, i write a solution for the problem:
https://forum.pfsense.org/index.php?topic=85797.msg475906#msg475906

I've decided to go the third route. I'm going to ditch esxi, create an ubuntu 14.04LTS host, install nginx and create 12.04LTS 32bit dockerfiles with Airtime installed, then deploy this for 50 instances and configure each with a unique port in docker, and then use the reverse proxy to forward to translate each subdomain to the port and vice versa.

You really should be running a 2.2 RC snapshot now.

CARP has been fixed with the synthetic driver.

No need to shut down machine before copy vmdk and vmdx. Just take a snapshot before copying them and the mahine will be up and running when you take backup/copy files.
Remember to delete the snapshot afterwards :)

Thanks for the follow up.

Codemaster, first an apology for an error on the diagram of the network.  It shows the internal router address as 192.168.0.1 when it should be 192.168.1.1.

Although I would like to follow the first option so that pfsense manages the ADSL connection, I do not think it will be possible although I am wiling to try as I can always revert.  I have the login details for the ADSL but when I tried to allocate 192.168.1.1, it of course clashed with the existing router address.  Furthermore, I do not know how to stop the box managing the connection as the command interface is limited on the box and I cannot see anything to disable the connection or to bridge the router (which I assume I would have to do?).

In the diagram you have changed the link of the router to go direct to the pfsense box but although I can do this in a virtual sense (i.e., through address mapping) I cannot do it in a physical sense as I need to use the four ethernet connections in the box for the IP phones and other items.  Can you confirm that your revision is intended as a virtual not a physical break?

The IP phones and power link and connection to my office are essential and using this box is the only way for them to have a wired ethernet connection (i.e., not wifi or power link) without me rewiring the house which I do not want to do.  Also, the power link has to be connected to the router (pfsense or SFR) not passed ver wifi as your diagram suggests.  I would need to wire a second (physical) cable connection from the pfsense server back to the SFR router position with a switch if your diagram requires a physical break as shown and again, this would be very difficult to achieve.

What DNS settings should I use?  At the moment, AirVPN is set up and working on the pfsense router and the DNS is set to its requirements and should remain so I assume those are the ones I should use.

I am not really understanding why you want to amend the wiring (if that is what you are proposing) as I thought this could be managed through subnet addressing which is really all I am now trying to understand and achieve.  Whenever I set a separate subnet i cannot ping from one to the other and that is the bit I do not understand and there seems to be several ways to achieve it including iptables, NAT and routing, all of which seem to require adjusting the netmask?.  This is the part I need to understand better and apply to my network

Also, having looked at your instructions (and tried it) I could not see how to enable the pfsense box to manage the WAN service dial up.  Is it automatic?  Does it require a reboot?  Is there something else I need to do to start it if I use it?

I have manage to get it all working again on my single network but would still like to continue to try to set it up via subnets if possible.

Geoff

@Jamerson:

i've noticed your Pfsense VM doesn't have a Vmware Tools installed !

Yeah i've had problems with vmtools for pfsense, but thats not the issue here since i've had it running before with the same issue, unfortunetly :/

I read that as his comment was the legacy drivers are a problem.

Too bad I can't read as well.  That's exactly what he meant.  I had it backwards.  I thought he meant that the legacy driver was better than the synthetic one that Zootie guy hacked together.

I moved my post: https://forum.pfsense.org/index.php?topic=85168.0

I see, thank you for the explanation. I'll take a look at Esxi.

But the "ifconfig mtu" commands are temporary aren't they? Wouldn't they be reset to whatever setting I have in the GUI? (which also hasn't worked for me after a reboot).

Any idea why I might be seeing different results on the native hardware (which was also without a reboot)

M

Don't mention it, and don't take anything said above personally.  You gotta roll with the punches in the tech trenches.

Yes, that was the issue! Thank you!

Weirdly enough, when checking for Updates in VB it said that it was up to date. I had to manually download and replace the version. After setting up the VM again, it finally works.

I think this might be related to our issue https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=165059

Another thing that we noticed, if we enable TSO on the pfSense vtnet interfaces, all traffic to the VMs on the same host as the master pfSense firewall gets stuck. Traffic going via the master firewall but to a VM on a different host is fine.

@johnpoz:

No B is Bytes, b is bits - that is how it is everywhere!!

http://en.wikipedia.org/wiki/Bit

the lower-case letter b is widely used as well and was recommended by the IEEE 1541 Standard (2002). In contrast, the upper case letter B is the standard and customary symbol for byte.

doing /sec vs ps is 2 different ways to say the exact same thing per sec.

So your doing it wrong ;)  And I can not believe you have ran into confusing before ;)

My bad. I'll be more clear in the future :D

-Jamie M.