I've seen all of that... I've also investigated the solution and unfortunately I know nothing about a hex-editor so I can't really do what has to be done. essentially I understand it like this: each firmware has an OEMid# in it, a checksum that has to match what the device has programmed into it or it won't accept the firmware. when you converted your wap, you changed the number it expects to be the dlink ID. now you get checksum errors when you try to reload the firmware... that's what happened to me. Andrew Hakman (http://www.andrewhakman.dhs.org/wap11/) is the one who tuned me in that far and from there he lost me... Basically I understand it to be this: someone needs to use a hex editor to open the linksys firmware and change it's OEMid to be that of D-links OEMid. I'm betting someone has already done it, we just need to figure out who.
I actually ended up just buying new waps (sadly enough) but I've been using the dlink-enstein's as client bridges which works out pretty well... question for you: which firmware are you using and maybe give some details of any modifications to the original settings you have made. I eventually got mine to run pretty stable, but I think they are adversely affected by some variety of card I had connecting to my network that is now gone. further suggestion: enable mac filtering and add one client at a time and see if you can find the link that makes things unstable. good luck. please keep me/us posted if you learn of a real fix for this. ----- Original Message ----- From: "brad dreisbach" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, March 21, 2003 7:54 AM Subject: [BAWUG] wap11/dlink problem > i installed the dlink firmware on my linksys wap11 v2.2. > ever since i have been having major problems. i am having > problems reaching wireless devices from my wired network. > im seeing packetloss sometimes, complete lack of connectivity > other times, duplicate packets. now...on the wireless side... > i cant even communicate at all between wireless devices. > i did manage to be able to do so pings across the wireless > when i turned the ethernet card of the source machine into > promiscuous mode(running tcpdump). has anyone else seen > this problem? ive also not been able to use ipv6 or multicast > over the wireless. is there an easy way to revert back to > the linksys firmware? i dont have another linksys or any of the > linksys images. > > -b > > -- > general wireless list, a bawug thing <http://www.bawug.org/> > [un]subscribe: http://lists.bawug.org/mailman/listinfo/wireless -- general wireless list, a bawug thing <http://www.bawug.org/> [un]subscribe: http://lists.bawug.org/mailman/listinfo/wireless
