Having the same issue with a couple new Intel 1000 PT network cards.. did you ever fix it?

@stephenw10:

If you need to upload the upgrade file manually you need:
pfSense-2.0.1-RELEASE-4g-i386-nanobsd-upgrade.img.gz

Thx for your help. After a few mouse click I'm now at 2.0.1 without trouble/hassle.

PfSense is great!

That's not normal for official release versions. Generally would indicate you're not actually getting the update file, maybe pointing to the wrong update location. Go to System>Firmware, Settings tab, pick the stable release for your current architecture, save, try auto update again.

cheers all for the help.

adding that firewall rule has worked, i now have a fancy access point :)

Maybe this is in the wrong section of the forum.

I tried to do a clean install of 2.0.1 RELEASE amd64 and was locked out. (in a VMware ESXi 5.0 environment) I didn't do anything CLI related - just saw that the console was showing WAN not pulling a DHCP address and LAN wasn't able to push DHCP to client so I gave up.

Installed 2.0 RELEASE amd64 and it works fine - but then when I upgrade back to 2.0.1 RELEASE amd64 I have the same issue with the web pages not loading properly and it's really buggy.

Sticking with 2.0 RELEASE amd64 (build Tuesday September 13th 17:05:32 EDT 2011)

Any thoughts feedback/tips/suggestions are welcome. Would be nice to get rid of some of these bugs in 2.0.

Thx.

What 'type' of virtual IP are you using?
If you use 'IP Alias', which is what I would think you should be using, you should be able to specify /24.

Though if it's working for you perhaps just leave it!  ;)

Steve

Sorry, in answering another post I realised I left out a step in my previous reply. I have added an explanation to the end of my previous reply.

@The:

utilizing this bridge should have to create new firewall rules and would i mirror the original LAN configurations or is this done automatically when LAN is applied to the bridge?

Configuration relating to a pfSense interface is not reset when the interface is assigned a different "network port".

@The:

Is there anything i must do with vlans or is that not related?  i thought i remember having to designate vlans because the IP address of the device is set to one network but if i have other networks on different ranges downstream from the router's interfaces they cant communicate with eachother or something like that?

If you want a specific answer you will have to ask a specific question. There are so many possibilities I'm not prepared to attempt to guess the details.

I suggest you to create a new interface on pfsense and assign it to wifi.

Internet –-- pfsense ----- lan
                    |----- wifi router

hmmm

seems i wont be able to test again with 2.0.1, i can't afford once more to be without net, so i will wait till the next pfsense upgrade…
if someone knows how to fix the pppoe connection on 2.0.1, you can write here..

thanks everyone
bye

LAN, WAN, etc do not matter. It only matters that you have a gateway, and it's set as default. Traffic will flow whichever way you specify that.

If you only assign one NIC, it switches to "appliance mode" (so to speak) and you can do things like that without bothering with the additional unused interface

FYI the config is in the third slice, in my example above that is ad0s3 - if you're plugged in with USB in a card reader it may be da0s3

Backup config.xml are allways in Directory

/conf/backup

or

/cf/conf/backup

Mmm … Fortunately somebody more informed than me pointed that out. Thanks for that  ;)

Well then ... that pfsense box will only do routing / firewalling / NAT / VPN / ... not backups. I have a dedicated machine that does backups, another one which will handle media, etc

Glad to hear that ... And I think it wouldn't changed much in my bills either, because I had another E-30 (an MSI) which has a single x16 slot and probably has the same problem. Therefore the microATX case I chose (FRACTAL DESIGN ARC MINI, rather nice I think) seems to be a good choice.

If it is as you pointed out then I'll limit myself to doing only failover and leave link aggregation on the "client" machines and switches.
I think you're right since one user in another forum pointed that out as well ... but as I said to him I think something's odd, because with a 100BaseT router (Zyxel) and everything else gigabit ethernet (1000Mbps) I couldn't get transfers above 12MB/s (instead of the theoricals 125MB/s). Will have to test that out again with this setup.

In that case I'll just use 3 interfaces as failover  plus one WAN interface OR 2xWAN failovers and 2xWAN failovers connected to an average switch (definitively not a procurve).

As a side note, do you know why the HP Procurves 1810-[8/24]g switches I bought costs a lot less than the 1800-[8/24]g ? Both support link aggregation and the 1810-* seems more energy efficient. Do you know anything about it ?

Last but not least now the problem got reversed: I can perfectly access the WAN but couldn't get access to the web configurator but I can ping the LAN interface of the Pfsense box. This is so screwed up … could it be the OPT interfaces I enabled (though with different ip addresses) ?

Many many thanks stephenw10  ;). Today you really helped me getting started with this router !

You may find this useful for setting up vlans.

http://doc.pfsense.org/index.php/HOWTO_setup_vlans_with_pfSense

So far so good - tokk the nanobsd+vga 1GB image, placed it on an old CompactFlash and inserted it via an old CF2IDE-adapter into the router box - fine!

Ordered 16 CF-cards and adapters for the several running and backup boxes to switch them all to this, and will report the exact brand and type if it works. Just in case somebody else faces those problems.

By the way: the messages when booting from CD was this:

acd0: FAILURE - READ_BIG ILLEGAL REQUEST …
...several times.
Trying to mount root com cdXXX:...
Configuring crash dumps..

So the boot process proceeded, and I didn't care because I supposed the read error was recovered.

(this post and several others told me not to care: http://forum.pfsense.org/index.php?topic=24805.0 )

Tried 4 or 5 old CD-ROM drives, all the same. Those where not running in router boxes, but apparently aged while laying on the shelf...

Hi :)
Thanks for all your information :)
I have succeeded to set pfsense. I will put information here, in case if it can help somebody else :)

My pfSense box is set  with 192.168.1.1

Carte Ethernet pfSense :

Suffixe DNS propre à la connexion. . . : wminer.com
  Description. . . . . . . . . . . . . . : D-Link DGE-530T Gigabit Ethernet Adapter (rev.B)
  Adresse physique . . . . . . . . . . . : 00-26-5A-84-6F-3C
  DHCP activé. . . . . . . . . . . . . . : Oui
  Configuration automatique activée. . . : Oui
  Adresse IPv4. . . . . . . . . . . . . .: 192.168.1.245
  Masque de sous-réseau. . . . . . . . . : 255.255.255.0
  Bail obtenu. . . . . . . . . . . . . . : 7 février 2012 13:59:53
  Bail expirant. . . . . . . . . . . . . : 7 février 2012 15:59:53
  Passerelle par défaut. . . . . . . . . : 192.168.1.1
  Serveur DHCP . . . . . . . . . . . . . : 192.168.1.1
  Serveurs DNS. . .  . . . . . . . . . . : 24.xxx.yyy.37
                                      24.xxx.yyy.77
  NetBIOS sur Tcpip. . . . . . . . . . . : Activé

In the pfsense webgui

Interfaces: Assign ==> Verified if you wan port is setted

Interfaces: WAN Type DHCP
Services: DHCP server  [checked] Enable DHCP server on LAN interface
DNS servers
                                     24.xxx.yyy.37
                                     24.xxx.yyy.77

Status: Interfaces ==> Make sure your status is UP  
ISP DNS servers (most be the same than above
                                     24.xxx.yyy.37
                                     24.xxx.yyy.77

Test in the pfsense box
Diagnostics: Ping to 4.2.2.2
                      Ping to google.com

Ethernet adpter set (at the end)

Get ip automaticallyautomatically Get DSN address automatically

Test in the command line from your pc
Diagnostics: Ping to 4.2.2.2
                      Ping to google.com

Hm, found a 1.2.3 nanobsd with vga-support in jimp's folder at files.pfsense.org. It installed and booted just fine.

Thanks for the reply. I will look into that.
We went ahead and moved forward across the board with a DNS based content filter, it was a better business move in general. However it does look like overall the problem was Squid related, as Ntop was installed just fine. Ill dig into it when i have a little more time.

I wanted to post my solution to my mount root problem.  I have had the same issue whether I was installing pfsense or FreeNAS.  Both are freebsd based.  My solution to both  was to change the sata emulation from legacy to native in the bios.  That fixed both issues.

no clue what the official word on this is ….

what i would try is just install a new VM, install a clean 2.0.1, then insert config from the other vm