There are far too many things that change to keep up with a list. As the other poster suggested, read the RCS log if you really need all the details.

It might be easier to list the things that haven't changed. :)

On 2.0 you just need to rdr the listening port but this is the other issue the client behind a nat.

Hi

just to note, the issues disappeared with the latest build.

cheers,

Stickies are fixed even on 1.2.3.
For the rest try it and report!

Anyone with a hint for me?

i  don't know what version you may be using but in my case i am having pfSense 2.0-ALPHA-ALPHA built on Wed Sep 23 11:28:05 UTC 2009 FreeBSD 7.2-RELEASE-p3 (and many versions before it–-i have updated many times already) with squid 2.6.21_10 as the only package installed.
      i am using two bridges only, mainly: a) opt1-bridge-to-wan, and 2) opt2-bridge-to-wan. however, i did not use opt1 nor opt2 for my long-range access point. i use my lan as the direct connection for my wireless ap. i am using my opt1 and opt2 as wired interfaces.
      i use different subnets and different gateways for each of the  lan, opt1, and opt2. i only copied the general(default) firewall rule from lan and applied to both opt1 and opt2(except for the names and the interface of course).
      ...and i can use wireless or lan or opt1 or opt2 seamlessly.
      maybe there's just a little bit of configuration you've missed? just my thoughts though... ::)

@fairchild:

@les_garten:

No Love here!  I would really like to get this going!

Anybody got any ideas?

i think its because everything sounds good, i got it working across 3 modems fine last night without any issues, maybe reinstall from scratch, update to latest svn and try again

Hi,
  Quick question.  You can pull out and plugin any combination of modems while running a continuous ping and as long as one modem is plugeed in the ping continues?  Also switching from one modem to the other the ping continues?  That's what I was looking for.

Thanx!
Les

This is fixed on the next snaps.
thanks for reporting.

I love PeerBlock (newer version of PerrGuardian), and was just thinking about this sort of feature on a firewall.  I wonder if it would be possible to have a package that could stay updated with the lists of known "bad" addresses?

There is no ftp-helper in 2.0 it is totally transparent.
Can you please get me a tcpdump with total packet content if you continue to have problems in this mode?

One side on the lan and the other on the wan.

Give me more details otherwise to me is just wrong reporting.

I did a fresh install with pfSense-2.0-ALPHA-ALPHA-20090923-0921 (8.0 Freebsd), activated ssh and changed IP. After several hours of "not touching the system" i looked at the screen, nothing. Menu is on, no error. When I tried to get access via ssh it panic-ed again. I shot a foto of the screen because it was too much info to write down. Other pid, so i think it varies. The pid-number even is different.

Hope its to read. Bad quality…

Now after half an hour it paniced again, other pid. It panic-ed when I tried to get access via ssh. Other pid again. Next time i try to see if the logs show anything. Is there any "more useful" thing I can do to help you finding the problem?

IMG_1081.gif
IMG_1081.gif_thumb

Working on nanobsd 7.2 snapshot of 2009-09-22 ~ 18pm

@fairchild:

@ermal:

Should be fixed.

in latest svn i assume?

Git, not svn.

That was fixed in 1.2.3 but not in 2.0 since the wireless in 2.0 will be going through a major overhaul to support FreeBSD 8.

THANKSSSSSSSSSSSSS SO MUCH.. all is right now..

I did various restarts with no effect. There seems to be maybe a typo somewhere in one script, because I have warnings inside of the fields like in TCP-Port or other ones. It seems to be only in System - Advanced. I played around with settings in system.inc, but everytime when lighty-webconfigurator.conf is written I have web-Port = ARRAY and lighttpd doesn't start till I change ARRAY to "80" to get lighttpd on again.

At last my skills in understanding the scripts is too low to "repair" this.