David Burgess wrote:
> On 7/25/07, Lee Sharp <leesharp at hal dash pc dot org> wrote:
>> David Burgess wrote:
>>> The only possibly related complaint I am aware of is that some
>>> customers are unable to get an address from monowall via dhcp and must
>>> therefore use a static IP address, but this is relatively rare and
>>> seems to be a different problem (one that is apparently exclusive to
>>> Linksys clients, I might add).
>> I think the DHCP issue is a symptom of the problem. The fact that you
>> have two networks on one collision domain could be adding to this. What
>> does your arp table look like during this? Look at the arp on m0n0wall,
>> the switch (if you can), the APs (you should be able to here) and the
>> clients both while functional and while broke. I am betting a corrupt
>> arp table in the network.
> This issue remains unresolved and we've had the odd other complaint.
> When we implemented an OPT1 interface (bridged to WAN) on our formerly
> unaffected monowall (~300 LAN clients), we immediately received
> complaints from several customers, most of them using new DLink
> routers (particularly the new black and orange/white models) and some
> using direct PC connections.
> The symptoms are always the same: dhcp renewals work fine but
> connectivity to the monowall is intermittent. This is only an issue
> when OPT1 is enabled. Only the LAN is affected, OPT1 clients are not.
> Mono's arp table looks healty, no duplicate entries, nothing out of
> ordinary in the logs.
Did you ever do an 'arp -a' on the clients? Both healthy and broken for
comparison... Also a 'route print' for windows machines as well just
for giggles. :)