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.

I have had the SAME problems with the snapshots and the 2.x release ….its very random.

it is not a switch issue, wire issue, and the only thing i can think of is a driver problem, but that said....i have tried four different NIC card makers and all of them have the same issue.

link to my original post aboot this issue: http://forum.pfsense.org/index.php/topic,40147.msg207235.html#msg207235

strangely enough the link does NOT stay down …its what i call a hiccup that isnt even noticed unless i do a constant ping for days upon days.

@Sensi:

Most of the vLans are serverless networks - the couple with a server have just one server.

But your original post said @Sensi:

(I've then got to give most of the vLans a dedicated WAN IP address - only a couple will share).

which implies a couple of VLANs will share an IP address which means you will need port forwarding to send (for example) the web requests to the server on "VLAN A" and ssh requests to the server on "VLAN B".

You need the Virtual IPs because you are using IPs not assigned to an interface.

@Sensi:

All the entries are IGMPs with a source of the router a destination of 224.0.0.1 (haven't a clue on that) on the interface of wan

So if the firewall is dropping your traffic to 10.64.0.100 it is not logging it. For now you can ignore those entries in the firewall log which don't have a source IP address of 10.7.0.101 and a destination address of 10.64.0.100.

Please show your firewall rules for VLAN7 including any alias OR go through the rules for VLAN7 yourself to verify that access to vlan64 is allowed.

Another possibility is that 10.64.0.100 has some sort of firewall (e.g. Windows firewall) that is blocking tracert. Please check that out.

As long as it sounds right then I'm happy.

Thanks

I just thought I'd update this thread.    I never did get pfSense with the DSL modem.  The modem is old an 10base-T so maybe that was the issue.

The NIC cards I had are bge and re.

Using the exact same hardware (and using the new Pfsense 2.0 (not the RC3) and a cable modem everything worked first time.

Thanks for the help.

I am with you guys. I would like to see a 2.0 appliance for vmware. Any idea when it will be coming out?

@dreamslacker:

@cmb:

install with the drive in another system, choose the embedded kernel option, and move the drive over when finished.

Is there any difference between choosing the Embedded Kernel option and configuring a VGA install to use Serial Console (in the WebGUI) instead?

If memory serves, I think the embedded kernel doesn't support SMP.  When I just installed my net6501 I did a full install with the SMP kernel on a virtual machine (in case Soren ever gets around to enabling hyperthreading on the Atom), checked the box for serial output in the Web GUI, then moved the drive to the 6501.  Works like a charm.