Have you verified that it's not the LAPTOP that's just slamming your
m0n0wall by using packet dumps?
I'm not sure if m0n0wall has a connections per second style of limiter,
but that would solve the problem if m0n0wall is being affected by all
sorts of attacks like that.
If the capability exists within m0n0wall to define connections per
second on the same criteria that we use within the ruleset, I'm not
certain of how to go about applying that configuration.
Rhon-Kaniel Bramwell wrote:
> Im having a problem with a m0n0 (1.3b2) that has problems handing out new
> dhcp leases after about 2 or 3 days running, the system is still responsive,
> meaning that I can login to the web interface and reboot the machine (WRAP
> 128MB RAM 233Mhz), but the system doesn't hand out any new ip addresses to
> clients. I originally thought the issue was with the logs filling up, still
> don't know if this is the case, I stopped logging the default rules and
> started pushing the logs out to a syslog server instead but the server is
> still doing the same thing.
>
>
>
> One thing that I've noticed is that in the Diagnostics -> DHCP Leases page
> I'm seeing the same machine multiple multiple times at slightly different
> times.
>
>
>
> Snippet
>
>
>
> IP address MAC address Hostname Start
> End
>
>
>
> 10.1.1.255 00:13:ce:94:61:48 LAPTOP 2007/05/08 12:25:12 2007/05/08
> 14:25:12
>
> 10.1.1.255 00:13:ce:94:61:48 LAPTOP 2007/05/08 12:25:12 2007/05/08
> 14:25:12
>
> 10.1.1.255 00:13:ce:94:61:48 LAPTOP 2007/05/08 12:26:02 2007/05/08
> 14:26:02
>
> 10.1.1.255 00:13:ce:94:61:48 LAPTOP 2007/05/08 12:26:02 2007/05/08
> 14:26:02
>
> 10.1.1.255 00:13:ce:94:61:48 LAPTOP 2007/05/08 12:26:07 2007/05/08
> 14:26:07
>
> 10.1.1.255 00:13:ce:94:61:48 LAPTOP 2007/05/08 12:26:07 2007/05/08
> 14:26:07
>
> 10.1.1.255 00:13:ce:94:61:48 LAPTOP 2007/05/08 12:26:32 2007/05/08
> 14:26:32
>
> 10.1.1.255 00:13:ce:94:61:48 LAPTOP 2007/05/08 12:26:32 2007/05/08
> 14:26:32
>
> 10.1.1.255 00:13:ce:94:61:48 LAPTOP 2007/05/08 12:26:35 2007/05/08
> 14:26:35
>
> 10.1.1.255 00:13:ce:94:61:48 LAPTOP 2007/05/08 12:26:35 2007/05/08
> 14:26:35
>
>
>
>
>
> Is there any workaround to this problem?
>
>
>
>
>
> Logs
>
>
>
> DHCP Log
>
>
>
> May 8 12:02:57 dhcpd: send_packet: No buffer space available
>
> May 8 12:03:05 dhcpd: DHCPDISCOVER from 00:18:de:06:3e:50 (CAMOYA) via ath0
>
> May 8 12:03:05 dhcpd: DHCPOFFER on 10.1.2.253 to 00:18:de:06:3e:50 (CAMOYA)
> via ath0
>
> May 8 12:03:05 dhcpd: send_packet: No buffer space available
>
> May 8 12:03:21 dhcpd: DHCPDISCOVER from 00:18:de:06:3e:50 (CAMOYA) via ath0
>
> May 8 12:03:21 dhcpd: DHCPOFFER on 10.1.2.253 to 00:18:de:06:3e:50 (CAMOYA)
> via ath0
>
> May 8 12:03:21 dhcpd: send_packet: No buffer space available
>
> May 8 12:03:57 dhcpd: DHCPDISCOVER from 00:18:de:06:3e:50 (CAMOYA) via ath0
>
> May 8 12:03:57 dhcpd: DHCPOFFER on 10.1.2.253 to 00:18:de:06:3e:50 (CAMOYA)
> via ath0
>
> May 8 12:03:57 dhcpd: send_packet: No buffer space available
>
> May 8 12:04:02 dhcpd: DHCPDISCOVER from 00:18:de:06:3e:50 (CAMOYA) via ath0
>
> May 8 12:04:02 dhcpd: DHCPOFFER on 10.1.2.253 to 00:18:de:06:3e:50 (CAMOYA)
> via ath0
>
> May 8 12:04:02 dhcpd: send_packet: No buffer space available
>
> May 8 12:04:09 dhcpd: DHCPDISCOVER from 00:18:de:06:3e:50 (CAMOYA) via ath0
>
> May 8 12:04:09 dhcpd: DHCPOFFER on 10.1.2.253 to 00:18:de:06:3e:50 (CAMOYA)
> via ath0
>
> May 8 12:04:09 dhcpd: send_packet: No buffer space available
>
>
>
> Exec.php -> df -h
>
>
>
> /dev/md0 12M 12M 697K 95% /
>
> devfs 1.0K 1.0K 0B 100% /dev
>
> /dev/ad0a 7.3M 6.3M 983K 87% /cf
>
>
>
> Exec.php -> top
>
>
>
> $ top
>
> last pid: 87486; load averages: 0.31, 0.17, 0.19 up 0+15:18:26
> 12:09:07
>
> 17 processes: 1 running, 16 sleeping
>
>
>
> Mem: 9100K Active, 3056K Inact, 40M Wired, 736K Cache, 6704K Buf, 52M Free
>
> Swap:
>
>
>
>
>
> PID USERNAME THR PRI NICE SIZE RES STATE TIME WCPU COMMAND
>
> 87483 root 1 -8 10 7416K 6888K piperd 0:01 17.00% php
>
> 111 nobody 1 96 0 1400K 828K select 0:50 0.00% dnsmasq
>
> 151 root 1 96 0 2588K 1088K select 0:34 0.00% mini_httpd
>
> 114 root 1 96 0 2416K 1424K select 0:13 0.00% dhcpd
>
> 104 root 1 96 0 1392K 716K select 0:12 0.00% syslogd
>
> 99 root 1 8 0 1888K 600K nanslp 0:06 0.00% ipmon
>
> 154 root 1 8 0 1236K 496K nanslp 0:01 0.00% minicron
>
> 118 root 1 8 0 1684K 760K wait 0:00 0.00% sh
>
> 107 root 1 96 0 2588K 1128K select 0:00 0.00% mini_httpd
>
> 87486 root 1 120 10 2224K 1368K RUN 0:00 0.00% top
>
> 311 root 1 8 0 1456K 744K nanslp 0:00 0.00% msntp
>
> 168 root 1 5 0 1684K 772K ttyin 0:00 0.00% sh
>
> 87485 root 1 8 10 1684K 1128K wait 0:00 0.00% sh
>
> 74425 root 1 4 0 2588K 1116K sbwait 0:00 0.00% mini_httpd
>
> 87484 root 1 -8 0 2588K 1184K piperd 0:00 0.00% mini_httpd
>
> 84855 root 1 4 0 2588K 1116K sbwait 0:00 0.00% mini_httpd
>
> 82215 root 1 4 0 2588K 1116K sbwait 0:00 0.00% mini_httpd
>
>
>
>
>
>
>
>
>
> Rhon
>
>
>
>
>
> Anngel.com
>
>
>
>
|