@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

Good to hear!

Keep us informed if further problems arise.

Hi,

Thanks for the reply. I was thinking of doing the same thing as what you said, the only difference will be that I will use WAN2. My WAN1 connection is used for other things like https :)

The thing that I'm a bit concerned about is opening up a port to the lan just so that skype can transfer its files. I feel like its leaving a massive hole in the firewall.

Here is my current setup
I'm using pfSense-1.2-RC3-Embedded

                            _________ line1--modem---WAN1=PPPOE---|        |                             | PFSENSE |--LAN Line2--Cheap router---OPT1--|_________|  |                                         WLAN

I hope that's the type of info you were after.

Hi ;)

Version of pfSense? Hardware in use?

As for spotting other DHCP servers, the clients will list the DHCP server they used.  If that IP isn't one assigned to your pfSense host then that may be your problem.  From your description however it is most probably a bad switch.

Thanks guys.
I figured out the problem. It was a bad qos rule that stops the packets. No problem with the Realtek card.

Thanks once more
LHRT

well it is documented in the GUI:

Disable webGUI anti-lockout rule
By default, access to the webGUI on the LAN interface is always permitted, regardless of the user-defined filter rule set. Enable this feature to control webGUI access (make sure to have a filter rule in place that allows you in, or you will lock yourself out!).
Hint: the "set LAN IP address" option in the console menu resets this setting as well.