I'm having an odd problem with my wireless setup. At boot-up, it seems to find the access point and connect alright, but the network is completely unavailable. The only hint of trouble is 3-4 copies of the message "Error -110 setting multicast list". Here's the log:

Detected Orinoco/Prism2 PCI device at 0000:00:12.0, mem:0xE8103000 to 0xE8103FFF -> 0xcfa3a000, irq:9
Reset done.........[snip]....;
Clear Reset.........[snip]....;
pci_cor : reg = 0x0 - FFFC60EC - FFFC5EF8
eth1: Station identity 001f:0001:0001:0004
eth1: Looks like an Intersil firmware version 1.4.1
eth1: Ad-hoc demo mode supported
eth1: IEEE standard IBSS ad-hoc mode supported
eth1: WEP supported, 104-bit key
eth1: MAC address 00:E0:00:87:F3:65
eth1: Station name "Prism I"
eth1: ready
eth1: Error -110 setting multicast list.
eth1: Error -110 setting multicast list.
eth1: Error -110 setting multicast list.
eth1: Error -110 setting multicast list.
eth1: New link status: Connected (0001)

And I think everything looks good in ifconfig:

eth1 Link encap:Ethernet HWaddr 00:E0:00:87:F3:65
inet addr:192.168.10.51 Bcast:192.168.10.255 Mask:255.255.255.0
inet6 addr: fe80::2e0:ff:fe87:f365/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:78 errors:0 dropped:0 overruns:0 frame:0
TX packets:35 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:25518 (24.9 KiB) TX bytes:4068 (3.9 KiB)
Interrupt:9 Base address:0xa000 Memory:e8103000-e8103fff

It even seems to be communicating with the network (RX & TX packet numbers with no errors), if I'm reading those right. However, I am unable to reach any point on the network, even the access point itself with a ping. Instead, I get:

From 192.168.10.51 icmp_seq=1 Destination Host Unreachable

To get things going, all I have to do is "ifdown eth1; ifup eth1". Exact same settings, and I get the same error messages, but this time everything works. And no change in the ifconfig output either.

I don't know if that error has anything to do with the problem -- I've found a few other people reporting the same message, but none of the responses have ever included a solution or even explanation.

I also occasionally have the connection return to this non-functioning state, but reseting the port always gets it going again. This doesn't happen often, but when it does, it will often happen several times in the course of an hour, before settling down again. I get a little vocal during these episodes.

So, any ideas? I really love to get to the bottom of this. I guess I can try to automate the ifdown/up restart process, if necessary, but I'd rather actually solve the issue, if possible. It does significantly slow down startup when other tasks are trying to hit the network and the system has to wait for them to timeout.