Hi Jim,
  always clean… but your answer made me thought that I was enabling the RAM disk on my Alix... disabled the RAM disk, the problem is gone! ;)

Thanks,
Michele

Try a tomorrow snapshot or gitsync.

Thx, for you reply!

But maybe, there is an misunderstanding or I did not understand… ;-) I think the GWs in "System > Routing" have nothing to do with this problem.

It´s about the DHCP Server "Services > DHCP Server". I have three Networks. Before the update, I left the Gateway field blank.

The default is to use the IP on this interface of the firewall as the gateway. Specify an alternate gateway here if this is not the correct gateway for your network.

After the update, devices did not get a standard-gateway via dhcp. So, I had to put the interfaces IP to the Gateway-field to get dhcp working.

Thx!

i noticed enabling WME also causes stuck beacon to happen more often, since i disabled, i didnt get any

yep. the issue has gone with this built:

2.1-BETA1 (i386)
built on Sat Apr 20 17:07:58 EDT 2013

@Stef:

Changing the system tunables did the trick

Given the original post said:
@Stef:

On the bridge Adapter in the firewall rules I've allowed everything both Ipv4 & ipv6
. . .

On All the adapters that are bridged I've done the same thing.

I can't explain what you reported.

Should be fixed.

Hi guys,
I know that a forum is not a hotline or paid support or whatever but 116 views and just one answer, how can I say it? Weird?
If someone have some piece of humankind or charity or maybe some pfsense skills that I in my situation don't have, can he spread a line here?
I don't what to think, a bug, a misconfiguration but some help would be really appreciated.

Thanks!

Few %.. It's a Dual core 3.0Ghz system so I wouldn't expect my 20mb cable line to cause issues with the 18mb dsl line. Also has 2gb RAM.

Anyone else able to test this?

I know it use to work and seems odd the reverse works but just wondering.

Old Thread, please refer to:
http://forum.pfsense.org/index.php/topic,56367.0.html

Good catch, just committed the fix.

Thanks!

that's the same as redmine #2463

Different issue so I split it, please don't hijack threads.

What type of IPv6 were you adding a gateway for (static, PPPoE, DHCPv6, …)? The fe80::1%re0 is actually the default route your provider assigned you? The looks of that makes me wonder if you're adding your own IP as your default gateway.

Nevermind, still happening.

Edit: and with the new latest, maybe not. Time for more testing.

Edit2: looks to be completely fixed, I'm now seeing blocks in my logs as they should be, and can't pass data where I shouldn't be able to. I can't seem to find a relevant commit so maybe it's magic, but it seems to be working properly now either way.

@cmb:

Oh the big difference there is when you're downloading from the ALIX, you're saving it to CF. CF is very, very slow.

Indeed it is.

I was able to cut the total firmware download and transfer time in half by using the two step desktop web browser then scp to alix method.

monitor user error

flopped my dns static route monitor ip