@420:

There are two NIC's: 1, onboard Ethernet Port: Realtek 8201CL LAN PHY(supports 10/100Mb/s auto negotiation operation)

2. Is the Linksys WRT54G PCI wireless Card.

Are you sure about the WRT54G PCI wireless card? I thought Linksys WRT54G was a range of wireless routers?

@420:

whats best to use as since i have one Etherenet port NIC and the other is Linksys pci wireless, should the lan be wireless or should lan be hardwired ?

should the wan be hardwired or should it be wirelessly ?

I would recommend:

ISP…....> cisco 2100 modem........> (Wired WAN) pfSense  (wired LAN)  ->  DLink 4500 router: port[1]comp1–-port[2]comp2–-port[3]comp3–-port[4]xbox360

This requires an additional wired NIC for the pfSense box. As suggested in the documentation pages (http://doc.pfsense.org/index.php/Use_an_existing_wireless_router_with_pfSense, other links in http://doc.pfsense.org/index.php/Category:Wireless might be interestng reading) you would use one LAN port of the DLink to connect to pfSense and leave the DLink WAN port unconnected. You would probably need to tweak a few things to use the pfSense DHCP server for your whole network.

Having a wired LAN port can be very useful if you need to troubleshoot.
Until you find out the real model number (and probably revision) of the wireless PCI card its not possible to say if its supported in pfSense.

To provide web filtering (blocking of nasty sites) you would need to add packages such as squid and squid guard or use something like one of the OpenDNS services (see http://www.opendns.com). Which one you choose would probably depend on the level of blocking you require.

I use pfSense as a wireless access point and firewall. I appreciate having one box to manage rather than two. Others have reported that they get better reliability with a separate wireless access point.

Nothing because the gateway address is only used when the interface is a WAN type interface, in scenario #3 it's a second LAN and no gateway address is needed.

@wallabybob:

Some more details would help.

@Keljian:

the pfsense box is routing at about 5-6mbit.

Measured where? Doing what?

@Keljian:

When connected directly to the airport extreme I get line speed (11~ mbit)

First mention of the airport. When what is directly connected to the airport? The airport is connected to what? And what is the airport extreme? (If I had to guess I'd say I suspect its an Apple sourced Wifi Access Point and LAN switch but it seems a fairly generic name so I'm not clear about its purpose.)

Some simple diagrams would help clarify the configurations you are comparing.

Ok

draytek 2700 -> pfsense box (pppoe client)-> (recent) apple airport extreme -> (wireless) macbook pro  = 6mbit down from speedtest.net and max of 500KB/s download from akami (in australia)
vs
draytek 2700 -> apple airport extreme (pppoe client) -> macbook pro  = 11mbit down from above sources

Airport is:
http://www.apple.com/airportextreme/

apple airport extreme is a 4 port gigabit switch/router with 2 channel wireless n

You're welcome. I'll try not to sit and wonder for too long what your modem is going to tell you about your voip usage. ;)

Don't bother with nano though, just use ee, it's just as easy and already built-in.

As for the install-info error, it's harmless. The package still installs, but doesn't install the info pages (like man pages but usually more in-depth)

The ARP table is used to determine if a client is online/offline on the DHCP-leases page.

It would be only always in the ARP table if you activated the "Enable Static ARP entries" option.
Of course in this case the DHCP-leases page then always shows the device as "online" regardless of the actual status.

But as soon as the client communicated with pfSense the device should show up in the table.

@clarknova:

I tried diagramming what you have described and it's pretty confusing. Mind you, I'm pretty novice.

One things stands out to me though, you have 2 switches, and yet you have opted to run LAN and WAN on both switches. If you want to review a thorough discussion on why this is bad, have a look at this recent thread on the mailing list:

http://marc.info/?l=pfsense-support&m=128098748819739&w=2

I've never used pfsync, so I won't comment on that, but I think the first thing to do would be to plug your internet connections and pfsense WAN ports into SW1. Plug your server NICs and pfsense LANs into SW2. Arrange your vlans the way you like and put your loop woes behind you.

For the LAN WAN issue on both switches I saw that issue too. I had bought 2 addition switches to handle the WAN connections and got rid of the VLAN problem. I ran into another problem though with WAN Failover not working right because the WANs were on the same subnet. So I ended up witha whole new solution:

I Got rid of the Dual WANs on each PF and just went with single WAN connctions on each. I plugged the independant WAN cables from the datacenter directly into each PF WAN port. I am just using the 2 Dell switches now and have the LANs of each PF going to different switches. All servers have 4 NICs that are loadbalanced, having 2 cables going to each switch for redundancy. This way I can loose a switch and everything will still work. I also set up carp between the PF's So I could loose a WAN and still get out and same with loosing a LAN. It seems this setup is alot cleaner and is working great. The 2 WAN lines coming from the datacenter are already running HSRP on their end.

Jon

Since you SSH'd in then it's safe to say that you will be able to remote desktop. Just check your SSH settings. You must have missed something.

Take a look through the package forum.  Packages like SquidGuard, LiteSquid, and BandwidthD will help you accomplish what you are looking for.

@submicron:

Try disabling snort and squid and see if that solves the problem.  If it does, enable either snort or squid and try again.  Once you know what the problem is, its easier to figure out how to solve it.

i actually did all that and i wasn't surprised that it still didn't work since i downloaded a file 2 days ago off rapidshare and i have not changed any of my setting for them.

then i remember the only setting that i changed in the last couple of days was a added a custom port forward for my https site. after removing that rule my problems where solved.

Drop to using 1.2.3-release and see if that fixes the problem.

yes…. its odd it works for a bit then dies, then works for longer and then dies....

It's a BETA snapshot - so that is up to you. We don't generally recommend them for production yet, but some people use them without problems.

There should not be any security issues. There might be a couple missing features or things that don't work quite as expected yet, but those are getting better every day.

It's up to what is required for your system. If you must have more than 4GB of RAM, then you will need to use x64. If you can get by with less for now, stick with 1.2.3 and update after 2.0 is released for real.

ok I got it. I just used FileZilla to SFTP port 22 to the pfsense machine, used "root" as username and the pfsense password.

Makes sense… Thanks!

If you haven't already seen this, it will probably be very helpful to you. http://doc.pfsense.org/index.php/WPAD_Autoconfigure_for_Squid

Everything related to PPPoE is in the System log.