Installation

[generic-pc-serial should now be used for PC Engines and Soekris boards]

Hello,

I’m bit confused with suggested procedure when upgrading from 1.3x, in my case 1.34 version to the latest 1.8.1.  So, please bear with my greenhorn preventive curiosity

Suggested :  "Go to http://m0n0wall/exec.php, enter the following command and click "Execute":

umount /ftmp && /sbin/mdmfs -s 16m md1 /ftmp

or in my case :

Where to go from here? Does one needs to use the area below and actually upload something, or after executing go straight to M0n0wall’s, System/Firmware area and proceed in usual fashion?

Also : http://www.abload.de/img/rename2zveci.png

I’m running 1.34, how do I check whether I’m using "embedded image" or not? Where do I look for this?

Probably silly question, buy your announcement insists on : generic-pc-serial should now be used for PC Engines and Soekris boards

But you offer both versions : http://www.abload.de/img/image99c68.png

I don’t use serial console, so can I use the first version?

Thanks for your assistance

Maybe I am mistaken, but I don't understand your abload.de URL. Where do you get it?
To my understanding - beware, I have yet to do the upgrade! - the http://m0n0wall/exec.php means YOUR router running m0n0wall! I actually don't get to it like this here, but it is always possible to use the IP-address followed by /exec.php.

Therefore, shooting into the dark, I guess what is meant is:
Download the image from http://m0n0.ch/wall/downloads.php
"Enable Firmware upload"
http://you.r.IP.add/exec.php
Enter umount /ftmp && /sbin/mdmfs -s 16m md1 /ftmp
"Execute"
"Chose File"
"Upgrade Firmware"

Keep your fingers crossed!

Uwe

P.S.: One probably has best two tabs open to the m0n0wall router for the whole process

Hi,

@Curtis, You should proceed as stated by udippel.
Beware that between "Execute" and "Choose File", you should point your browser to http://you.r.IP.add/system_firmware.php.
What is your platform ? A regular PC w/ keyboard and monitor ?

@udippel, for the  abload.de URLs, he just made screenshots of portions of the following pages:
- http://m0n0.ch/wall/upgrading.php
- http://m0n0.ch/wall/downloads.php
and he uploaded them to some file sharing service.

Pierre

Therefore, shooting into the dark, I guess what is meant is:
Download the image from http://m0n0.ch/wall/downloads.php
"Enable Firmware upload"
http://you.r.IP.add/exec.php
Enter umount /ftmp && /sbin/mdmfs -s 16m md1 /ftmp
"Execute"
"Chose File"
"Upgrade Firmware"

Yep. Here's a bit more what I hope is clarification:

I enabled the firmware update function.

Then I opened a second browser tab, and entered "http://192.168.1.254/exec.php" which brings up the page wherein one can enter that "umount /ftmp && /sbin/mdmfs -s 16m md1 /ftmp" and hit Execute. That all worked fine.

But then, if you 'upload the image file' using the features on that page, all it does is upload the file to a tmp directory, presumably on the Monowall. And then what? You stand there with your ham sandwich or other appendage in hand.

What worked for me, and what is not clear in the Upgrade instruction, is going back to the update firmware page:

http://192.168.1.254/system_firmware.php

and doing the update from there in the usual fashion. The img file is, of course, on a hard drive or USB stick or somesuch, and is uploaded from there.

But ... that business of renaming the file to embedded-1.8.1.img? All that gave me was an error to the effect that that was not the correct image file. So I dropped back and punted ... and did the update - still from that system_firmware.php page - using the file as downloaded with the original name. That worked. The system rebooted, and I waited with bated breath to see what version would be reported - still on 1.34? or on 1.81?

Joy to the world! It came up as 1.81, and all is as it should be.

To reiterate: Keep two browser tabs open. One for the http://192.168.1.254/system_firmware.php page and one for the http://192.168.1.254/exec.php page. The IP address will, of course, be the IP address of your device.

Enable the firmware update on the system_firmware.php page

Execute the umount /ftmp && /sbin/mdmfs -s 16m md1 /ftmp command on the exec.php page. Then go back to the system_firmware.php tab and upgrade with the generic-pc-serial-1.8.1b561.img file.

The system will reboot in the usual manner after updating. You can observe that if you have a concurrent console connection. Once that's done, refresh your browser on your device's page, and it should show the properly accomplished update.

That's my story and I'm a-stickin' to it. This is on the Soekris 5501-70

Having 2 browser tabs open at the same time in Chrome made all the difference, thanks for the tip. Both on an ancient WRAP unit and a Generic PC unit.

Great to have a new version with all the fixes and additions, monowall rocks!

[But lets go with your quotes]

@Udippel, Pierre Nast, DinkyDauBilly,

Thank you for your kind assistance, before I explain my present outcome, forgive my, almost didactic insist on making a few thing more clear. I was really furious yesterday, because stacked with work, and m0n0 email update, made me passive with my update, and omitting a thing or two. By the time you provided inputs, I’ve already started, and almost forgot about this topic.

Well, hasty action, was doomed with equal fate.

I’ve failed to grasp from m0n0wall-announce that new rule for memory is 128mb, and this is where fun begins for my episode.  I’m not sure whether my installation was well executed on my behalf, but will cover this when answering your replies. According to m0n0, 1.8.1 it is : http://www.abload.de/img/badinstalli4sc2.png

After each boot, renew interface is denied… until I actually switch off, and then switch On my HP Switch, then, mono 18.1 is willing to speak, but, WAN is of no use : http://www.abload.de/img/b-interface61sh7.png

Could my lack of memory  (96mb) be the primary reason for this?


But lets go with your quotes

@Curtis, You should proceed as stated by udippel.
Beware that between "Execute" and "Choose File", you should point your browser to http://you.r.IP.add/system_firmware.php.

This is where you lost me, after "unmount /ftmp && /sbin/mdmfs -s 16m md1 /ftmp"

your "Execute" warning, after unmounting : http://www.abload.de/img/a-executejssqc.png

I simply left to another tab and went with firmware.php procedure.

Is this what constitutes you order?  Or something, that I clearly do not understand, should be done in execute command area?

What is your platform ? A regular PC w/ keyboard and monitor ?

Indeed, a regular PC (Supermicro + CF Flash)….

But then, if you 'upload the image file' using the features on that page, all it does is upload the file to a tmp directory, presumably on the Monowall. And then what? You stand there with your ham sandwich or other appendage in hand.

Precisely, what made me confused : http://abload.de/img/a-executejssqc.png

http://192.168.1.254/system_firmware.php
and doing the update from there in the usual fashion.

Yes, that is what I did, as it made only sense, after not going anywhere with "uploading the file" area.

But ... that business of renaming the file to embedded-1.8.1.img? All that gave me was an error ....

Again, exactly the same situation,  with renamed image, any attempt to write to CF resulted : http://www.abload.de/img/backupfaill8sdx.png

Well, assuming my obstacle is the lack of memory, and I will deal with that, at the end of this week, I hope, there is no other reason, 18.1 is not working on my m0n0.

Restoring from 1.8.1 to 1.34 is no go, so I’ve made a fresh 1.34, and restored my previous configuration.  But I really like to update 1.8.1.

Thank your for your patience

the update instructions have been changed, 1.34a has been released, the only change is that it will handle the large 1.8 image, so you don't have to follow all those steps.

This is a very good thing! 

the update instructions have been changed, 1.34a has been released, the only change is that it will handle the large 1.8 image, so you don't have to follow all those steps.

Yep, thanks a lot! - Though it is still confusing: Here I was careful and read the instructions and ... renamed the generic-pc-serial-1.34a.img to embedded and upgraded. There simply is no embedded-1.34a.img; so one HAS to do it! Step 1 done. Fine.
Then I downloaded generic-pc-serial-1.8.1.img and followed Step 2. Puff! - A red warning pops up that the version is wrong and I actually do need the generic-pc-serial-1.8.1.img.

In a nutshell my suggestion:
"1. Install version 1.34a for your platform first.
If you're currently running the 'embedded' image, download file generic-pc-serial-1.34a.img and rename the downloaded file to embedded-1.34a.img
(There is no separate version for embedded systems any longer: from now on your platform is generic-pc-serial)
2. Download file for 1.8.1 for your platform.
3. Upload the new firmware image."