> We're using m0n0wall as a captive portal. The m0n0wall handles routing between
> the WAN and LAN. NAT is not used.
> We have had a problem these last weeks with a few PCs. When the client connects
> they get an IP address from our DHCP but when they try to connect to the
> captive portal the webbrowser times out with an message that it cant find the
> server. The problem is resolved when the clients get a new ip address or by
> rebooting the m0n0wall. We have at maximum 150 - 160 clients connected to this
When this happens try and see if a "broken" client can connect to the
http://m0n0wallip:8000 which is what the captive portal is supposed to
redirect to. This will tell you if it is a redirect issue, and we can
go from there.