Noticed it…

The width is static:

#content { ... width: 840px; ... background-image: url("images/horizontal.png"); background-repeat: repeat-y; ... }

But the width of the table isn't fixed. Very minor cosmetic issue.

ip address conflict?

After installation a nom d'utilisateur (username) and a mot de passe (password) are required to help keep casual hackers from messing with the firewall configuration.

Try nom d'utilisateur: admin and mot de passe: pfSense

I expect this would be in the installation guides.

There is a ticket I opened sometime as a reminder for all services in general that have some kind of login functionality that uses the user manager:  http://redmine.pfsense.org/issues/736

@torontob:

Thanks.

Is there a safer Beta version that I should use? I see that the packages are updated daily. Is this something like the SVN and TRUNK where today's Beta could be potentially all broken up?

Thanks

Yes, that is exactly how it is. (though sometimes the builder is stopped then restarted if a known issue is found and fixed before it finishes)

According to your df output before, you had no /cf mounted.  Maybe that slice was corrupt and couldn't be mounted?

50x5 damm.
yes i did disable hvap and actually it completely killed my internet connection. interesting…

You can assign it as an optional interface the bridge and than it will work normally without dropping you from LAN!

right! thanks I totally missed that.

Worked like a charm ;)

That's what I thought too… I'll continue fiddling and post back my results.

Problem looks to have gone away for me too.

Today I updated to snap '2.0-BETA5 (i386) built on Thu Jan 27 07:01:20 EST 2011'

I have an installation of the snort package, using the manual workaround (for wrong mysql-client package URL) described in issue 1080.

After going into GUI Services->snort->SnortInterfaces, then add & remove an interface (I have several interfaces to choose from; some of them are not snorted), I did not see the 'warning in line 3468' message any longer.

I'm not entirely sure if snort or the snort GUI was at fault, or if something just hadn't been fully cleaned up from a previous snapshot / config.

For now, I'm at least happy my pfSense is working as expected, just uncertain how it went wrong and exactly what fixed it.

Okay, I had tick at the qInternet, but I got error saying :  There were error(s) loading the rules: pfctl: should have one default queue on pppoe0pfctl: errors in altq config - The line in question reads [ should have one default queue on pppoe0 pfctl]: …

Since I am not good in this, I got main queue of qInternet which got a few child queues of qACK, qOtherDefault, qP2P, qOtherHigh, qOtherLow.

What I need is just a shaper that can cap nonproductive traffic like p2p and better manage my WAN connection by giving priority to web and email traffics.

Hi All,

I upgraded the firmware last night to:
2.0-BETA5 (i386)
built on Thu Jan 27 01:01:15 EST 2011

And the SSH key seems to be working fine now.

Thanks.

Not having any problem here.

ntpdate -d 192.168.1.253
27 Jan 15:58:23 ntpdate[5421]: ntpdate 4.2.4p8@1.1612-o Fri Apr  9 00:28:41 UTC 2010 (1)
Looking for host 192.168.1.253 and service ntp
host found : pfsense.local.lan
transmit(192.168.1.253)
receive(192.168.1.253)
transmit(192.168.1.253)
receive(192.168.1.253)
transmit(192.168.1.253)
receive(192.168.1.253)
transmit(192.168.1.253)
receive(192.168.1.253)
transmit(192.168.1.253)
server 192.168.1.253, port 123
stratum 3, precision -21, leap 00, trust 000
refid [192.168.1.253], delay 0.02603, dispersion 0.00000
transmitted 4, in filter 4
reference time:    d0ec62eb.98a657ff  Thu, Jan 27 2011 15:32:27.596
originate timestamp: d0ec68ff.c31adfff  Thu, Jan 27 2011 15:58:23.762
transmit timestamp:  d0ec68ff.bdaed56b  Thu, Jan 27 2011 15:58:23.740
filter delay:  0.02637  0.02608  0.02609  0.02603
        0.00000  0.00000  0.00000  0.00000
filter offset: 0.021008 0.020961 0.020924 0.020968
        0.000000 0.000000 0.000000 0.000000
delay 0.02603, dispersion 0.00000
offset 0.020968

27 Jan 15:58:23 ntpdate[5421]: adjust time server 192.168.1.253 offset 0.020968 sec

That is from my ubuntu box, I turn off built in time stuff on my window clients and run true ntp.. And it has no issues.

ntpq> pe
    remote           refid      st t when poll reach   delay   offset  jitter

*pfsense.local.l 221.107.86.229   3 u  754 1024  377    0.455   22.233  34.308

If I recall correctly – this
"leap 11"

Means your server is not in sync, so no your client will not sync to it.  You need to figure out why your server is not sync'd -- yup logs would help!!  I wish they would just go with the standard full ntpd vs that openntpd crap ;)

doesnt freebsd come with ntpd, whey does pfsense run openntpd vs and actual full ntp server?