GS748TS web interface issue when configuring LAGs

This is strange, I am using Chrome 33 and IE 11.0.3 and see everything on the LAG and VLAN screens. I am having a VLAN issue related to the actual traffic behavior, which is what brought me through this thread, but after checking against those two and Firefox 3.5.6 all the ports and their config states show up with no problems.

This has cost me hours until I found a reference somewhere else pointing into the direction of an old Firefox. BTW: you can use Firefox Portable 19.x.y as well, it'll work.

The NetGear webinterface is completely in javascript and somwhere in processing the result something goes wrong. I had a case open with an engineer who came up with 3.5.6 as well (but I already knew). I have complained that a switch that is still sold is no longer manageable with a normal browser. First response: this switch is EOL, see our list. So I glanced at the list and said: but hey, here is a strange thing... the switch might be EOL but it is also advertised as a switch that is a replacement for another type that is EOL. That is a bit confusing for your dearly appreciated customer.

The last rumour I heard is that a maintenance update for the firmware is being considered to solve this issue.

F

Hi All,

I used to be able to configure it using Chromium Browser from a Linux box (Lubuntu 12.10), but it didn't work for me today (latest Chrome from Linux Mint 17).

Luckily I was able to configure it while using Safari browser on Mac which is not an option for many people, but possibly Safari on Windows will work as well. Also, some but not all problematic features of the interface were configurable from default Android browser on my ASUS TF701T tablet.

Hope it will help.

PS: Update to 5.0.10 firmware does not solve the problem.

I confirm that the latest Safari for Windows ( v.5.1.7) allows accessing all features of the web interface.

Hit by this issue too.

This is definitely a ProSafe "Lifetime Warranty" issue since it is no longer possible to configure the hardware.

For sites with policies mandating specific application versions Netgear's suggestion in Support answer 238341 to use an obselete browser is not a solution.

I consider it unacceptable that Netgear's recommended 'solution' is to use an unsupported, insecure, web browser, instead if simply fixing the Javascript bugs in the web interface and pushing out a firmware upgrade.

iam_TJ wrote:

Hit by this issue too. This is definitely a ProSafe "Lifetime Warranty" issue since it is no longer possible to configure the hardware. For sites with policies mandating specific application versions Netgear's suggestion in Support answer 238341 to use an obselete browser is not a solution. I consider it unacceptable that Netgear's recommended 'solution' is to use an unsupported, insecure, web browser, instead if simply fixing the Javascript bugs in the web interface and pushing out a firmware upgrade.

Expecting them to push out a firmware fix for this is unlikely. Download an older version of Lightweight Portable Security (which has a built-in browser) and use that to configure it. Free easy workaround.

SamirD wrote:
Expecting them to push out a firmware fix for this is unlikely. Download an older version of Lightweight Portable Security (which has a built-in browser) and use that to configure it. Free easy workaround.

Speaks volumes to Netgear's lack of serious support for ProSafe though.

As to fixing it, I've already re-written part of the code so it works, as a proof-of-concept that I can successful write and install my own firmware images. If I can do that, then Netgear can for sure.

iam_TJ wrote:
Speaks volumes to Netgear's lack of serious support for ProSafe though. As to fixing it, I've already re-written part of the code so it works, as a proof-of-concept that I can successful write and install my own firmware images. If I can do that, then Netgear can for sure.

It does, but unfortunately this is common for any of the smb router manufacturers. (I've seen this with Cisco rv series as well).

That is awesome that you can write the firmware changes yourself! Please share! I'm sure others would love to your version of firmware.

SamirD wrote:
That is awesome that you can write the firmware changes yourself! Please share! I'm sure others would love to your version of firmware.

I will make sure the process is bullet-proof before I publish the details since I don't want other, probaby non-technical, folks bricking their devices! It will require use of specialised tooling on a Linux workstation.

I can't simply publish firmware images since, unless *everything* is re-written from scratch, it would infringe on the Netgear copyright - unless other device operators want to cooperate on an opne-source implementation :)

iam_TJ wrote:

I will make sure the process is bullet-proof before I publish the details since I don't want other, probaby non-technical, folks bricking their devices! It will require use of specialised tooling on a Linux workstation. I can't simply publish firmware images since, unless *everything* is re-written from scratch, it would infringe on the Netgear copyright - unless other device operators want to cooperate on an opne-source implementation :)

I agree, although if they mess up, it's their own fault. The consumer side of third-party router firmwares has already sorted out that liability.

True, unless Netgear has used open source in their code. Also, you could just provide a custom service that someone needs to contact you--this way you control the distribution.