IIRC some Unix systems would parse an IP address such that an initial 0 meant the following number was octal (base 8) thus 031 (octal) was 25 (decimal) and so 201.031.161.136 meant 201.25.161.136 which is confusing until you discover whats going on. I'm not sure the convention was universally adopted, in which case there would be an ambiguity in 031.
No idea if 031 is rejected because of this possible ambiguity.
@mcrane:
If you are using firefox you can save the link to your pfsense box. Then go back to that favorite right click on it and choose properties. If you put pfsense in the keyword section and save it. Then you can go to your browser's URL bar and type pfsense and it will then replace the keyword with your link you saved in the favorites.
Another option way this can be done on more than one system is by using opendns with a free account. Once you are logged into opendns you can define keywords that will be replaced with links that you define.
Actually these are nice options that I never have thought about yet. Great ideas! :)
@hoba:
This is the change: http://cvstrac.pfsense.org/chngview?cn=22213
You can manually change the file at your pfSense using diagnostics>edit file from the webgui.
I have applied changes and it is OK now.
TNX again.
Sasa
I can not make reliable 95th percentile graphs because that depends on the average over which it needs to be calculated. I can draw a line ofcourse for the 95th percentile but these would ofcourse differ per graph as most graphs have different average timeunits.
The 2 hour graph is 1 minute averages, the 16 hour graph is 5 minutes, the weeks graph is 30 minutes. etc.
Regarding your other point, no can do.
You might be interested in the bandwidthd package.
I did now your test, seems that it was my fault - something wrong with my secur key:
/usr/local/sbin/lighttpd -f /var/etc/lighty-webConfigurator.conf
firewall:~# /usr/local/sbin/lighttpd -f /var/etc/lighty-webConfigurator.conf
2008-03-28 16:25:26: (network.c.377) SSL: Private key does not match the certificate public key, reason: error:140A80B1:SSL routines:SSL_CTX_check_private_key:no certificate assigned /var/etc/cert.pem
firewall:~#
I generatet a new set key and certificate, now https workes with my certificate.
I am running v1.2 as well, on a system with 512mb ram, a 2.6 northwood celeron, and a 40gig WD hd. The gui does seem pretty slow, haven't firgured it out myself. Other than that it's a dream come true.
Yes, i can duplicate this, you can open a bug ticket for this and 1.3 if you want, i think for 1.2 it is really cosmetic…, you can make a new config.xml with copy and paste various sections to a new one.....
grreetings
heiko
pfSense is not compatible with the m0n0wall-cmi but the m0n0wall-cmi could be extended/modified to manage pfSenses with it as well. Maybe try to convince the m0n0wall-cmi guys to dive into this or post a bounty like you already suggested.
