Did you disable any kind of firewall on the WAN-modem?
Can you look with TCP dump if you actually get any frames on the WAN2 interface?

@GruensFroeschli:

I set the lan ip to 192.168.2.1/24.

At this point, i have not been able to connect from firefox with http://192.168.0.1

Might this be the problem?

err typo on my part.  I used the correct assigned ip.

Some things do require javascript, but that's usually reserved to enabling/disabling options from showing or being available for selection. Usually it works for checking/unchecking/saving.

I usually just run links from the console and access it via http://localhost/ though, using the version built into the system.

You didn't say you were using the proxy before - If you are using the squid package, that traffic will not balance. It always goes out WAN. There is no way to load balance squid proxy traffic on 1.2.3.

I'm having the same issue with the same versions.
I also posted the issue separately: http://forum.pfsense.org/index.php/topic,27292.0.html

Its doubtful you'll need to mess with anything.  You'll get occasional TX Overrun messages depending on the kind of card you're using, but unless your performance is heavily impaired and you see a ton of these messages at corresponding times, its nothing to lose sleep over.  Glad the problem turned out to be nothing more than a browser hiccup.

It's hard to say what might be causing the stop. A shell script isn't really intended to take binary input directly from the console, but it maybe could be handled in a more graceful manner.

;D <- I just couldn't resist!

Thank you!

@joebobfrank:

Why is this so dangerous tommyboy? I hear lot of people connect to their computers remotely through the Internet.
Some people host their own FTP servers and some people host websites from their homes too, is this dangerous?

To a degree yes, however what you've doing here is exposing your firewall for people to probe and break into.

@joebobfrank:

What I would like to do is configure a tunnel of some sort so that when I am at a public computer somewhere I can
connect back home through a tunnel to check my e-mail to avoid the sniffers. Can this be done easily with pfSense?

Use a VPN.  pfSense supports PPTP, IPsec and OpenVPN.

There are various tweaks or features here and there I can think of that are missing from the GUI, but are supported in FreeBSD.  Some of the things I can think of that I've seen or heard of on dedicated APs but are missing:  association control by MAC address (whitelisting or blacklisting), WPS, WDS, and controlling the channel width (5 MHz, 10 MHz, 20 MHz - default on non-N, 40 MHz - default on N).  These are already all available in FreeBSD, but no code has been written yet to take advantage of them from the GUI (except there may be a partial implementation of association control by MAC address that is currently disabled).

Also there is 802.11n, which is supported as far as running the card in that mode, but I don't know of any FreeBSD drivers that have working 802.11n rate control yet, so it is not yet possible to actually use the faster speeds in that mode.

I noticed that the Traffic Graph shows all the traffic, its just the queue graph that gets clipped. Would this be affected by the traffic shaper max bandwidth values?

looks like somehow it's getting an IPv6 IP in there? Looks weird for sure.

Same thing happened to me a couple of weeks ago.  Just like NeophyteHeaven I had uninstalled Snort to upgrade to the new version.  Only thing I could do was a clean install to get the WebConfigurator to run again.

You must involve some kind of encryption, ideally a VPN such as OpenVPN, IPsec, or as a last resort, PPTP.

HTTPS is ok, but a self-signed certificate has its drawbacks. If you always access it from the same machine though it isn't so bad, because you will still be notified if the certificate has changed in some way.

Personally, I use HTTPS+IP restrictions on most locations, and OpenVPN or other tunneling for the rest.

Agree and sorry for wrong conclusion.
I have a firewall which shows more than 100TB in Total (over 8 months).

@0tt0:

Ok, I'll assign a specifc high tun # and see if that changes anything. Perhaps this type of usage isn't really recommended?

It's more of a "it works if you're careful but don't expect perfection" type deal. :-)

Some other caveats are covered in the book and on the doc wiki, but mainly hardwiring the tun device is important if you have more than one OpenVPN instance – client or server.

The theme files are all in git.
https://rcs.pfsense.org/projects/pfsense

Vector logo is available in cvs here: http://cvs.pfsense.org/cgi-bin/cvsweb.cgi/artwork/