Should be fixed in next snapshot.

It's not a bug, we just don't automatically allow DHCP traffic over bridges anymore. You have to add rules to pass that traffic just as you do with any other kind of traffic. Auto added rules are bad.  And this auto added rule wasn't even intended to allow DHCP traffic over bridges, that was just a consequence. Allowing that traffic was a bug, this is a bug fix that you now have to add that rule.

It's very, very unlikely there was a driver regression between September and December, almost nothing changed in FreeBSD 7.0 between then. It's also highly unlikely any changes in the pfSense code base would have caused anything like that, since nothing at all related to Ethernet interface code has changed in a long time, longer ago than September.

Can you reliably replicate this being resolved going back to an earlier release, then breaking going back to 1.2.1 release?  If so, what date is the one that works?  Given the lack of changes in any related areas, I doubt if that's truly the case. If so, I have a bunch of 1.2.1 snapshots that I can make available to help narrow down further.

What wireless NIC are you using?

The Atheros based wireless PCI NIC I'm using as my 'production' wireless access point gives service over many days without requiring a reboot. On the other hand, a USB wireless NIC I played with only a little bit (rum driver) doesn't seem to sustain connections very long but I've not seriously investigated that yet.

1.2.1 is a bugfix release. No new features. If you need the new features, use 2.0 and deal with the fact that it may not be stable.

Set hw.ata.ata_dma=0

for compac flash.

Refer to

http://forum.pfsense.org/index.php?topic=6840.msg69524
http://devwiki.pfsense.org/BootOptions

Disable DMA for IDE drives

@n1ko:

And it isnt possible to downgrade to the previous driver (from the 6.3) ?

No.

@n1ko:

Is this a common bug in the freebsd or somekind of pfsense specific bug?
Also happens with my Nokia E90

FreeBSD issue.  Install a 7.0 FreeBSD iso and report the problem to freebsd-mobile@

fixed but i still have bandwith problems.

Try a different CDRom drive.

And if you want to reply that you already tried a different one, well try yet another different cdrom drive.

vsftp

Thanks!  For now I have just downgraded back to 1.2 RELEASE and will upgrade again when this problem has been fixed.

Any advance on this issue? Its still happening in 1.2.1-RC4.

With the help of Billm I solved the connection problems by turning off RIP.

The missing console is still gone.. but I can live with that..

Solved thanks to Billm. RIP causing the problem.

I created a rule that blocks the traffic but doesn't log it.. that simple…