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

PPPoE is fully working now.

Please cvs_sync.sh releneng_1 and test!

Tested so far:

Port forwards

Firewall rules

Radius

LCDproc is usable, with a few restrictions, I think!

A few month ago, i connected a 4x20 HD44780 LCD to my pfsense-pc to parport, using std-winamp-style. But, IIRC, the lcdproc-pkg was built for FreeBSD 5.3?

So I endet in building my 'own package' on another BSD-machine. Transferred to the pfsense, it was working (CPU, Mem, Disk), except of everything that depends on network-data. So the Problem may be the (not) pf-specific code of LCDproc? Because of having no deeper knowledge on BSD's, I did no further testing. But nevertheless I think a Status-Display would be very nice to have…

ng0 is DEDICATED to pppoe if its in use or not.

Yeah, I need to add range features to ALIASES.  I'll look into it soon.

funny my last update was only a couple of days ago i will look and see when the fix was made

cheers maybe i will test the udp bit and see

That sounds exciting, especially if you're thinking along the same lines as paragraph 2 in my original question, like the capability you get on some of the Cisco enterprise-class switches.  It'll save me having to drag out and connect in a hub every time I want to monitor something.

I'm glad I moved over to pfSense.  You guys are doing great work!

status>interfaces in the webgui will show you this information. At the shell menu interfaces with link up will be displayed with a "*".

Are you sure your rules are correct and you don't cause routing trouble?

thx for the quick reply, fixed it.

oke then i will wait untill there is a newer version then the one from 10 feb