It's been fixed in 2.2 for months.

If you are still on 2.1.x and on a BSD/Linux release that has the problem, installing the Tahoma font should fix it. Either that, or remove Verdana. Installing Tahoma is easier and less likely to cause a problem though.

Throw away the dd-wrt router completely, pfSense can handle this all alone.

How many pots does the pfSense box have?

if it has at least 2 ports, use one as WAN, and add to another one VLANs. Note that in pfSense you can add VLAN tagged traffic to a port, while you can still access that port with untagged traffic too, and firewall rules apply completely separately: the VLAN-tagged traffic is handled as it it would go through completely new virtual network cards, so you look at them as your pfSense would have physical interfaces for each VLAN, while it doesn't have, but it looks like so. This applies to firewall rules, DHCP and all the existing services in pfSense. So you take this port and plug it to your switch as a trunk interface, you'll be able to access through the switch the VLANs separately, and that's great. if your pfSense has jut one port, you can do similar as above, just assign WAN functionality to a new separate VLAN - you'd use WAN traffic also through the switch, but separated from the rest.

@stephenw10:

It's a bit of a fiddle to setup because the lcdproc package doesn't play nicely with the sdeclcd driver that's required. There's a link in the wiki page but this is where you want to look:
https://forum.pfsense.org/index.php/topic,7920.msg344513.html#msg344513

Steve

I fixed the problem on all my WatchGuard units by editing the following file.

/usr/local/pkg/lcdproc.inc

define('LCDPROC_HOST','localhost'); define('LCDPROC_PORT','13666');

My changes: See line 36

define('LCDPROC_HOST','127.0.0.1'); define('LCDPROC_PORT','13666');

Importantly not the gateway for the dd-wrt box itself but whatever it's handing out as a gateway via dhcp for clients.
I don't actually know if that's a user setting in dd-wrt. :-
Edit: Looks like you have to add it as a dhcp-option. Really just letting pfSense handle DHCP woukd be much easier.

Steve

See my reply to your PM. Better to post here though.

Hi Mark.
That is the expected behaviour. By default all unsolicited incoming traffic is blocked on the WAN interface. That should not stop you accessing wan side resources (like the internet!) from the LAN though.

Steve

I got it to work by choosing Option #3 at the boot menu (boot with USB).  Thank you for the reply.

"Works great."

What would depend on what your looking to accomplish and what kind of performance you want out of it.. If you want to save couple of bucks on a nic and get lower performance then sure works great ;)  Hairpinning any sort of connection would never be my first choice to be sure.

Thank you Steve.
I installed the nanoBSD image on a 4GB USB stick.
Now I am going to look for a USB stick with a write-protect switch.

Luc

https://doc.pfsense.org/index.php/Filesystem_Full_/_Out_of_Inode_Errors

Yes, he was running earlier !. was resolved by installing the light squid package again, is now running ok. thans's
:D

Sure you can use a managed switch an put both connections into a trunk to feed your hardware.

The easiest way (and probably the most common solution) is to use a low power system which could look like this:
http://store.pfsense.org/VK-T40E/

Hello,
as you suggested, I switched on pfSense 2.2 RC on my machine. I tried to compile the driver under VM with FreeBSD 10.1, it compiled well but the kldload didn't work, so I took the one provided by arrmo, and this time it works : the alx0 have a dhcp lease when plugged to a SFR Box. Now I will perform tests to verify tu upload and download ratio ;)

EDIT : I configured my network as I planned (Captive portal + Freeradius + external MySQL database), and the debit, when I'm the only client, is almost the same as a connection not passing through pfSense. I built this for a LAN party in March, so i'll see in a few month if the custom driver bear the load ;)
Anyway, thx for your help and advices !

@johnpoz:

…you can not traffic shape if you run squid on same box??

IIRC that were past problems. When Squid was in transparent mode then traffic shaping didn't work out.
But it wasn't my post and I cannot verify it currently.

The quality graph is measuring latency, packet loss etc. to an external gateway or monitor IP. So it is only relevant and possible on interfaces with a gateway (WAN-style interfaces).
If you had a gateway to some other router on your LAN that has other intranet subnets behind it with static routes, then I guess that would also keep quality data.

Yes, ath0 is a wireless device, as you have guessed.
On the webGUI, go to Interfaces->(assign)
Available Network Ports dropdown at the bottom will show you the device names of any unassigned network devices that pfSense knows about.

that can also be easiley configured through the console menus.

Zikmen

Ok. There's no FreeBSD driver for the Broadcom BCM43225 chip used in that wifi card and it's very unlikely one will appear any time soon. Broadcom have not released an specs for it so it has to be reverse engineered as I understand it.
https://wikidevi.com/wiki/AzureWave_AW-NB290H

'Cascaded router' sounds like it might be the right option here but I need to do more reading. I'm probably not the right person for this since I'm in the UK and only vaguely familiar with uverse.  ;)

Steve

test hard drive with mhdd (if sata, must be set to "as ide" in bios instead of "ahci")
test memory with Memtest (and shake memory dimms while testing) the test should not stop as you shake the dimms. if it stops, use contact cleaner (DeoxIT)
install windows on the workstation (to be sure the machine is working fine)
Try another cdrom drive
burn the disc again
reinstall PfSense with default settings
finally, give us an update.

zikmen

test hard drive with mhdd (if sata, must be set to "as ide" in bios instead of "ahci")
test memory with Memtest (and shake memory dimms while testing) the test should not stop as you shake the dimms. if it stops, use contact cleaner (DeoxIT)
install windows on the workstation (to be sure the machine is working fine)
reinstall PfSense with default settings
finally, give us an update.

by the way, why are you moving to machine installed pfsense instead of Virtualisation setup?

zikmen