@Jason: Can I just create entries for those on the System Tunables page? No, loader variables are not the same as sysctl tunables.

@bainwave: Thanks bob for your speedy help. few more questions still hunting me.. 1. I have  CISCO Catalyst 2950G switch, can I club all my 3 broadband connections with a single NIC? if yes, how could I achieve this? All my broadband connections are having a pool of (20) public ip's. 2. Now can i configure all my public ip's into this pfsense in order to run my show? Am in a work group environment, can I control the users & computers from this pfsense? Once again Thanks for your advise. You need to setup VLANs on pfSense upon the first boot up.  Configure 1 VLAN each for the 3 WANs and 1 LAN. If for example, you use VLAN 10, 20, 30 and 100 for WAN 1, 2, 3 and LAN respectively; then you continue with the interface setup assigning VLAN 10 for WAN, VLAN 100 for LAN; the remaining interfaces can be configured from the webgui. Let's assume you use ports 1, 2, 3 on the switch for WANs 1, 2 and 3 respectively.  You'll then need to configure Port 1 to be native VLAN 10, Port 2 to be VLAN 20 etc.  Now, these ports need to strip the VLAN tag on egress and tag on ingress (default VLAN ID per port). Next, assuming Port 4 is connected to pfSense, you'll need to trunk VLANs 10, 20, 30, 100 to Port 4. The rest of the ports that are connected to LAN will then need to be in VLAN 100 (tag on ingress aka default VLAN ID) and strip the VLAN tag on egress. eg. In priviledged access mode type: vlan database vlan 10 WAN1 vlan 20 WAN2 vlan 30 WAN3 vlan 100 LAN exit copy running-config startup config configure terminal interface fastethernet0/1 switchport mode access switchport access vlan 10 interface fastethernet0/2 switchport mode access switchport access vlan 20 interface fastethernet0/3 switchport mode access switchport access vlan 30 interface fastethernet0/4 switchport mode trunk switchport trunk allowed vlan 10,20,30,100 interface fastethernet0/5          <–--  repeat bolded section for all the ports you need to be on LAN switchport mode access switchport access vlan 100 end copy running-config startup-config After that you can configure the remaining VLAN interfaces in pfSense for your WAN2 and WAN3 links accordingly.

Thank you very much Nachtfalke!

@wallabybob: Why not backup the config file through the web GUI: Diagnostics -> Backup/Restore click on Backup/Restore tab This uploads the config file to system running the browser: you can copy/save it to your preferred destination. Hi wallabybob, thanks for reply. Looking to actually run the config from another location not save it. I want to be able to run the config from a "write" protected device.

Why wouldn't changing the cables around "fix" the problem? unplug cable from em0 unplug cable from em1, put it in em0 plug other cable into em1 problem solved, now both boxes match what they're using em0 and em1 for.

dmesg is correct. We do not use the stock e1000 driver from FreeBSD 8.1-RELEASE (which is what 2.0 is based upon).

Thanks for your help :)

Change some disk options at setup. For example, enable AHCI sata mode.

I have restarted my pfsense box from scratch with a new config file and now everything works!

[SOLVED] This problem only occurred when I manually entered the interface names.  When I allowed pfsense to auto detect the interfaces, setup continued as expected.  Hopefully this information is useful to others.

@marcelloc Thanks! I'm also reading this http://doc.pfsense.org/index.php/Upgrade_Guide#Embedded

Then you don't have to worry (other than the fact that your ISP is handing out dubious advice).

OK This doesn't work (or is so slow that you think it's not working). bonded ADSL  –>  pfSense Router (manually configured) -->  laptop (DHCP configured from pfSense) This does work. bonded ADSL  -->  netgear router (manually configured) -->  pfSense Router (DHCP configured by netgear router - the setting in pfSense of 'Allow DNS server list to be overridden by DHCP/PPP on WAN' makes no difference if it is on or off - but it has been a bit faster, 10%, with it turned off) --> laptop (DHCP configured from pfSense) I doesn't make sense that I need another router to make it work - I have used a different ADSL source that can DHCP pfSense and it works fine on that.

One other "failure to migrate" occurred during the upgrade - my WAN interface is PPPoE into a DSL modem (AT&T DSL) and was set to periodically reset every 24 hours to get a new IP address. After upgrading to 2.0 the periodic reset settings were lost.

not easily or in time. The strange thing is that it works on a different connection - so the hardware must be OK

Hi all ! @loziopigna: Hi all. I have try to install pfSense-1.2.3-usbinstall.img.gz on usb key using dd and USB Image Tool but when start pc whith usb key recived error: Boot Error Any suggestions? Try to install PFsence from USB-disk, but got same as above error, can you give some advices ?

The setup is; Bonded ADSL line in with about a dozen usable IP addresses. About 18 internal vLans (which must be totally closed from each other - except for the fact that one, vLan64, has to be available from all the other vLans). Most of the vLans will have a dedicated public IP address, but a few will have to share. And I need to get this working today (it's 1220 here in England)!!

Yep, have set up dns addresses correctly - now have the situation where if i try and ping google from a laptop connected to the pfSense box, it gets the correct address, but times out on the pings.  I can get pfsense to run a ping itself from diagnostics and that works fine. Sharedband is a bonding setup (in UK here) where you get multiple lines which go into a modem/router box.  Each of these routers outputs to a sharedband box and the sharedband boxes all output to a normal switch - you then take a feed off of another port on the switch to give you your bonded broadband.

@jilingshu: hmmm…. I have already tried it and found there r so many bugs in those snapshots... Even some features which work well in 2.0-RELEASE are broken in 2.1-DEVELOPMENT such as Captive Portal... :-( Only thing that doesn't work in 2.1 is captive portal, everything else is little different except with IPv6 support, all works well.