IPFW is only used for CP, that is correct. If IPFW gets unloaded the interface won't be captured to the loginpage anymore. The firewallrules set at that interface however will remain active as these are handled by pf. When this occurs how many states does your system show at status>system? Maybe someone who authenticated fired up a statehog like bittorrent? I don't know if there is a way to bump up the limit for IPFW somehow or what limit is in place atm but I guess you are exceeding it somehow.
Holger > -----Original Message----- > From: Imre Ispánovits [mailto:[EMAIL PROTECTED] > Sent: Wednesday, November 15, 2006 1:49 PM > To: [email protected] > Subject: [pfSense Support] Too many dynamic rules error > > Hi List, > > I'm using pfSense 1.0.1 on generic pc dual-wan-carp configuration. > I've started to play with captive portal now on OPT4 interface. > I'm receiving the following messages on the console: > > # ipfw: install_state: Too many dynamic rules # IP firewall unloaded > > # Warning: memory type IpFw/IpAcct leaked memory on destroy > (1 allocations, > #1024 bytes leaked). > > I've got the feeling that this has some relation to captive > portal, but I'm maybe wrong. > What these mean? How serious it is? What should I care of to > get rid of this errors? > > Thanks > Imre > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
