DWL-G810 wireless bridge
I bought this D-link DWL-G810 wireless bridge a couple of years ago to connect a network segment in the basement of our house to the rest of the computers and the internet, since connecting them by real UTP cables proved pretty much impossible.
On the outside it's a simple box that has an ethernet socket on one end and a 802.11g connection on the other. What ever device you connect to it behaves like it would be connected by a wired network to all the computers on the local network, including those that are actually on the wireless LAN.
Well, that's the theory at least. In practice, I never could get it to work properly. The connection kept dropping, DHCP requests wouldn't get through and so on. Very annoying, since even once a machine managed to get an IP only each other webpage would open in a browser. So it has been accumulating dust in a corner ever since.
Now I've noticed that D-link released some new firmware updates (which is pretty surprising for a device that will soon be 3 years old). It's quite confusing though, since you got U.K., German and Australian departments of D-link, each claiming a different version of the firmware is the latest. And apparently this product has been discontinued in U.S.
I've tried 3.16b77 (from the German site), 3.15b70 (from the U.K. site) and 3.15b73 (from the Australian site).
I've had most success with 3.15b73. So far, I haven't seen any connection drops with it and it also has the added bonus that the admin page can be accessed from the wireless side, which seems impossible with other versions. Interestingly, other two versions didn't bring any obvious improvements over the old 2.2 firmware, although they appear to be newer.
The device still has some interesting properties though. For example, inbound traffic that you send to its IP via the wireless interface can be seen on the wired side, which is weird. So if you ping it from Wi-Fi, you see your ping packets on the wire with tcpdump, but not the answers. Same for HTTP traffic to the admin page (including the plain-text password for HTTP basic authentication).
It's also constantly searching for multicast-capable clients on the wireless side for some reason (no idea why):
21:41:28.394980 xx:xx:xx:xx:xx:xx (oui Unknown) > Broadcast, ethertype ARP (0x0806), length 60: arp who-has ALL-SYSTEMS.MCAST.NET tell 0.0.0.0
For the record, this is hardware H/W Ver: C1 (product number ending with BEUC1) and I'm using it with a WPA-PSK protected network.
I have been running the C firmware on B units, without any problems; this is welcome since the C version is not available in the United States.