On Mon, 22 Sep 2003, Ryan Grove wrote:
> I recently moved into a new house and, due to the lack of DSL in the
> area, subscribed to Comcast Digital Cable. I'm using m0n0wall as my
> gateway and firewall. The WAN interface is using DHCP, and m0n0wall is
> providing DHCP service to my machines on the LAN interface as well.
>
> The problem is that twice in the last five days, m0n0wall seems to have
> stopped communicating on the WAN interface. I can't get packets out and
> packets can't come in until I reboot m0n0wall, and then everything works
> fine again. Using m0n0wall's ping utility, I've verified that it's not
> an issue with the LAN interface. I'm not sure how to figure out if this
> is an issue with Comcast taking away my IP or with m0n0wall dropping it
> and not renewing for some reason. Has anyone else experienced something
> like this?
I haven't used it with the cable modem "seriously", but when I did have it
running on the cable modem for test purposes, I saw evidence of a memory
leak in dhclient. Check the logs when it stops working.
Fred Wright |