@rds_correia:

And also look at those short cable fixes.
I never knew why m0n0wall doesn't complaint about short cables on my system while pfSense always warns me about it.
Even because my cable ethernet cables are now both 5 meter long…
I would be much more relaxed if I didn't see those warnings once every 5 minutes but I gotta level it with you

That's probably because m0n0 isn't running RELENG_6_1.

–Bill

It pings the monitor IP of the link every 5 seconds. If the ping fails the link will be excluded from the pool until it comes back.

OK Different box, same hardware basically and on a HD, Firefox, and runs just fine. Very snappy!
Changing Time Zone took 4 seconds, not 25.
Whew, that's a relief!

and yeah, I could have using IE60SP0 yesterday, it's got that 'slow finish' . reproducing it now, but my benchmark, Time zone still doesn't take forever like it was.
I'll re-check that box Fri or Mon when it's plugged in on location.

On the floppy, seems like I noticed 98) even with a config'd floppy, and I thought it strange. But it might have been on a interface mismatch, but before reboot…
Yes, manually copying the file over is what I ended up doing.

Thanks for the comments.

Woow :)
Nice i will try it asap ;)

@sullrich:

Install the darkstat or ntop package from System -> Packages.

ntop and darkstat is a start of something… but It is not what I need....  have posted a bounty on this one :)

Ok, I updated to 1.0-RC3

It works  ;D

Auto-solved ^^

You probably should start with deciding how many zones you need. A typical setup to start with would be 3 nics in your pfSense (WAN,LAN,DMZ). Depending on usage a 4th nic for "home use" might make sense that is only able to connect to the internet but to none of the other subnets. Put the servers that should be available from the internet to the DMZ. The other trusted machines go to you LAN subnet. Untrusted machines go to the "home use". You can setup DHCP individually for each internal subnet at services>dhcp.

Now create the additional IPs you have at your WAN connection using firewall>Virtual IPs. You can use them then for portforwards to your servers.

Create firewallrules between the different subnets with appropriate rights at firewall>rules (like pass LAN-> DMZ; block DMZ -> LAN;…). Setting up aliases for ports/hosts can keep the amount of rules low and makes reading/changing firewallrules later easier.

You also should enable nat reflection at system>advanced as it usually makes using a DMZ from other subnets easier.

Can't reproduce this.

Modify the /etc/inc/system.inc file - the /etc/syslog.conf is build in there.

Check the log option for your default lan to any rule. Then all connections will be logged as pass in your syslogs. Other option is to use a package like darkstat or ntop.

@Gertjan:

A DSL PCI card modem device ?!! Why not, as long as it exposes on the PCI side a compatible Ethernet interface.

Well, if I remember this one right, they were offering special drivers for some brand(s?) that had to match built numbers of the distribution etc.
I doubt they were serving an ethernet-like interface to the host machine.
And manufacturers were quite limited. Very limited at that time (I haven't looked since then).

jahonix

FTP Sesame handles bridged interfaces.  This should be working.

Thankyou!

Sorry,
I have just tried what you suggested and still does not work.  Due to this not being connected to the internet what should be used as the gateway?  i have tried setting it to 0.0.0.0 and the WAN ip address but no luck either.

Thanks

Beau

@sullrich:

Take a look at /etc/inc/pfsense-utils.inc

In paticular:

enable_rrd_graphing()

Thank you sullrich for the tip.

I am using pfsense in a very pequliar way, you can find in :
http://forum.pfsense.org/index.php/topic,772.msg4635.html#msg4635

Since my original post, the ethernet card of the LAN interface, totally useless to my wireless community application, gave it's seat on the PCI bus to a 3rd wireless card, shrinking to a vlan opt that serves nothing.

This, as an update.

The important thing is that by looking at your mentioned file, I now have quality rrd graphing on one of my wireless links.

My coding skills are just not existing, so my implementation is the "crude" way.

a) For my setup the quality of the WAN interface is of minimal importance. It is directly wired to the cisco router.

So, I changed the if statement :

if("$ifname" == "wan") {
/* create link quality database */

to the Atheros card interface :

if("$ifname" == "opt2")

b) Then, I had to change the ip address it is pinging to. I did this by "hardwiring" the ip of my peer's wireless card.

I know, it's not a very educated way, but it works.

out=$btick ping -c $numpings -q $gatewayip $btick

this was changed to :

out=$btick ping -c $numpings -q aaa.bbb.ccc.ddd $btick

The next thing I have to figure out is which part of the code I have to duplicate to provide the same service for the other two wireless interfaces.

Any help on this will be appreciated.

If I had the required programming skills, I would have included a parameter box in the wireless interface web page for setting the ip to be pinged.

But I am not a programmer, nor a purist, so even so it's a nice thing to have.

It turns out to be a bad setting in the slow machines BIOS….

There is no problem with pfsense, I have problem with my hard drive. Thx for help.