well the command is as follows tcp_outgoing_address

Ok so I eneded up putting a switch between the two, I know that LACP  provides fault tolerance and load balancing but it will not increase my bandwidth, each link will be treated separately, if I wanted to increase bandwidth I would use a round robin scheduler on both ends. The reason I have lacp between both pfsense boxes is to provide another link to load balance tcp connections as well as vpn traffic through. The main reason I posted my question was to find out whether pfsense could be set to setup a LACP link between two pfsense boxes without additional hardware. I soon found out that this was not possible. And yes a seperate IDS on each box. After adding the switch to my network design this has opened up a third location to stick an IDS Kind Regards. This issue can be closed

look this.  :( Help me! haha [image: 5b6c1a67-2beb-4bf2-8925-6c67ae66c31b.jpg] [image: 5b6c1a67-2beb-4bf2-8925-6c67ae66c31b.jpg_thumb]

You guys are right! I missed it, but even with 10.2.0.1 I have the same issue :/

@johnpoz: "172.16.220.220 /16" Why would you use such a large network?  Do you have some 65k nodes there? yeah there are a lot of connecting people diagram is attached [image: nw.png] [image: nw.png_thumb]

Yes. You can do both, however. Some routes across a transit network tagged to the L3 switch and a VLAN tagged to the same switch but no L3 there.

@phil.davis: Click the "tool wrench" on the System Information widget title bar to access the settings. Select all (or the items that you want displayed). Press Save. I am not sure how that would unselect all the items by itself, but maybe there is some upgrade path causing an issue there. That was it, thank you. I am not sure how I managed to hide everything in the first place but, either way thanks.

Post yours settings of squidguard. Please

https://doc.pfsense.org/index.php/Installing_FreeBSD_Packages

Update: It appears that the current Netgate image of pfSense, with it's "AWS VPC VPN Wizard", configures the IPSec connections in a way that is no longer compatible with AWS. I guess AWS changed something since this wizard was created. AWS said that both tunnels created by the pfSense wizard should not be active at the same time, and that one should be in standby. I opened a ticket with Netgate support about this on May 4th, and hope to get this resolved before too long.

Status, Monitoring. Use the wrench icon to configure. Status, system logs, click on the funnel icon top right.

Well that is useless switch.. Either get a 2nd dumb switch or get a smart one that support vlans so you can isolate your 2 wan connections and put them on different networks.. Why do you have them connected to a switch anyway.  Can you not just directly connect your isp device to pfsense interface? If possible bridge this isp device so you directly get a public IP on pfsense.  Or use 2 different transit networks.. BTW - work updated to visio 2013, wow the icons are ugly ;) [image: 2wans.png] [image: 2wans.png_thumb]

[image: crystal_ball.jpg] I see something else between pfsense and ISP, what is that? Is it modem?

That's a traditional symlink on FreeBSD systems to the source tree.