peter <(E-Mail Removed)> wrote:
> I have isolated this problem down to the firewall.
> If I turn off the "SPI and Anti DoS" feature, then the DHCP client works
> again.
SMC speaks to this a little in their FAQ
http://www.smc.com/index.cfm?sec=Sup..._id=379&site=c
It is also mentioned on DSL Reports
http://www.dslreports.com/forum/rema...6807~mode=flat
I unchecked SPI and anti-DoS because it prevents connection to any IP
address ending in 000 or 255 and also sent me a bunch of SMURF attack
messages. Prior to that I made these adjustments, which stopped some
problem that I had. My SMC7004WFW settings are behind yours.
> Connection policy:
> Fragmentation half-open wait: 10s -- 30
> TCP Syn wait: 30s -- 60
> TCP FIN wait: 5s -- 25
> TCP connection idle timeout: 3600s
> UDP session idle timeout: 30 s
> H.323 data channel idle timeout: 180s
> Dos Detect Criteria:
> total incomplete tcp/udp sessions high: 300 sessions
> total incomplete tcp/udp sessions low: 250 sessions
> incomplete tcp/udp sessions (per min) high: 250 sessions
> incomplete tcp/udp sessions (per min) low: 200 sessions
> max incomplete tcp/udp sessions number from same host: 10 --20
> incomplete tcp/udp sessions detect sensitive time period: 300 ms > --1000
> max half-open fragmentation packet number from same host: 30 > --60
> half-open fragmentation detect sensitive time period: 10000ms
> flooding cracker block time: 300s
---
Clarence A Dold - Hidden Valley (Lake County) CA USA 38.8-122.5