Hey Phil, I meant the kbps levels. Before it was presented in an ascending order, now its so different. It doesn't seem to notice the ip addresses that are using a lots of bandwidth, place them at the top and those that have gone off the network. Instead it mingles everything to an extend that I cant notice.

But anyways, helped lots. Thanx

You need to redirect based on host-header information which isn't something that the firewall usually sees. As Kejianshi says if you run a reverse proxy that will be able to see it. Searching the forum for 'host headers' reveals some promising threads. E.g.:
http://forum.pfsense.org/index.php/topic,46494.0.html

Steve

Why don't you use freeradius2 which restarts much faster with

radiusd onerestart

Freeradius2 can do everything freeradius1 can and more.

I'll try it and see if it works out!
Thanks

Ok found it.

Nice write up here if you can use OpenVPN: http://swimminginthought.com/pfsense-routing-traffic-strongvpn-openvpn/

Other protocols will be similar though.

Steve

Yes, or use a supported wifi card directly in the pfSense box if you don't have a any signal problems.

Steve

Are there no any documentation out there about to setup Reverse Proxy with Squid3?

Tried to find myself, can't find it. If someone know how to setup, please let me know.

Ha, nice.  :)

Steve

Happened across my own answer.  PfTop, Rules view.

Was there ever a solution discovered for this? I'm seeing the same thing on my firewall running 2.1-RC1 (i386) (built on Wed Aug 28 16:55:08 EDT 2013)

Is there code somewhere that forces the system to log if the IP options checkbox is checked under the advanced options on my IGMP rules?

@ilumos:

My two thoughts with using VLANs are that 1) I'm not sure if cheaper wireless hardware can deal with VLANs and 2) every subscriber would need a VLAN capable switch to untag the packet (is there a cheap way to do this?)

Whereas PPPoE can traverse wifi, can it not?

Look at the "airMax" Ubiquiti products line… you can get info/help about the wireless part of your project at his forum

http://community.ubnt.com/

@stephenw10:

Edit:
@jimp:

VLAN MACs follow the MAC of their parent interface.

That is the default behaviour. The web GUI allows specification of MAC address on VLAN interfaces. I have a recollection that in some contexts the configured MAC address for a pfSense VLAN interface wasn't propagated to the hardware. (I can't remember the context - a virtualised environment? a 'feature' of specific hardware?)

Bridge interface MAC address seems to get propagated to the hardware.

Yes though you would not want to remove the existing command, but run it also (should be OK to put a ; and then your command after the one there already)

Ok…sorry for the delay in getting back...school starting has kept me very busy...

I have considered VPN and even tried to implement it but had zero luck with that. I'm not sure why, it was several weeks ago now. I know that opening multiports for RDP is not the best solution, but it seemed like one that I could make work, at least for now. I would love to get VPN up and going but I'm not sure my Firewall/VPN skills are up to it.

If someone could point me to a beginners guide to VPN, espeically if it was specifically related to setting it up on pfSense, I would really appreciate it. I am under the gun timewise for getting this working...so that students can have remote access.

Regards,

riversr54

If someone will find this topic I've got one remark.
Initializing the monitor mode in 'separate lines' (like in the post above) didn't work for me.
I had to do it in one line with:

ifconfig wlan create wlandev ath0 wlanmode monitor ifconfig wlan1 up

Interface options for reference:

wlan1: flags=8943 <up,broadcast,running,promisc,simplex,multicast>metric 0 mtu 1500         ether 00:80:48:64:63:57         inet6 fe80::280:48ff:fe64:6357%wlan1 prefixlen 64 scopeid 0xb         nd6 options=43 <performnud,accept_rtadv>media: IEEE 802.11 Wireless Ethernet autoselect mode 11g <monitor>         status: running         ssid "" channel 11 (2462 MHz 11g) bssid 00:80:48:64:63:57         regdomain ETSI country NL ecm authmode OPEN privacy OFF txpower 30         scanvalid 60 protmode OFF wme burst</monitor></performnud,accept_rtadv></up,broadcast,running,promisc,simplex,multicast>