Cisco Home Community

[justinsg]

The support details so far:

http://dl.dropbox.com/u/1962276/Support%20Contacts.pdf

Message Edited by justinsg on 12-08-2009 05:09 PM

[Satch]

---

justinsg wrote:

The support details so far:

http://dl.dropbox.com/u/1962276/Support%20Contacts.pdf

Message Edited by justinsg on 12-08-2009 05:09 PM

---

Brilliant work justinsg.  If you can get some real action out of this then you will make a lot of very unhappy WAG160N owners very happy.

Please keep us informed on your progress.  Cheers.

[popen]

---

justinsg wrote:

The support details so far:

http://dl.dropbox.com/u/1962276/Support%20Contacts.pdf

Message Edited by justinsg on 12-08-2009 05:09 PM

---

Great Job...

[justinsg]

Cheers, I could swap my router for another brand, but I like this Linksys one - it just needs a tweak!

Also can someone just post a brief explanation of what they think the error is with the firmware/router. I have a fairly good theory that the AP Isolation is not staying disabled, but there are other posts suggesting that this stems from an even deeper problem, to do the bridging interfaces and/or the ARP/RARP requests et. (which I don't know a lot about  )

Message Edited by justinsg on 12-10-2009 02:49 AM

[popen]

Well, I'm not an expert. But what I found was that wag160n does not respond to ARP request packets when the dropouts occur.

ARP is a protocol by which a host can ask for a physical or MAC (layer 2) address of another host when it only knows its IP address. When a host needs to send a packet to another host on a lan, it needs its MAC address. When the dropouts occur, the ARP request packets from a wireless host destined to the router are not given any response and therefore, that host can not communicate with other hosts.

You can take a look here:

http://www.osischool.com/protocol/arp/basic/index.php

There's a flash animattion simply illustrating the mechanism

[ra66i]

This thread needs to be stickied.

[Satch]

Any further updates on your quest justinsg?

[justinsg]

Yup - waiting for a callback from the Cisco/Linksys headquarters in California (I am in New Zealand but I have been waiting for a bit...)

@popen: Thanks for that, I understand completely now what's going wrong

Message Edited by justinsg on 12-14-2009 08:47 PM

[Satch]

---

justinsg wrote:

Yup - waiting for a callback from the Cisco/Linksys headquarters in California (I am in New Zealand but I have been waiting for a bit...)

---

I live in Auckland.  Please keep us informed mate.

[ra66i]

Justin - Next time you speak to them, could you also point out that by not putting the WAG160N GPL code pack up on their GPL site, they're also in GPL violation for the software on this router right now, and this is illegal.

http://www.linksysbycisco.com/UK/en/supportgplcode?gplsku=#WAG160N