I have a WAC730 that need to go back to standalone. It has a centralized management type firmware on it. I've connected to it via console cable and I connect and logon as root and use password to logon (i've reset it to factory default). I then launch firmware-upgrade-tftp <filename> <tftp-server-ipaddress>" It connects to my TFTP server, downloads the 3.7 firmware and starts the upgrade. BUT during this I see several times it cannot copy files or create directories as the file system is in read only mode. Is there a command I need to run before the firmware-upgrade-tftp command to give root the rights to create directories and copy files?

I was able so solve this. I setup a TFTP server and copied the 3.7 firmware to my tftp directory.Then I used a console cable to access the WAC730 independant of the network. I tried running firmware-upgrade-tftp firmware.tar 192.168.1.29 which did copy the file and try and run the upgrade but this is where it would fail due to read only restrictions preventing the upgrade. So I found a command on the console to simply TFTP the .tar file to the /tmp folder on the WAC730. Then once it was in place I ran another script called firmware-upgrade or something like that pointing it at the newly copied firmware.tar file That let the WAC730 perform the firmware upgrade successfully this put it back to normal firmware where I could logon and change it to standalone.

Forum Discussion

Galljc

Aspirant

Jun 01, 2017

Solved

WAC730 Back To Standalone Mode Via Console

I have a WAC730 that need to go back to standalone. It has a centralized management type firmware on it. I've connected to it via console cable and I connect and logon as root and use password to logon (i've reset it to factory default).

I then launch firmware-upgrade-tftp <filename> <tftp-server-ipaddress>"

It connects to my TFTP server, downloads the 3.7 firmware and starts the upgrade. BUT during this I see several times it cannot copy files or create directories as the file system is in read only mode.

Is there a command I need to run before the firmware-upgrade-tftp command to give root the rights to create directories and copy files?

Firmware

Galljc
Jun 02, 2017
I was able so solve this.

I setup a TFTP server and copied the 3.7 firmware to my tftp directory.
Then I used a console cable to access the WAC730 independant of the network.

I tried running firmware-upgrade-tftp firmware.tar 192.168.1.29 which did copy the file and try and run the upgrade but this is where it would fail due to read only restrictions preventing the upgrade.

So I found a command on the console to simply TFTP the .tar file to the /tmp folder on the WAC730. Then once it was in place I ran another script called firmware-upgrade or something like that pointing it at the newly copied firmware.tar file

That let the WAC730 perform the firmware upgrade successfully this put it back to normal firmware where I could logon and change it to standalone.

3 Replies

RaghuHR
NETGEAR Expert
Jun 02, 2017
Hi Galljc

Is your WAC730 managed by any Netgear wireless controller earlier? Have you tried factory reset after the tftp transfer completes?

Thanks

Raghu
- Galljc
  Aspirant
  Jun 02, 2017
  Is is not but I suspect it was in a former life. I did resolve this by using the console and TFTP to copy over the firmware and run it from the busybox shell that put it back to 3.7 standalone
Galljc
Aspirant
Jun 02, 2017
I was able so solve this.

I setup a TFTP server and copied the 3.7 firmware to my tftp directory.
Then I used a console cable to access the WAC730 independant of the network.

I tried running firmware-upgrade-tftp firmware.tar 192.168.1.29 which did copy the file and try and run the upgrade but this is where it would fail due to read only restrictions preventing the upgrade.

So I found a command on the console to simply TFTP the .tar file to the /tmp folder on the WAC730. Then once it was in place I ran another script called firmware-upgrade or something like that pointing it at the newly copied firmware.tar file

That let the WAC730 perform the firmware upgrade successfully this put it back to normal firmware where I could logon and change it to standalone.