[HOWTO] Installing OpenWrt on Check Point L-50

Why don't you use a Debian, Ubuntu or Fedora live distribution booted from a USB stick?

1 Like

WSL could have all kinds of weirdness when it comes to underlying hardware... If you're on Windows, I would suggest using Putty.

Define at first what is proper serial port.

Recently acquired one of these and there are a few things that should be noted:

  1. mtd1 is the u-boot env partition, not mtd2. Make sure you select the correct partition when making backups. I would personally recommend backing up all partitions anyway just to be safe.
  2. kwboot shipped from u-boot 2022.04 and onward requires the -a (use timings for Armada XP) option, otherwise it will be able to interrupt the boot process, but won't actually start sending the boot image. -p can be dropped now since images will be automatically patched when required.
  3. Make sure you save the environment variable with saveenv after setting the MAC addresses, otherwise the ethernet interfaces will not come up.

The wiki will be updated once I get my account approved.

1 Like

Hi all,
OK i really and seriously tried it dozens and dozens of times !!! Without success until....

So, all my tests was on LiveCD or installed Ubuntu. I tried it on Ubuntu 20 and 18. Same issues.
The computer has a real RS232 port. (!!! NO USB RS232 converter !!!).

Everytime, issues were about:

  • "xmodem: Connection timed out"
  • "xmodem: Bad message"

Also, to send the boot image, it took each times about 10 minutes.
The display was something like:

60 % [+.......+..+..+..+..........++.......+....+....+...+]
61 % [+.++.+..+..+..+..........++.......+................+]

Like if many disconnections happened during the tranfer.

Anyway, after trying all the different ways available on the openwrt forum...

i tested another OS.
I installed a Mint version 20: https://www.linuxmint.com/edition.php?id=281

Fresh install. Nothing more except...."screen" and "u-boot-tools"

sudo apt install screen u-boot-tools

Then, the command to see the matrix (don't forget that i had a real serial port, S0):

sudo screen /dev/ttyS0 115200

And:

sudo kwboot -B 115200 /dev/ttyS0 -b u-boot.kwb -p -t

Power On the checkpoint.

ANNNNNDDDD.... Magic ! It took seriously 45 SECONDS to transfer the boot image.

This time, the transfer appeared like "normal":

60 % [....................................................]
61 % [....................................................]

Once arrived to the goal for my first time: " => ", I screwed the installation with the unclear "fw_setenv ethaddr" or "eth0addr" or "setenv" etc etc.
I wasn't able to get an ip or whatever else from the network ports.

So i started over the installation / tranfert about the boot image.

IMPORTANT !!!
A thing that i saw a lot of time during my tests !!
Power off and power on the Checkpoint wasn't enough to start over the process in a clean way. Like if something was stuck to the current session.
When i powered on the Checkpoint, i saw the firmware being loaded but like a corrupted one... all caracters was mixed !

To fix that, easy peasy, reboot your damn computer.
Once rebooted, i started over the whole process and like the latest time, 45 seconds to send correctly the image.

So... to determinate if you have to use "setenv" or "fw_setenv", it's easy... just type it :). One of them will answer with a command not found.

About the "eth" to set i had this config:

[Expert@MAINTENANCE_MODE]# fw_printenv
[...]
hw_mac_addr=00:1C:7F:xx:x:x
ethaddr=00:1C:7F:xx:xx:xx
eth1addr=00:1C:7F:xx:xx:xx
lan1_mac_addr=00:1C:7F:xx:xx:xx
lan2_mac_addr=00:1C:7F:xx:xx:xx
[...]

BUT to set it, i wrote:

setenv eth0addr=00:1C:7F:xx:x:xx
setenv eth1addr=00:1C:7F:xx:x:xx
setenv lan1_mac_addr=00:1C:7F:xx:x:xx
setenv lan2_mac_addr=00:1C:7F:xx:x:xx

I got the IP address from my home router and then... followed the rest of this tutorial !

Summary :slight_smile: :

  • Mint 20 installed
  • REAL RS232 port.
  • Computer rebooted if you have to start over the boot image transfer.

I hope this tricks will help you !