Openwrt на виртуальной машине

OpenWrt on VMware HowTo

This article describes how to use OpenWrt as a virtual machine with VMware virtualization.

Tested with

Things you need

First of all, you need to download the image from list above on your machine. After that you extract & convert it to a vmdk image:

On Fusion I had to use the IDE drive controller type.

Quick Start

Follow these steps to get an Up to Date VM with the latest code running on ESX in 15 minutes:

Testing

Here are some results from my system:

ToDo List

(Is there a better place to make these requests?)

Disk Size Issues

Disk size and problems with veeam backup and enlarging the disk Veeam backup and VMware will complain about the size of the virtual disk provided by the OpenWrt download because the disk is not multiple of 1KB. (this means: no backups available, and could be crucial in production environments)

VMware won’t let you enlarge the disk in the normal way, so one simple way is:

Community

Please use these images in your home and work labs and provide any feedback you might have.

Feel free to update this wiki page with your results.

There is some feedback that the newer images are not booting properly. Has anyone else run into this issue?

Upgrade to 19.07.5 from ova

Here is an upgraded OVA VM export with version 19.07.5, using ext4 instead of squashfs and an extended /overlay filesystem, with DHCP enabled instead of a static IP for br-lan interface: https://www.dropbox.com/s/4b0dy8d8iqf8a91/OpenWRT_x86_64_19.07.05.ova?dl=0

Upgraded/Updated OVA for OpenWRT21

After import of the previous OVA-file to VMware Sphere, I was able to upgrade to the latest OpenWrt version (21-00-RC3).

Источник

OSBoy notes.

Установка OpenWrt на виртуальную машину

Создание виртуальной машины (ВМ)
Запускаем VirtualBox и жмём «Создать». Задаём имя, тип и версию гостевой системы:

Затем Выбираем созданную ВМ и жмём «Настроить». На вкладке «Сеть» настраиваем сетевой интерфейс для связи ВМ с внешним миром. Мой хост-компьютер подключен к домашней сети и интернет через роутер. Поэтому удобнее всего для ВМ будет использовать тип подключения «Сетевой мост». Таким образом ВМ будет выглядеть в сети как отдельное устройство: будет иметь возможность общаться с другими устройствами в домашней сети (включая хост-компьютер), выходить в интернет, получать от роутера IP адрес по DHCP и т.д.

На вкладке «COM-порты» нужно обязательно поставить галочку «Включить последовательный порт», иначе OpenWRT не сможет запуститься.

config interface lan
option ifname eth0
option proto dhcp Применяем настройки сети: /etc/init.d/network reload Чтобы ВМ получала от роутера фиксированный IP адрес, добавляем MAC-адрес виртуального адаптера в список постоянных аренд в настройках DHCP сервера на роутере и присваиваем ему нужный IP.

config interface ‘wan’
option ifname ‘eth0’
option type ‘bridge’
option proto ‘static’
option ipaddr ‘192.168.1.10’
option netmask ‘255.255.255.0’
option ip6assign ’60’

config interface ‘lan’
option ifname ‘eth1’
option proto ‘dhcp’

В VirtualBox версии 5.0.4 у меня наблюдался такой баг: виртуальные (гостевые) машины видели по сети роутер, друг друга, выходили в интернет, НО не видели хост-машину, так же как и хост-машина не видела гостевые! Баг вылечился обновлением VirtualBox до версии 5.0.6.

Расширение дискового пространства
Ну и теперь, когда у нашей ВМ есть выход в интернет, можно устанавливать все необходимые пакеты, например: opkg update
opkg install nano mc В скачанном образе OpenWRT корневой раздел размером около 48мБ. Этого вполне достаточно для установки пакетов первой необходимости и выполнения многих задач. Однако, если нам этого недостаточно, то увеличим виртуальный жёсткий диск. В VirtualBox вроде бы для этого есть специальный инструмент и можно в принципе воспользоваться им. Но я сделал иначе.
В настройках виртуальной машины подключим ещё один виртуальный жёсткий диск. Выбираем «Создать новый диск», затем задаём его название, выбираем нужный размер и формат хранения:

Источник

Русские Блоги

Сборка openwrt под vmware

Я недавно не был занят, и я хочу изучать openwrt, поэтому я попытался создать его для удовольствия. Конечно, это не в форме компиляции исходного кода, которая занимает слишком много времени.

Сначала загрузите образ существующей системы на официальном сайте. Путь следующий:

Установка Vmware не будет говорить, вы можете увидеть мой другой блог.

Используйте прямо под Ubuntu:

После завершения подготовки запускается среда openwrt.

Откройте VMware и выберите «Создать новую виртуальную машину».

1. Выберите «Custom (дополнительно)» в конфигурации виртуальной машины:

2. Нажмите «Далее», «Аппаратная совместимость оборудования виртуальной машины».

3. Перейдите к следующему шагу, выберите «Я установлю операционную систему позже». Из установки операционной системы:

4. Перейдите к следующему шагу, выберите «Linux» в гостевой операционной системе и выберите «Other Linux 3. Kernel» в версии:

5. Перейдите к следующему шагу, задайте имя виртуальной машины в поле «Имя виртуальной машины», просто назовите его случайным образом. Здесь установлено значение «openwrt-15.05». Если указан путь, который вы хотите сохранить, то здесь / home / Баллак / VMware / OpenWRT-15,05 /:

0

6. Перейдите к следующему шагу, оставьте процессоры и память без изменений:

8. Перейдите к следующему шагу. Типы контроллеров ввода / вывода могут оставить значения по умолчанию:

9, перейдите к следующему шагу, выберите тип виртуального диска IDE, Вы должны выбрать IDE здесь, иначе вы не найдете раздел при запуске ！！！

10, перейдите к следующему шагу, диск выбирает «Создать новый виртуальный диск»:

11. Перейдите к следующему шагу. Размер диска остается неизменным:

12. Перейдите к следующему шагу, просто оставьте файл диска без изменений:

13 Перейдите к следующему шагу, выберите «Настроить оборудование»:

14. Извлеките новый CD / DVD (IDE), звуковую карту, принтер и USB-контроллер, а затем закройте, чтобы выйти.

15, нажмите Finish и увидите следующий интерфейс, указывающий, что создание было успешным:

Выполнив описанные выше действия, не спешите запускать, сначала скопируйте файл openwrt-15.05.1-x86-generic-комбинированный-ext4.vmdk, полученный с помощью инструмента qemu-img, в рабочий каталог вновь созданной виртуальной машины openwrt

Введите рабочий каталог виртуальной машины openwrt и просмотрите файл с помощью команды ls:

Измените 1: 1.fileName = «openwrt-15.05.vmdk» на:

После настройки запустите openwrt:

Однако вы обнаружите, что хост не имеет доступа к openwrt через веб-страницу, здесь нужно только изменить файл / etc / config / network:

Пересмотренная версия выглядит следующим образом:

Затем сохраните, выйдите, выполните /etc/inid.d/network restart, чтобы перезапустить службу.

Затем хост пингует 192.168.1.4, в это время он может пропинговать:

Затем откройте браузер, введите 192.168.1.4, вы можете увидеть нормальный доступ:

Нажмите «Войти», интерфейс предложит вам установить пароль:

После установки пароля просто нажмите «Сохранить и применить».

После входа в систему с учетной записью root и паролем, который вы только что установили, вы можете увидеть настоящий интерфейс openwrt:

Интеллектуальная рекомендация

Разработка Android NDK (1)

Использование C ++ для реализации свертки простого двумерного изображения

Использование C ++ для реализации свертки двумерного изображения оглавление Использование C ++ для реализации свертки двумерного изображения Введение 2. Требования к проекту 3. Простые знания, связанн.

Кто действительно хочет узнать U3D, приди, я возьму тебя

Игра FreeShale Game Triver OLED12864 Отображает изображение для трека, совместное использование кода

Сначала сначала собирайте изображения камеры, потому что оборудование отличается, я не буду объяснять это. Во-вторых, бинаризация собранного изображения В-третьих, вызовите следующую функцию, чтобы от.

Источник

OpenWrt on x86 hardware (PC / VM / server)

OpenWrt can run in normal PC, VM, or server hardware, and take advantage of the much more powerful hardware the x86 (Intel/AMD) architecture can offer.

Download disk images

Go here, choose the release version, then click on target and then on x86. You will see different targets.

There are multiple targets for x86 OpenWrt, some are targeted at old or specific hardware and their build defaults may not be suit modern x86 hardware:

Now you will see different files offered, the following two are disk images you can download and use:

Hardware support

All images support basic video output (screen text terminal), so you can connect a screen to the device’s video ports and see it boot up.

Some images support keyboard input which can be used to configure OpenWrt.

To communicate through a PC serial port you will need a “null-modem” aka “crossed” serial cable to connect the device’s serial port to your PC’s serial port.

To be able to connect to your device, the image must support the Ethernet hardware.

NVMe SSD support is available since OpenWrt 21.02.

Installation

The installation consists of writing a raw disk image on the drive which will boot OpenWrt system. It may be a USB flash drive, USB SDcard reader with SDcard or in a SATA hard drive or SSD (recommended). You can do it either on a secondary PC, or booting the router machine with a Live CD/USB.

WARNING: writing raw image files DELETES the content of the drive you write them on, be sure that you are not deleting anything important, and that you have selected the right drive.

Windows / macOS

If you are using a Windows / macOS, you will need a program to extract the raw disk image from the compressed archive you downloaded. Then you will need to open the raw image file with a program that can write it on the drive you want to install OpenWrt on.

A good free and opensource archiver program you can use is 7zip, or Keka.

A good free and opensource raw disk image writer program you can use is Win32 Disk Imager, or Etcher.

Linux

Extract the image file from the archive. Most sane distros will let you do so by right click and then select “extract”, or you will have to open up your graphical archive manager and do it from there. Then write the image file you extracted to the drive you want to install OpenWrt in. Many distros include a disk image writer application such as GNOME Disks. Identify the disk you want to write the image on, e.g. sda, sdb, sdc, etc., and write the image with dd tool where using the previously identified drive name. Note you have to gain administrative privileges with sudo and write to the drive (sda, sdb), not to a partition (sda1, sdb3).

Installing OpenWrt in an internal drive

If you want to write OpenWrt in Sata or IDE drives or CF Cards or SD cards, you can just remove them from the device and flash the image raw from your PC. Also sometimes eMMC is removable or can be put in “usb write mode” in some devices.

But if you cannot remove the storage from the device (or do not have an adapter to connect them to the PC), you can write OpenWrt on a USB drive (or another removable storage device), then you can then insert it in a USB port or slot. When booting select the drive where you installed OpenWrt.

Then you need to identify how is the internal storage device called with lsblk or dmesg:

Be aware that you will also see the USB drive or the storage device you have temporarily installed OpenWrt on.

This for example is the output of a 4GB USB drive with 2 partitions on it that was assigned the name /dev/sda:

After you have identified the onboard storage you want to install OpenWrt in, you can follow the Linux install instructions above. Then power off the system, unplug the removable storage device you used to install OpenWrt, and power on again. Now it should boot from the internal storage.

Partition layout

The x86 image is using the following partition layout (as seen from inside of the device):

Any additional space in the device is unallocated.

Resizing partitions

An example fdisk operation on a 8GB flash drive:

Be sure to update the GPT partition UUID in the GRUB configuration when using efi.img.gz:

Resizing filesystem

Resizing F2FS overlay

Resize F2FS overlay for squashfs-combined.img.gz:

Resizing Ext4 rootfs

Resize Ext4 rootfs for ext4-combined.img.gz:

Adding extra partitions

When OpenWrt is installed on a x86 machine using generic-ext4-combined.img.gz, the drive’s partition table is overwritten, which means that any existing partition is deleted. Any remaining space will be unallocated and the drive will have a normal MBR partition table.

Any partition management tool that supports MBR and ext4 can be used to create extra partitions on the drive, in example fdisk, GParted.

But attention must be taken for future upgrades. If extra partitions are added, you cannot use -combined.img.gz images anymore, because writing this type of image will override the drive’s partition table and delete any existing extra partition, and also revert boot and rootfs partitions back to default size.

Upgrading

On most embedded devices, upgrading OpenWrt is much simpler than the first installation and consists of simply executing sysupgrade. On x86 machines, on the other hand, upgrading is more complex than the first installation.

One of the advantages of x86 is the easiness to backup and restore drives, using any normal backup tool that supports MBR and ext4. Always make a proper backup of the whole drive and test its restore before any upgrade procedure. It’s also recommended to restore the backup on a virtual machine and execute the upgrade on it prior to upgrading the real router, to learn and experiment the procedures without risking the real thing.

On all procedures on this section, we must either connect the drive on a secondary PC running Linux, or boot the router with a Linux Live CD/USB.

If you had used a ext4-combined.img.gz type of image to install, there are 4 options for upgrading:

The 2 last options require more steps to execute, but have the advantage of leaving MBR partition intact, therefore keeping boot and rootfs partitions sizes (in case of having resized them) and any extra partitions. At this time they are the most recommended methods of upgrading. The only exception is when new OpenWrt image brings a newer version of GRUB2. Part of GRUB2 is stored close to MBR and outside of partitions area, so we need to write a full ext4-combined.img.gz to update it.

Extracting boot partition image

The boot partition contains part of GRUB2 software, Linux kernel and grub.cfg with boot options. rootfs partition contains OpenWrt files, packages and configs.

At the moment, it’s not built a separated image file with boot partition, as it’s available for rootfs. To be able to upgrade boot partition without overriding the whole drive, we must extract it from ext4-combined.img.gz, this requires a spare empty drive or a virtual machine.

Upgrading rootfs partition

As said above, there are 2 options for upgrading rootfs partition, when we are using the ext4 file system and not squashfs: writing ext4-rootfs.img.gz image or uncompressing rootfs.tar.gz into existing partition.

For uncompressing rootfs.tar.gz, we must mount rootfs partition, delete all files from it, then uncompress updated files.

It may be tempting to not delete config files, but the risk isn’t worth it, because some file may conflict and not be properly upgraded. It’s safer to backup config files (as we should also backup whole drive before upgrading) and copy them back after upgrading. I suggest going further and having a Subversion repository on another computer where all config files are saved and their changes are tracked, and use rsync to sync between the repository working copy and production files on the router.

Building your own image with larger partition size

Anyone can compile OpenWrt from source, but it’s a complex procedure with many options which require some experience, specially for using it on a production router.

Different from compiling, we can build our own custom image using the Image Builder. This doesn’t compile the whole software, instead it downloads required packages from the same repository used by OpenWrt to install them. Image Builder builds the same image files used for installing and upgrading OpenWrt.

Due to that it’s much simpler than compiling and offers great advantages, like adding directly to the image all packages we need, removing those we don’t need, and also adding to it our config files. Having packages on the image, we don’t need to reinstall all of them after an upgrade. And having our config files directly on the image, we don’t need to reconfigure everything or copy all files from backup, which is specially difficult when default network configs don’t work with our router’s interfaces or it doesn’t start with correct IP address. In many cases, OpenWrt will be back fully working on first boot after upgrading.

Another advantage for building a custom image is when the default rootfs partition size is too small to store all packages and we need to resize it. Note that, when following above procedures of installing then resizing partition and upgrading by writing partition image or extracting rootfs.tar.gz, we don’t need to build the image with the final size of the partition. Doing so would result in the too large image file and would require enough RAM to store the whole file during building. It’s recommended to use on the image just enough size to store all packages plus a small amount of free space.

Follow the Image Builder tutorial to setup the building environment using the x86/64 target. Once the building environment is setup, we use the make image command to build an image, which results on a set of files with the types of images described on this page. They are saved on bin/targets/x86/64 inside the building folder.

Because x86 hardware doesn’t have profiles, we don’t need to use the PROFILE parameter. With PACKAGES parameter we set all packages we want to add to or remove from default list. The command make info lists default packages list. FILES parameter is used to add custom config and script files to be added to the image, it points to a folder which represents root folder when OpenWrt is running.

Источник

VirtualBox Advanced

Work in Progress!
This page is a continuous work in progress. You can edit this page to contribute information.

Overview

This guide extends the basic VirtualBox HowTo with broader setup recommendations, samples and common “gotcha-s”.

NOTE: Use a wired virtualbox host (unless you are really confident with virtualbox i.e. 80211 bridging issues ).

Prerequisite Concepts

x86_64 Basics

As the operating system within VirtualBox is basically an x86_64 host, having a general grasp of the hard drive partition setup, bootloader operation et. al. is beneficial. Particularly, when you need to undertake more advanced network interface setup within the VM and then translate that to VBox nics. In other words, lack of confidence performing bare metal config will compound troubleshooting if you are unable to clearly differentiate what is physical and what is virtual. In this case perhaps using an old pc or spare usb disk to test on real hardware first is a good first step.

squashfs vs ext4

Where is my router?

Using squashfs:

Squashfs images are neat when you are using the Imagebuilder to integrate all packages you want in a single re-settable image. You can install with sysupgrade, and not lose any of your “installed packages” as you have integrated them in the base firmware image.

Since you have Virtualbox anyway, why not have a Debian or Ubuntu VM and use the Imagebuilder too. It’s a very convenient way of tracking snapshot(master) to have the latest and greatest, and the only practical way to do so for most other devices supported by OpenWrt, so this is more or less the best “choice” for OpenWrt veterans that have deployed many devices and are using the imagebuilder already.
NB: With Imagebuilder, the size of the read-write partition is irrelevant as all packages are embedded in the squashfs read-only partition that is enlarged as needed, so 128MB is available for config only.

Using ext4:

This type of image mimics a more conventional Linux distro like Debian or Ubuntu, where you have packages and you keep updating or installing them as needed. But afaik this is a bit of a pain to do if you try to follow snapshot, as OpenWrt does not implement the ability to have multiple ( non-identical ) kernels with kernel modules (the Linux “device drivers”) installed at the same time, and select what kernel to boot when you reboot. Although it is possible to manually edit grub.cfg to support this manually using differing rootfs partitions for each kernel ( without sysupgrade support )

Therefore, using sysupgrade to flash a new combined-ext.bin will typically zap the “boot” and “rootfs” partitions, config is migratable, packages are not.

VirtualBox Networking Basics

Knowledge of the basic network types offered by VirtualBox will help you immensely…

Источник