Hi,
On 2017-06-19 08:52, yanosz wrote:
Hei folks,
I've some issues setting up a tagged vlan on a TP-Link 841n v9 router.
The vlan (tag 23) should spawn all ports (lan, wan) having a dedictated
interface.
For doing so in luci I add a new vlan, name it 23 and enable all
drop-down boxes (incl. cp
Hi,
I have been using the image builder in the past to generate custom
images with additional packages for my other TP-LINK routers, and that
works fine.
Now I would like to use an old Linksys WRT54GL as an access point and
would like to generate a custom image with a minimal set of packages
Hi Jo,
On 20/10/17 10:59, Jo-Philipp Wich wrote:
Hi Mikael,
try "make info", that should display the required package set per device.
Thanks for the info.
$ make info
[snip]
linksys-wrt54g:
Linksys WRT54G
Packages: kmod-b43 kmod-b43legacy
[snip]
So I did this:
$ make image PROFILE=
Hi,
I am playing around with an old PC Engines Alix board and I want to put
OpenWRT on it.
For the x86 platform I see that there are two options: ext4 and squashfs.
What is the recommended filesystem to use on a CF card in this case?
I am mostly interested in knowing if it has any performanc
On 2018-04-11 11:30, Felix Fietkau wrote:
On 2018-04-11 10:59, Mikael Bak wrote:
[snip]
What is the recommended filesystem to use on a CF card in this case?
[snip]
Both are fine, squashfs is recommended. No significant performance
penalty either way.
- Felix
Thanks Felix,
I will give
On 2018-04-11 14:11, Nishant Sharma wrote:
[snip]
I didn't know a way to expand squashfs, so decided to compile the image
and adjusted /root size as per the size of the disk.
I'm using the Image Builder to create custom images. I can't find any
option how to specify the size of the rootfs
Hi txt.file,
On 2018-04-11 14:48, txt.file wrote:
There is no need to create a bigger squashfs as squashfs is read-only.
With squashfs you get two file systems. squashfs for the files in the
image and jffs2 for changed/added files. During the first boot the jffs2
is created. It starts after the
On 2018-04-11 14:50, Tomasz Maciej Nowak wrote:
W dniu 11.04.2018 o 14:35, Mikael Bak pisze:
[snip]
I'm using the Image Builder to create custom images. I can't find any
option how to specify the size of the rootfs and/or the overlay.
Is it possible with Image Builder or must I
On 2018-04-11 16:09, Luiz Angelo Daros de Luca wrote:
You can also expand the overlay partition directly on img file or after the
installation.
First expand this physical partition. I like to do it with parted (script
friendly) but it is not available
as OpenWrt tool:
$ /usr/sbin/parted OpenWr
