I have diagnosed and solved this or a very similar problem for a couple of
online friends but I am not clear how your system is setup. As you suggested,
in those cases the NAT routers were failing when they ran out of state table
entries which is something I have never seen m0n0wall or pfsense suffer from.
The solution in one case was to switch the DSL/cable modem into bridge mode and
use the external router as the PPPoE endpoint. They originally had 2 layers of
NAT and the modem was the device failing. In another case where the DSL/Cable
modem was using DHCP on the WAN interface, updating the firmware solved the
It is correct that your cable modem is using DHCP on the WAN side and using NAT
to provide a private address on its LAN for m0n0wall which then provides
connections through its own NAT to you and your tenant? Do you have just one
public IP address or something more?
>Quick info about my setup (didnt want to post the whole status page)
>- I don't use any advanced features - just some very basic traffic shaping
>rules, some firewall rules, some static DHCP mappings, but for the most part
>the settings are all default. Internet is cable 6M/800K dhcp. the system is
>a pentium II or something - there's never more than 1% cpu usage and memory
>is always around 12% used - it's on a 128MB CF, version 1.22.