@hoba:

Not doable in 1.2. pfSense uses a completely different shaper. Might/should be possible in 1.3.

we would like to wait…. :o

It would look like this:

                      ----nat-router----OPT1                     /                      pfSense LAN ----- clients/server ISP-Link----- switch -------------------WAN

I suspect you want a "transparent firewall".
The users dont notice anything that they are being filtered / protected but you still have a firewall.
Take a look at the documentation and look for the keyword "transparent firewall".

With a transparent firewall you bridge the LAN to the WAN –> you have the same subnet on LAN and WAN (as you have it right now).

A fast test would be to boot from the cd and only select the wan and lan nic. ( Remember a switch or crossover cable between your pfSense box and the test pc ).

Try to run the smp kernel in case you are runnning the uniprocessor kernel atm. If that doesn't help either simply disable acpi (see http://devwiki.pfsense.org/BootOptions how to make the option permanent on bootup).

This feature was realy nice for the ALIX/wrap boards…

Until I certain version (I think it was an early pfSense version 1.0x) it worked always perfect. What changed that the firmware update doesn't work anymore?

Is this going to be reimplemented later? Sorry, didn't read the upgrade post before.

Now I have a second ALIX board where I could make some tests with new software.

Performance will be poor but if the nics work with freebsd they will work with pfSense. However, most (or even al?) usb-nics don't support altq shaping so you will have to live without the trafficshaper.

The install process basically is just itting next, accept, go on, leave me alone, just do it…  ;) Pick the defaults and it will be ok usually.

None that is supported through the webgui at least.

m0n0wall has images for dedicated embedded systems. we don't and we don't want to do that either. our embeddeds are made to be able to run on various sorts of embedded hardware, but you have to configure it. maybe netgate should add a note about the nullmodemcable and offer it as option/bundle for a few bucks more. these cables are cheap and it would save you some shippingcosts if you get it with the unit in one delivery. that's something netgate (or other resellers) have to decide though. just making some suggestions here  :)

Try "pfctl -d" from the shell. This will disable the packetfilter. Then create the needed rule to access the webgui at WAN. Save, apply and reboot. You should now be able to do everything using the webgui at WAN. If your WAN has private IP-space make sure to uncheck the "block private IPs"-option at interfaces>wan too.

Polling prevents the system from getting blocked by interrupts. As long as you are not hitting such situations frequently I would not use polling.

@gendrix:

@hoba:

Try to disable UDMA. See http://devwiki.pfsense.org/BootOptions for how to do that and how to make it default.

thancs tho HOBA, i have tried what you've wrote, and its work

i have new problem now, i cant open the web configurator. I cant ping the lan interface, always show messeges :

rl0 watchdog  timeout
rl1 watchdog  timeout
rl2 watchdog  timeout

all my ehernet interfaces doesnt work. i shows not a normal detection on my ethernet switch. i try to move the ethernet card to other pc, it works ok.

i don't whats the problem. i think my cpu is in trouble.

any idea ??? ??? ???

You may want to check the hardware compatability list to make sure your NICs are there - if not it is hit or miss…

gm...

The workaround above works with any version. However for embeddeds I recommend a reflash.

With 1.2:
If I enable Upnp on both LAN and OPT1, on OPT1 the pfsense router is seen with the LAN address , but Utorrent can not open port with UpNp, maybe because I block the OPT1 -> LAN in the firewall rules. So I added a rule OPT1 -> Lan Address but still no port opening.

If I enable OPT1 only,  pfsense is seen with the OPT1 address and Utorrent can open port with Upnp

I've also seen problems where particular brands of cards don't work in a particular brand of adapter, but other brands do.  So far I've not had any problems with the Crucial (Micron) brand of cards in any adapter.

Reinstall with the 1.2-RELEASE cd and then pick the SMP kernel.  Does this change the situation?

@vsnine:

Additionally, http://192.168.1.1/status_nut.php is not actually dynamic. vi reveals that the page is just a dump of what it shows from some other page.

Glad it is working now. The status_nut.php page utilizes NUT's upsc. The page parses the data returned from the command.

No i have not always had high collisions, only when using the hub.

1st: the name of the interface is not x10 its xl0 or rl0 (notice the difference betwen 1 and the letter "l")

2nd: too use auto detect u must first unplug the cable from bouth of youre interfaces and connect them when the dialog apears

try this and post back reply