 sn9 join:2010-12-30 San Francisco, CA kudos:1 | SS6300: Least buggy/most complete firmware?Years ago, I purchased a SpeedStream 6300 retail here in the USA, and it came with firmwar e 004-E771-A28, of which I no longer have a backup due to a hard disk failure, nor do I ha ve the A3F updater anymore, but I do still have the x.img and x.def backups from A3F if I need them. Currently, what's on the device is as follows:xsh> show sys versions Series: 6300 Firmware: 004-E771-A6X Build: 91-78 Config: 003-6045-G0L DSL: a0_22f Wireless: 3.31.12.0 with C0 and SROM mods xsh> cfg sys{cfgv cfgv desc = "Full Router GA configuration." pnum = "003-6045-G0L"
The config I extracted from the 004-D241-A69 updater for the 4200. Given this config, would A6X (Bell Canada Business Internet) be preferable over A3F? A3F is described as very buggy elsewhere in these forums, and it's unclear to me what the limitations on A6X are with the 6045 config as opposed to A3F with 6045 (instead of the 6144 in the A3F updater). Is it a tradeoff? Should I put A3F back? Also, would any firmware allow a bridged circuit to use NAT and/or NAPT while still bridging it to the LAN? Thanx |
|
 | Bell's firmware tends to be locked down, it also allows for their agents access (via the Internet side) into the modems settings, and as such I wouldn't recommend it. |
|
 sn9 join:2010-12-30 San Francisco, CA kudos:1 | Even with the Full Router GA configuration? I'm in the USA and have never had any connection to Bell Canada. |
|
 | Well the backdoor is built into Bell's (Bell Canada) firmware so although they would not have access (Bell Canada does not operate in the US) it might allow your current ISP access or someone else. I am not sure how its done (what is the mechanism that allows them access) other then they do remotely configure and control that model if a customer is having problems (user lost password, miss configured other settings etc.) |
|
 sn9 join:2010-12-30 San Francisco, CA kudos:1 | There is a standard protocol for doing exactly that, called TR069. I'm pretty sure that's been in any firmware for some time now. |
|