Re: [LEDE-DEV] tagged vlans on a TP-Link 841n v9
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. cpu) as checked. After applying, the system becomes unreachable (v4, v6) on any interface. What's wrong here? How can I enable the vlan? On my 841n (v10) the WAN port is not part of the switch and thus cannot be used as a trunk port. Perhaps this is true for v9 too. You should however be able to configure one of the LAN ports to act as WAN and carry VLAN23. In this case the real WAN port is useless. The TP-Link 1043nd (at least v1) has the ability to do what to want since the WAN port on that device is part of the switch. HTH, Mikael ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
[LEDE-DEV] Linksys WRT54GL / image builder
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 (without luci and some other stuff). My question is: How can I know what packages I must include when building the image with the image builder in order to get the device to boot and be able to login via ssh? Something like this: $ make image PROFILE=linksys-wrt54g PACKAGES="[what should be here?]" Thanks for all the hard work with lede/openwrt! TIA, Mikael ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] Linksys WRT54GL / image builder
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=linksys-wrt54g PACKAGES="kmod-b43 kmod-b43legacy" And it got me a quite small, basic image without luci that fit on my device. FYI: the image I can download from today's snapshot is too big to fit on these devices (3.7MB). The image I built is only 3.5MB. So I'm asking how is the package list determined for a device when the snapshots are built? Is there a make command in the image builder I can run to see what the default packages are for a given device? Thanks again, Mikael For reference here's the complete package list I got after building my own image with the above command (Image builder for LEDE 17.01.4): b43legacy-firmware - 3.130.20.0-1 base-files - 173.1-r3560-79f57e422d busybox - 1.25.1-4 dnsmasq - 2.78-1 dropbear - 2017.75-2 firewall - 2017-05-27-a4d98aea-1 fstools - 2017-06-30-bdcb075f-1 fwtool - 1 hostapd-common - 2016-12-19-ad02e79d-6 ip6tables - 1.4.21-2 iptables - 1.4.21-2 iw - 4.9-1 jshn - 2017-02-24-96305a3c-1 jsonfilter - 2016-07-02-dea067ad-1 kernel - 4.4.92-1-f748c7658ebe780bcfe532cde71ec481 kmod-b43 - 4.4.92+2017-01-31-3 kmod-b43legacy - 4.4.92+2017-01-31-3 kmod-cfg80211 - 4.4.92+2017-01-31-3 kmod-gpio-button-hotplug - 4.4.92-2 kmod-ip6tables - 4.4.92-1 kmod-ipt-conntrack - 4.4.92-1 kmod-ipt-core - 4.4.92-1 kmod-ipt-nat - 4.4.92-1 kmod-leds-gpio - 4.4.92-1 kmod-ledtrig-default-on - 4.4.92-1 kmod-ledtrig-netdev - 4.4.92-1 kmod-ledtrig-timer - 4.4.92-1 kmod-lib-crc-ccitt - 4.4.92-1 kmod-mac80211 - 4.4.92+2017-01-31-3 kmod-nf-conntrack - 4.4.92-1 kmod-nf-conntrack6 - 4.4.92-1 kmod-nf-ipt - 4.4.92-1 kmod-nf-ipt6 - 4.4.92-1 kmod-nf-nat - 4.4.92-1 kmod-ppp - 4.4.92-1 kmod-pppoe - 4.4.92-1 kmod-pppox - 4.4.92-1 kmod-slhc - 4.4.92-1 lede-keyring - 2017-01-20-a50b7529-1 libblobmsg-json - 2017-02-24-96305a3c-1 libc - 1.1.16-1 libgcc - 5.4.0-1 libip4tc - 1.4.21-2 libip6tc - 1.4.21-2 libjson-c - 0.12.1-1 libjson-script - 2017-02-24-96305a3c-1 libnl-tiny - 0.1-5 libpthread - 1.1.16-1 libubox - 2017-02-24-96305a3c-1 libubus - 2017-02-18-34c6e818-1 libuci - 2016-07-04-e1bf4356-1 libuclient - 2017-09-06-24d6eded-1 libxtables - 1.4.21-2 logd - 2017-03-10-16f7e161-1 mtd - 21 netifd - 2017-01-25-650758b1-1 nvram - 10 odhcp6c - 2017-01-30-c13b6a05-2 odhcpd - 2017-10-02-c6f3d5d4-2 opkg - 2017-03-23-1d0263bb-1 otrx - 1 ppp - 2.4.7-11 ppp-mod-pppoe - 2.4.7-11 procd - 2017-08-08-66be6a23-1 swconfig - 11 ubox - 2017-03-10-16f7e161-1 ubus - 2017-02-18-34c6e818-1 ubusd - 2017-02-18-34c6e818-1 uci - 2016-07-04-e1bf4356-1 uclient-fetch - 2017-09-06-24d6eded-1 usign - 2015-07-04-ef641914-1 wpad-mini - 2016-12-19-ad02e79d-6 ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
[LEDE-DEV] Advice on filesystem for x86 (CF card)
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 performance penalty in chosing the wrong one. I am also curious to know if either of these filesystems is going to destroy my CF card faster than the other. TIA, Mikael ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] Advice on filesystem for x86 (CF card)
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 squashfs a shot then. Do I have to expand the fs after flashing in order to make use of my 1GB CF card. On ext4 I have to expand the partition after flashing. TIA, Mikael ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] Advice on filesystem for x86 (CF card)
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 and/or the overlay. Is it possible with Image Builder or must I build the whole thing from source? TIA, Mikael ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] Advice on filesystem for x86 (CF card)
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 end of the squashfs until the end of device. The good point is that you have some failsafe mode where you ignore the jffs2 and only load the squashfs. Then your device has the same behavior as directly after flashing. With ext4 you get a single read-write file system (which makes failsafe difficult). This is how ar71xx works and I expect x86 does the same. If I am wrong correct me, please. kind regards txt.file Yeah, I know it's useless to expand the squashfs part. What I really want is to expand the overlay part so it can use the entire remaining space on my CF card. Thanks, Mikael ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] Advice on filesystem for x86 (CF card)
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 build the whole thing from source? Should be possible by editing CONFIG_TARGET_ROOTFS_PARTSIZE in .config. Thanks a lot! I changed this value to 512 and rebuilt the image. Now I can see that /overlay has about 500MB free space, and LuCi tells me the same in System->Software. Thanks again. This was exactly what I was looking for! Cheers, Mikael ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] Advice on filesystem for x86 (CF card)
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 OpenWrt...combined.img resizepart 2 100% Nice! That worked. Partition resized. GParted did not let me do that. Now resizing the filesystem depends on which fs you use. If you are using f2fs (LEDE and OpenWrt snapshot), you can expand using a mounted filesystem. You just need to remount overlay as ro. It might be a bug but when I did in a rw mounted fs, it exploded my filesystem. # mount -o remount,ro /overlay # resize.f2fs /dev/loop0 # from f2fs-tools # reboot As a matter of fact I did not have to do the resize.f2fs. Perhaps because my image contained the f2fs-tools package the fs was automatically resized on first boot (just speculating). Now I have 932MB on /overlay and I'm happy :) Thanks a lot for the help. Cheers, Mikael ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
