Hello gnbh,

Thanks for the update.
The order of the interfaces plays definitely a role in it. It doesnt work the other way around.
Also pressing "disconnect / connect" doesnt reconnect it again.

Its not to be seen as a solution, but more a workaround for the desperate.

As soon as we know a better way of doing it we will post it here.

Our guess is that PPPOE is brought up first with the subnet mask as written in the config file.
Because opt2 has the same subnet mask it seems valid for that split second.

Soon after PPPOE is up probably netmask is corrected to /32 but connection stays alive.

Hi heper, I never tested load balancing, because in my case I don't want to load balance between 2 physical WANs, I just want to control my traffic, and choose between 1 physical WAN and 1 logical WAN (openvpn connexion through WAN).

So I didn't even try load balancing feature.

However, I think it should work, because in my setup, http traffic after being filtered by squid comes back to pfsense through a network interface, so for pfsense itself it's transparent, like if there was no proxy at all. Instead of coming from LAN, http traffic comes from a DMZ interface, but that's the same thing. So if you're able to configure load balancing correctly without squid, you should be able to make it work the same way with a squid setup on another virtual machine.

wow manual install of image without an error - PERFECT WORK!

I was thinking about editing the config file in the iso.

Sorry for my nooby's impatience ;-)
Your right, with the lastest snap from monday the 24th, the firmare message appear at the end of the reboot but after few secs the gui is available again.
Thanks

i reinstalled pfsense now

the only problem that the dhcp clients loose there ip and i see an error in the logs

dhcpd: send_packet: Host is down

and sometimes but not everytime the server freezes

i found this: http://lists.freebsd.org/pipermail/freebsd-bugs/2010-January/038270.html

I didn't think about…. That should work nicely.. Thanks for your suggestion :-)

yes, confirmed: I get the harddisk and "Update in progress". Very nice.

Thanks ermal.  -Raylund

@_igor_:

Did you change your interface-settings as said by wallabybob?

Virtual box NICs default to some type of AMD NIC. One or both of the NICs wouldn't work (I forget the exact symptom but it was something along the lines of "wouldn't transmit" which bears a resemblance to what you have reported). The problem went away when I changed the emulated NIC type to Intel e1000.

That should be your next action!

Your way to search for that error seems to be ineffective.

Of course I did, had already tried and retried.

Your way of assisting seems to be ineffective.  Otherwise I'm sure the problem would be solved by now.

Please make sure that you have not activated killing states on down gateways on Advanced->Misc settings.

What snapshot did you use to upgrade?

That function call is on line 85 in 2.0, not 73. It was on line 73 in 1.2.x though.

I'm guessing your upgrade did not actually complete properly, at least that one file (and probably others) may not have been upgraded.

Sorry that I didn't answer. It was fixed on sunday I think. Now the wizard is working again.

In the last twenty minutes I have managed to update twice and things appear normal enough.

@geeknik:

Pinging from my desktop machines, which are assigned everything via DHCP. The DHCP server is giving out the OpenDNS IPs and not the pfSense IP for DNS. And I ran that command, forwarding is off.

I need to update http://doc.pfsense.org/index.php/Unbound_package to reflect that one needs to add the pfSense IP to the DHCP DNS Server settings. Otherwise currently pfSense dishes out the DNS Servers defined in General.

@geeknik:

Unbound keeps dying though. And when it goes, the whole web gui for pfsense quits responding. Restarting the gui through SSH doesn't do anything. I have to reboot the entire machine and 50% of the time when it comes back up, Unbound isn't even listed as installed and DNSMasq is re-enabled.

What does /var/log/unbound.log and /var/log/system.log say? It sounds like your config gets rolled back due to a problem hence why DNSMasq is re-enabled and unbound is not listed as installed. /var/log/system.log should give more info on this problem.

Thanks works perfectly!