hi

i volunteer to test it on 4 different servers if any developer willing to work on it

hadi57

Here is the dump, Sorry to be in wrong thread, is it possible to move these posts to the openvpn thread?


I would imagine that its a hard coded limit.  I don't think anyone has gotten anywhere near this number considering that this is the first that I am hearing of such a large deployment consideration.

Really don't know how well this is going to work.  These really are unchartered waters.  And considering that when you make changes to PPTP it disconnects the client(s), I wouldn't see any difference on the PPPoE side as well.  If you are serious about this large of a deployment I would definitely do some type of test before going live.

Might have been a leftover arp cache problem

In the future try clearing the arp cache on any neighbor devices, switches, routers, etc.

Soekris 4801 is too slow to work with wireless cards and multiple wans. Once traffic goes up on the wireless, the CPU interrupt usage goes sky high and nothing else gets done. Look at the new ALIX boards.

This is from experience. I want to get rid of my net 4801 board for this reason.

You are going to want to stick with the FreeBSD 4 series of m0n0wall in this case (1.2).

@qzvt:

and i don't understand you say that

Did you search?!?

Somebody asked this a while back…
http://forum.pfsense.org/index.php/topic,5056.0.html

thanks
Will move to the packages forum.

The links i use

http://www.freebsd.org/cgi/ports.cgi?query=darkstat&stype=all

ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-6-stable/All/

Post the output of 'top' run from a command line.

Minor point - pfSense is FreeBSD based, not Linux.

Proxy - install Squid - this will also allow you to block domains

Bandwidth shaping - pfSense can do this too (Firewall -> Traffic Shaper)

When you say you want "direct control" of the linksys - consult the linksys documentation.  According to what you've posted the pfSense host is behind that, so has nothing to do with it.

IP Redirect - Firewall -> NAT -> Port Forward

If in doubt, read the documentation ;)

This is not as simple as you think.  FreeBSD does not have multi-homing by default.  Please search the forum, this has been covered in great detail and will not be fixed until FreeBSD receives multi-homing bits which is in progress.

ok, that makes sense. Thanks!

@sullrich:

1. Add your script to /usr/local/etc/rc.d/
2. The script must end in .sh
3. chmod a+rx /usr/local/etc/rc.d/scriptname.sh

This is what I have done - and it does not work - but my script runs in an endless loop - maybe this is the problem?

Bye,
eweri

I have a similiar unresolved problem…..  http://forum.pfsense.org/index.php/topic,7103.0.html

You'll need to do a full install:

http://devwiki.pfsense.org/FullInstallOnWRAP

It works very nicely.  Expect the beta versions after 1.2 is released.

Proto    Source    Port  Destination  Port  Gateway  Schedule  Description   
*      Lan2 subnet        *        *            *      *              *    Default Lan2 out