OK, I'm looking very much forward to see if that function comes into pfSense  ;) :D

Thanks for a very great firewall OS

Anders Hansen

hello, I will also like to know how the rules of filtering update themselves? which is the procedure? which are scripts used ? thank you very much! (sorry for my bad english, i'm french…  ::) )

Short answer: you don't without knowing how to do it yourself.

Try outbound NAT manually - only for 192.168.2.0/24
PPPoE is not encrypted  tunneling -  encrypted is PPTP..

Też pozdrawiam z Polski ;-)

R.

dd on any unix box (or cygwin).  I usually dd an image for archive and then use physdiskwrite later for writing CF cards.

–Bill

Alright I'll raise the states…  ;D

The Load Balancer is working now I've done the Monitor IP address things, and so far the net hasn't gone down. Thankfully.

I love the new RRD graphs in Beta3  ;)

I still get these messages though.

slbd[11921]: Service changed status, reloading filter policy

And I got (some time in the early hours of the morning)

Apr 26 04:47:26 php: : There were error(s) loading the rules: - The line in question reads []:
Apr 26 04:47:26 kernel: pool_ticket: 993769 != 993770

So I'm still not sure what's going wrong, but hey, the internet seems to be working!!

It does.  This isn't FreeBSD, it's pfSense.

I reinstall PFSense Beta 2
Update Beta 3

Setup bridge Set rules create VIP Set Carp options –-- kernel error and other messages.

PS PFSENSE work int this Hardvare 14 days - not any kernel erroros
ps2 i can't boot from beta 3 iso CDLive - can;t load kernel!

@VaCUm:

I'm running pfSense at home on a old Pentium II and i use a CF-card instead of a hard drive. I have changed /etc/platform to wrap and disabled logging to minimize disk activity.

You want 'embedded' not wrap btw.

–Bill

How does openntpd perform in a high IRQ (interrupt) environment?  A number of my machines on OpenBSD run 15K + interrupts/second - with that load, ISC's ntp daemon sucks ass.

upgraded to beta 3, but before i did it happened two times earlier that day. Some times it last up to two hours of not being pingable/ssh'd into etc/etc. Other times it only lasts 20 min.

so we will see how beta 3 does. Beta 3 so far seems much more responsive just through the menus and such. great work!

Both WRAP and Soekris platforms work fine.

Confirmed here on both Soekris platforms (4801/4501).

Btw, I prefer a serial cable over a monitor and kayboard. It's cheaper!

I can only agree to that. And it needs less space ;)

Thanks for reporting. Solved in HEAD, prolly made it to beta3.

I somehow don't trust this subnetmask (255.0.0.0). Also note that the gateway is outside your WAN subnet. These settings don't make any sense to me.

576 is pretty low. Try pinging with no fagment flag:

ping -f -l <lenght><wan-gateway ip="">(windows syntax)

your mtu should be the highest length you are able to ping +28 (overhead). A typical mtu value for DSL should be 1492 but your's seem to be lower as this is the default value pfsense will use for pppoe. Try to find out your maximum with ping.</wan-gateway></lenght>

Perfect, i'll try that.

Thanks.

@magi.sys:

Is it possible to have what they call unnumbered pppoe setup with pfsense?
I have 8 static ip addresses assigned to me via broadband, and here's what my current router does.

It assigns an ip address to itself on the WAN, and bridges to the interenal network that has 5 static ip addresses in the same subnet. Can pfsense be setup like this?

Probably not, but pfSense can give you an extra useable address.  Instead of the lame 5 that you get cause the router eats one and won't let you use it for NAT'ing, you get six…pfSense will let you use that sixth IP for NAT.

--Bill

thanks