Try a recent snapshot.
On 6/20/07, Fabian Steiner <[EMAIL PROTECTED]> wrote:
Hello!
We are using PfSense 1.2_BETA and are experiencing some serious problems
concerning DynDNS updates. Sometimes they are performed (obviously without
adding additional options, e.g. wildcard=ON) and sometimes they
Hello!
We are using PfSense 1.2_BETA and are experiencing some serious problems
concerning DynDNS updates. Sometimes they are performed (obviously without
adding additional options, e.g. wildcard=ON) and sometimes they don't work at
all.
In 1.0.1 system.log shows the following output after the
On Wed, Jun 20, 2007 at 01:50:10PM -0400, Chris Buechler wrote:
> Any switch's CAM table can be overflowed by directly connected users,
> but good switches won't fully turn into a hub in that scenario. Good
> switches keep one CAM table per VLAN, and in the case of overflow, only
> the overflow
Bill Marquette wrote:
Low end switches have a tendency to not have enough ram or cpu to
handle a high volume mac spoofing attack and will usually end up
turning into a hub under this kind of attack, rendering your vlans
useless.
Any switch's CAM table can be overflowed by directly connected us
On Wed, Jun 20, 2007 at 01:53:38PM +0200, Eugen Leitl wrote:
>
> I've just installed 1.2 beta on a Sun Fire X2100 M2,
> by booting pfsense 1.2 beta CD from a external USB DVD drive.
> Install was straightforward and without problems.
>
> I only see bg0 and bg1, though. According to dmesg it's
> t
I've just installed 1.2 beta on a Sun Fire X2100 M2,
by booting pfsense 1.2 beta CD from a external USB DVD drive.
Install was straightforward and without problems.
I only see bg0 and bg1, though. According to dmesg it's
the Broadcomms. Do I have to load extra drivers (how?)
or use a snapshot in
