Retarded, there is clearly a firmware problem with the AM300. It is passed the wrong subnet mask ip to the WRT when the default gateway is on a different subnet than the wan ip. Other PPoA half bridge modems from different companies handle the situation fine. It's probably just an oversight in the code.
... and no we can't use PPoE for because the network is PPoA.
Dynalink 1320's go for about $20 on trademe and work fine FYi
Hmmm, yeah, the only problem with Dynalink modems are they're utter SH!TE!!! Connect speeds & stability are generally complete rubbish with those eh. Pretty much the same for DLink really.
Yeah, except when they are overheating themselves... - of cource they blame the reseting on the line conditions like the line could cause the OS on the router to crash.
Be aware with the dynalinks halfbridge that it fakes the gateway address so sometimes you find IPs that are similar to yours inaccessble since it would be on the local subnet.
Just got a reply from Linksys. The issue has been handed to their software engineers. I'll be told when they release a firmware update. Will keep you posted.
We too have had issues with the subnet issued from the AM300. Our *nix router has two wans, two AM300's in Half Bridge. when both WAN NIC interfaces on the router got the same subnets everything stopped.
This "Partial" workaround only applies to those who get static IP's untill new firmware.
-- Statically assign your WAN interface on your router with the /32 space (255.255.255.255) and leave the modem in half bridge mode. The AM300 thinks the WAN interface has been DHCP'd.
Lorenceo: Linksys sure seem to have this problem on the back burner..
Seconded, I've tried contacting them numerous (5+) times. After a lengthy wait period the tech I talk to promises me that a senior technician or engineer will call me back about the problem and that they'll keep me posted on progress. I haven't recieved any calls or emails from them, except an email with the current 1.19.02 firmware attached that they tried to tell me was a beta firmware! I ran a checksum analysis on it, and had to prove to the tech I spoke to about it that the file I was sent was exactly the same as the current firmware.
I realised that the process might take a while, so I grabbed my overheated and mostly dead Dynalink RTA1320 and called Dynalink support. It was just under waranty, so I sent it away for repair and recieved a brand new unit 4 days later that's working perfectly. Thumbs down Linksys, thumbs up Dynalink.
I'm starting to get annoyed with Linksys to the point where I'll ask for a full refund for the AM300 because it's not f***ing working propperly. Sorry to moan at you guys, I just hope someone with a bit of power at Linksys reads this thread and does something about it, but I'm not holding my breath.
Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly
to your computer or smartphone by using a feed reader.