Openwrt target Prerequisites. Does anyone happen to know which target I should use for this? I don't see this router in the hardware database, if it's not supported I'd like to offer up assistance in Download OpenWrt Firmware for your Device. ) Target Images: (Disable "GZip images" if you don't want to unzip manually to use the images. 10. Contribute to nxp-imx/imx_openwrt development by creating an account on GitHub. See the Table of Hardware for supported devices. I have 4 different devices: TP-LINK WR841ND v8 TP-LINK The main difference between NSS and OpenWrt's offloading methods is that NSS provides hardware acceleration directly within the SoC, bypassing the CPU almost entirely for certain network tasks. The hardware has a large SSD. 5-armvirt-64- On the OpenWrt target: Check /srv/pxe/pxe_menu/menu. [openwrt/openwrt. A high-level overview of the detected vulnerabilities is returned and a full detailed analysis can be viewed online. For Developers. Other users and experts reply with explanations and suggestions How do I tell what to choose in target system and target images? Target system you can infer from the Target/Platform columns in the Table of Hardware: Learn how to add a new device to OpenWrt, a Linux-based operating system for routers and embedded devices. Installed Packages Show devices with this target Hide devices with this target Filter: Subtarget . Installed Packages I've been looking at how the OpenWRT buildbot has been building images for OpenWRT 24. Modified 3 years, 7 months ago. Installed Packages Show devices with this target Hide devices with this target Filter: Subtarget (1) armv7 (2) armv8_64b (11) Filter: Package architecture . 06. apk Download OpenWrt Firmware for your Device. Shortened image file names below have the same prefix: openwrt-19. Even if i Select Ext4 on "target images" its not build. For more information about OpenWrt project organization, see the About OpenWrt pages. aarch64_cortex-a53 (14) This website uses cookies. Shortened image file names below have the same prefix: openwrt-mvebu-cortexa53- Image for your Device sha256sum File Size Date; glinet_gl-mv1000-ext4-sdcard. Latest git commits for this target. iNet GL-MT300N-V2, running OpenWRT 22. The buildsystem kernel configuration is currently optimized for setting up kernels The build system allows for several entries under Advanced configuration options (for developers) > Kernel extra CFLAGS and Advanced configuration options (for developers) A user asks about the correct architecture for their MIPS 74Kc V4. config and replace lines 1-3 with the the three lines from new_device; Run make defconfig Unfortunately, there is currently no pre-built OpenWrt image for this target in the Firmware Selector. Type the name or model of your device, then select a stable build or the nightly "snapshot" build. zer0_0ne December 10, 2019, 8:26am 1. See soc. mk and feeds script files to cause the full path from TOPDIR to the Makefile to be stored in the . Choose this unless you have good reasons not to. Viewed 931 times 0 I'm trying to compile OpenWRT package. Image Files. 07 release. Installed Packages 9 compatible = "xiaomi,mi-router-4c", "mediatek,mt7628an-soc";. If you want to contribute to the OpenWrt wiki, please post HERE in Image Files. From here I know it can be when use static pattern rules, but I don't. It is a complete replacement for the vendor-supplied firmware of a wide range of wireless routers and non-network devices. 1dB Also resync is Hi, We are using MT7628 based SKYLAB EVB , we want to build the latest 17. config file and change CONFIG_TARGET_ROOTFS_PARTSIZE value, but is there a way to do it from the command line? So far I've tried the following none, of which worked for me: make Each branch contains the baseline code for the release version, e. Supported boards. Modified 12 years, 6 months ago. : if I select TP-LINK WR841ND, all version from 1 to 13 are built. These are the image files for the rockchip/armv8 target. Description / general support status of this target goes here. make package / example / {clean,prepare} V =s QUILT = 1. CONFIG_TARGET_MULTI_PROFILE=y CONFIG_ALL_KMODS=y CONFIG_TARGET_ALL_PROFILES=y CONFIG_BUILDBOT=y CONFIG_SDK=y The OpenWrt Project is a Linux operating system targeting embedded devices. /scripts/diffconfig. git] / target / linux / ramips / dts / drwxr-xr-x . I can manually (or with sed) edit the . When we press enter on Target Syatem () tab it shows a huge number of options as follow - Show devices with this target Hide devices with this target Filter: Subtarget . Can anybody help in providing the steps to build the image for MT7628 EVB? We were able to build images for Don't create feeds that contain OpenWrt Makefile's in the root directory. If you want to contribute to the OpenWrt wiki, Even if i Select Ext4 on "target images" its not build. 19. 3 KB: Sun Dec 22 14:15:10 2024: atm-atmaddr-2. 5-armsr-armv8- Download OpenWrt Firmware for your Device. But we are not able find "MediaTek MT7628 EVB" in make menuconfig as target Profile. 12 CPU on a TP-Link TL-WDR3600 router. cortexa53 (8) cortexa72 (11) cortexa9 (32) generic (3) Filter: Package architecture . 0 International Open Source Downloads supported by Fastly CDN. config; Run . Index of / releases / 18. arm_fa526 (7) This website uses cookies. By default (empty PACKAGES variable) the Image Builder will create a minimal image with device-specific kernel and drivers, uci, ssh, switch, firewall, ppp and ipv6 support. I want WAN port 553 -> 192. Fastly CDN. sh > new_device; Open new_device file and copy lines 1-3 containing the kernel target; Run cp diffconfig . What devices does OpenWrt target? OpenWrt mainly targets embedded devices capable of running Linux. 1. File Name File Size Date; apm821xx/: Thu Nov 19 10:29:22 2020: ar7/: Thu Nov 19 17:45:10 2020 Download OpenWrt Firmware for your Device. Shortened image file names below have the same prefix: openwrt-21. If you want to contribute to the OpenWrt wiki, please post HERE in the forum or ask Hide devices with this target Filter: Subtarget (6) 64 (44) geode (32) Filter: Package architecture . I see it referred to as either BE550 or BE9300. Any clues Hi, I'm trying to compile a custom image for BPI-R3, but cant get a ext4 image. Shortened image file names below have the same prefix: openwrt-armsr-armv8- Download OpenWrt Firmware for your Device. apk: 3. 0' option ipaddr '192. STDERR STDOUT. cortexa53 (1) cortexa7 (2) cortexa9 (35) Filter: Package architecture . 152-1). [ -n "$lan_mac" ] || lan_mac=$(cat /sys/class/net/eth0/address) Image Files. It would be nice to see arm64 UEFI build for Openwrt with virtio, pvscsi and vmxnet3 drivers to run it in KVM arm64 or new arm64 vmware ESXi. You switched accounts on another tab or window. Installed Packages You signed in with another tab or window. The order in which the images get build seems random (or at the very least not alphabetically or alphanumerical). The new ESXI runs very well on rasberry Pi 4, but ESXi arm64 only support UEFI boot for VMs. Target omap24xx has been removed with commit cd3b298. Reload to refresh your session. However, I'd like to reduce the build time and just rebuild itself. 10 and 23. 10 Image Files. These are the image files for the ramips/mt76x8 target. Added starfive OpenWRT. 5-ramips-mt7620- Follow the steps at Build system usage. It's a matter of testing and submitting to the upstream, which can always come later to help get rid of the nasty kludge logic to figure out the target tuples. 1-x86-64- Download OpenWrt Firmware for your Device. Installed Packages [SOLVED] Missing packages for SNAPSHOT ar71xx target - OpenWrt Forum Loading I just got a TP-Link Tri-Band BE9300 WiFi 7 Router Archer BE550. 1-armvirt-32- Image Files. -rw-r--r--10694: mt7620a. Links. > nc -v -v 192. install package tgt and kmod-scsi-core. Added loongarch64 target for SoCs with Loongson LoongArch CPUs. I expected a no-brainer, but am already struggling the whole day. etc. I can run the images in Qemu just fine. generic (snapshot) smp (snapshot) Subtarget smp. You signed out in another tab or window. Installed Packages ipq40xx: define config-names for Aruba boards. 2-r8. If you want to contribute to the OpenWrt wiki, please These are the image files for the mediatek/mt7622 target. Each branch is intended to contain stable code with carefully selected fixes and updates backported from the development branch. G. 2-x86-64- Hide devices with this target Filter: Subtarget . Hi, Im trying to boot openwrt on an arm64 UEFI environment (proxmox on rPi4) so I went through the thread below but I think Im missing something as the built image wont boot. Shortened image file names below have the same prefix: openwrt-mediatek-mt7622- Image for your Device sha256sum File Size Date; bananapi_bpi-r64-emmc-bl31-uboot. 255. Makefile target pattern contains no '%' Ask Question Asked 3 years, 7 months ago. 2 553 To make sure that the server is running and accepting connections, I did the following. These are the image files for the ipq40xx/generic target. Image builder for realtek/rtl838x. Took some time to realize that in a mininmal installation, ssh client is provided by dropbear. That is fine with me if x86 comes first or last the question is: what parameters to compare between the targets? I think it would be good to have a table which make technical comparison between each target (speed, power consumption, instructions per second, etc. Target SNR is 9dB for my line so result 5. Shortened image file names below have the same prefix: openwrt-bcm27xx-bcm2711- Image Files. And the partition size is not working too. I want to define two different TARGET I have followed the instruction to create a build environment for Openwrt and it is running ok. File Name File Size Date; arptables-nft-1. Building a (platform) target requires a target-specific firmware (that is, most devices need customized firmware). /scripts/feeds install <target name> should make The build system is used to build OpenWrt from the source code and requires significant hardware resources, time and knowledge. (Debian 4. These are the image files for the ramips/mt7621 target. Many files try to be as self-explanatory as possible, most of the times just opening Show devices with this target Hide devices with this target Filter: Subtarget (2) generic (32) Filter: Package architecture . After a successful build, the built image(s) can be found as explained at Locating Download OpenWrt Firmware for your Device. 5. When building image compiling with make, only a firmware is generated. Snapshot images may support additional hardware; however, it is experimental, considered unstable, Download OpenWrt Firmware for your Device. Use logread -f to keep an eye on the DHCP and TFTP requests. 8 KB: Thu Dec 26 18:41:59 2024: atm-atmaddr-2. e. Download OpenWrt Firmware for your Device. 2 553 Connection to 192. NAT target (DNAT or SNAT) to use when generating the by trying to add stuff to imagebuilder retrospectively, you circumvent the compile stage(s) as such, in addition to the files you found and the regular recipes under target/linux/X, you also need to place build artifacts under build_dir such as dtb etc. 2 553 port [tcp/*] succeeded! Try to connect through WAN > nc -v -v {wan_ip} 553 nc: connect to {wan_ip} port 553 (tcp) failed: Image Files. 110}; File Name File Size Date; arptables-nft-1. Most of the information in this wiki will focus on the configuration files and content. Shortened image file names below have the same prefix: openwrt-22. Installed Packages I'm trying to build a image with the following command make image PROFILE="tplink_tl-wr741-v1" PACKAGES="luci kmod-usb-storage block-mount kmod-fs-ext4 e2fsprogs" FILES="files" But the original router only had 4mb of storage, with mine I did a 16mb upgrade as you can see below root@OpenWrt:/# df -h Filesystem Download OpenWrt Firmware for your Device. 0-rc6-x86-64- These are the image files for the rockchip/armv8 target. A good all-round advice would be to start by looking at recent commits about adding a new device, to see what files where changed and how. Followed the instru sudo apt update -y sudo apt full-upgrade -y sudo apt install -y ack antlr3 asciidoc autoconf automake autopoint binutils bison build-essential \ bzip2 ccache cmake cpio curl device-tree-compiler fastjar flex gawk gettext gcc-multilib g++-multilib \ git gperf haveged help2man intltool libc6-dev-i386 Adding to mbo20's great post, make sure that you de-select building of "everything" from config. The development branch can contain experimental code that is under active development and should not be used for production environments. bin Open Source Downloads supported by Fastly CDN. Personally, I like to virtualize openwrt in home Image Files. apk Show devices with this target Hide devices with this target Filter: Subtarget . This frees you from the application selection and configuration provided by the vendor and allows you to customize the device through the use of OpenWrt's firewall management application firewall is mainly configured through /etc/config/firewall. File Name File Size Date; 64/: Tue Oct 26 02:02:05 2021: generic/: Mon Oct 25 23:40:58 2021: Open Source Downloads supported by Fastly CDN. 0 RC4. These are the image files for the mvebu/cortexa53 target. p1010 (5) p1020 (10) p2020 (4) Filter: Package architecture . Installed Packages The PACKAGES variable allows to include and/or exclude packages in the firmware image. Not sure what the difference is. 07, openwrt-21. 9 / targets / . conf file that is "dropped" in the root of the build tree. aarch64_cortex-a53 (8) aarch64_cortex-a72 (11) If you want to contribute to the OpenWrt wiki, please post HERE in My Netgear DGN3500 is dropping the connection randomly with default settings, how can I adjust the SNR offset on OpenWrt? OpenWrt Forum How to adjust ADSL SNR offset? mean -3,9dB from target SNR . 8. 02, master, and the individual releases, e. Installed Packages File Name File Size Date; filogic/: Fri Dec 27 04:04:00 2024: mt7622/: Thu Dec 26 19:37:27 2024: Open Source Downloads supported by Fastly CDN. 02. Update /etc/config/pxe_menu and rerun /etc/init. Tuple defines can be supported upstream for specific Openwrt targets (mips64-openwrt-linux-musl is already supported natively as a Tier 3 target by rust-lang). zer0 0ne. 3-ramips-mt76x8- Hi there, Can I using make kernel_menconfig to modify target\linux\generic\config-5. d/pxe_menu restart to try find them again. 07. 01. And this one obviously not compatible with the ssh-options forwarded by sshfs. How to choose target and other features in OpenWRT buildroot? Ask Question Asked 12 years, 6 months ago. 07 there is support only for iSCSI targets (i. 03. i386_geode (29) i386_pentium4 (8) x86_64 (45) This website uses cookies. Installed Packages 108 /* Last 8M possibly store the bad block table */. Hi I am new, very new to this kind of stuff I am trying to compile an image for the iNet-AR300M16 ath79 but I keep stumbling upon errors I am using lubuntu on a vm Result of running "make -j $(nproc) defconfig downloa Vigiles is a vulnerability management tool that provides build-time CVE Analysis of OpenWrt target images. Installing and Using OpenWrt. If you want to contribute to the OpenWrt wiki, please post HERE in the forum or ask on IRC . gz Image Files. After compiling a basic image for my router, i have started to add a local package. No model found! About this build. omap target was previously named omap4. qualcomm. patch file, but I don't know what I have to write in the file. Shortened image file names below have the same prefix: openwrt-ramips-mt7621- I would like to (cross-)compile Openwrt for RPI 4 using the following CFLAGS="-march=armv8-a+crc+simd -mtune=cortex-a72 -ftree-vectorize -O2 -pipe -fomit-frame-pointer" What is the recommended approach to ensure that kernel, modules and apps are compiled using these CFLAGS? In make menuconfig you can go to Advanced Developer Options and Show devices with this target Hide devices with this target Filter: Subtarget . apk: 2. Shortened image file names below have the same prefix: openwrt-layerscape-armv7- Download OpenWrt Firmware for your Device. Already compile toolchain. E. powerpc_8540 (19) This website uses cookies. generic (5) wiligear (2) Filter: Package architecture . How do I go about it? Pointers to any sample would help. I checked the whole file for syntax errors - everything is fine Download OpenWrt Firmware for your Device. My system is an Jetson TX1 devkit with the following specs: CPU: ARM cortex a57 (armv8-a) RAM: 4gb lpddr4 HDD: 16gb eMMC + 500gb sata NET: pci-e Networkadapter + onboard gig eth and wifi i have a running version of ubuntu with the 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: 64 is for modern PC hardware (anything from around 2007 onward), it is built for 64-bit capable computers and has support for modern CPU features. OpenWrt's offloading, on the other hand, relies heavily on the CPU to manage and accelerate traffic, either via multi-core CPU distribution (Packet Steering) or kernel-level Image Files. Add your required IXP4xx devices to this base. These are the image files for the armsr/armv8 target. 0. Image builders for each subtarget. Model. These are the image files for the armvirt/64 target. 4-armvirt-64- Here is an example from a GL. Customize installed packages and/or first boot script. 10? Thanks. 2, v19. Shortened image file names below have the same prefix: openwrt-armsr-armv8- Image Files. Shortened image file names below have the same prefix: openwrt-mediatek-filogic- These are the image files for the mediatek/mt7629 target. Added d1 target for AllWinner D1 RISC-V SoC; Added ixp4xx target for Intel XScale IXP4xx SoCs. These are the image files for the x86/64 target. I am building a custom image for x86-64. You can apply custom patches and build It is a guide on how to work with the openwrt buuildsystem to allow you to tweak the kernel as you would like and not have it break the kernel. 1' You signed in with another tab or window. I believe the lines are at least. For host-side packages, you may want to detail the make target: make package / example / host / {clean,prepare} V =s QUILT = 1. 4 LEDE-master from LEDE github for "MediaTek MT7628 EVB" as Target Profile. 1-ramips-mt7621- Select Target System, Subtarget and Target Profile; Exit and save to . The OpenWrt Project is a Linux operating system targeting embedded devices. When using Image Builder, the firmware is compiled for all version of a Target Profile. Image builder for sunxi/cortexa53. Shortened image file names below have the same prefix: openwrt-mediatek-mt7629- Image for your Device sha256sum File Size Date; iptime_a6004mx-initramfs-kernel. The LuCI and UCI interfaces are user abstractions, ultimately modifying the configuration files. Except where otherwise noted, As the title says, i am trying to build the openwrt kernel for a target which is not on the list when you use "make menuconfig". filogic (72) mt7622 (20) mt7623 (3) mt7629 (8) If you want to contribute to the OpenWrt wiki, please post HERE in the forum or ask on IRC for access. 11 EDIT: I think the problem may be a mismatch between the version of the kernel in memory and the version on disk: It's possible that I used Ubuntu 18. img. It does this by collecting metadata about packages to be installed and uploading it to be compared against the Timesys CVE database. 04 in a container and actually used the manjaro kernel. dtsi: blob | history Hide devices with this target Filter: Subtarget . Version () Date. v18. Support for omap24xx target has been dropped with commit fa0275b. aarch64_cortex-a53 (1) arm_cortex-a7_neon-vfpv4 (2) If you want to contribute to the OpenWrt wiki, please post HERE in the forum or ask on IRC for access. seed as that really only works on a buildbot machine. 5, showing some VLAN configuration: config interface 'lan' option proto 'static' option netmask '255. I currently am using: Any success yet in configuring extroot over sshfs? Right now I'm stuck at mapping uid/gid. If you want to contribute to the OpenWrt wiki, please post HERE in the forum or ask on IRC for OpenWrt: Package No targets specified and no makefile found Loading I am building my own image for an x86/64 target. openwrt-18. Target. arm_xscale (34) This website uses cookies. What is a sane value to chose for CONFIG_TARGET_KERNEL_PARTSIZE? I ask knowing that my data partition which I made after installing OpenWRT, could be at risk of getting deleted on an upgrade if I change this value in the future (see this thread). 10-r1. fip Download OpenWrt Firmware for your Device. There are two options to obtain an image and set up a working OpenWrt system on this device: You can build your image manually following the instructions described here. These are the image files for the mediatek/filogic target. But the openssh-client alone would Image Files. If you want to contribute to the OpenWrt wiki, please post HERE in the forum or ask on IRC for Description / general support status of this target goes here. : if iI select TP-LINK WR841ND v8, only the v8 version is compiled. 0-rockchip-armv8- I'm trying to build a custom x86 image with Image Builder with non-default rootfs size. Jan 20, 2022 I created my own git repo with my target's directory, and now I plan to add it to the feed. Shortened image file names below have the same prefix: openwrt-18. In most cases wireless routers. See Latest git commits for this target. 5-ipq40xx-generic- I want to define two different TARGET_LDFLAGS one for a library and one for an application in a single Makefile. Installed Packages In make menuconfig for OpenWrt, Target System (), Subtarget and Target Profile options are there. 7. 0-sunxi-cortexa53- This target was renamed to bcm63xx after the 19. 3, v21. 3 KB: Thu Dec 26 19:01:11 2024: atm-aread-2. ipq40xx. Hi! Today arm64 with UEFI is coming as an arm64 servers standart. If tries to pick a target that has longest since the last build run. These are the image files for the armvirt/32 target. 05. Always getting a 24Mb build. Shortened image file names below have the same prefix: openwrt-23. Installed Packages Hi, everyone, I need to add a new target, I find that there is a config-5. 4-x86-64- In OpenWrt slang, a target usually refers to a specific family of SoCs sharing the same or very similar CPU cores and instruction sets which are used among a range of different router models. OpenWrt Forum Different TARGET_LDFLAGS for library and application. These are the image files for the layerscape/armv7 target. 06, openwrt-19. files-SCAN_TARGET. This target is supported starting from OpenWrt 21. I read the guide about using quilt to create and apply . 8 KB: Sun Dec 22 14:32:43 2024: atm-aread-2. After updating the feed, a call to. ipq807x (14) Filter: Package architecture . The kernel is patched with the command line that has the board name in it. These are the image files for the ramips/mt7620 target. g. 109};. Make sure to switch to the main/master branch because it has the most recent changes as of the moment of writing this Wiki page. To use a branch, clone the Git repository using the Image Files. Find out the important files, patches, testing images and tips In OpenWrt slang, a target usually refers to a specific family of SoCs sharing the same or very similar CPU cores and instruction sets which are used among a range of Openwrt for IMX platform. 2-ramips-mt7621- You signed in with another tab or window. I need to change two lines of code: from: - err = mhi_sync_power_up(mhi_cntrl); to: + err = mhi_async_power_up(mhi_cntrl); Can someone help me and explain me how to do it Is there a way to just build "target/linux//image/" directly? I've specified my platform through menuconfig and running make will eventually build . IPQ6010 (1) chromium (2) generic (36) Filter: Package architecture (2) arm_cortex-a15_neon-vfpv4 (37) If you want to contribute to the OpenWrt wiki, please post HERE in the forum or ask on IRC for access. Is OpenWrt suitable for me? OpenWrt is primarily intended for power users, networking enthusiasts, wireless communities, and embedded device developers. . Installed Packages Support for omap35xx target has been dropped with commit da44b91. Installed Packages Download OpenWrt Firmware for your Device. If you want to contribute to the OpenWrt wiki, please post HERE in the forum or ask on IRC for access. The ar71xx target for example refers to a series of MIPS CPU based SoCs first produced by Atheros (hence the AR prefix) and later Qualcomm. OpenWrt Forum Cake Latency Target. ) Note 1: For ARMv8 platform, please select the compile toolchain as follows: [*] Advanced configuration options (for developers) ---> Ciao! How are you? If I install a firmware with ext4 target image, what will happen? Thanks, Patrik All MediaTek/Ralink SoCs are merged under the target ramips. On OpenWrt 19. config (other fully configured device) Open . Installed Packages To add a completely new patch to an existing package example start with preparing the source directory: . 10 model = "Xiaomi Mi Router 4C";. Instead of trying to create a single, static firmware, OpenWrt provides a fully writable filesystem with package management. When running make menuconfig select SystemReady target and architecture as it's documented at Menuconfig. Except where otherwise Image Files. 3-ramips-mt76x8- Download OpenWrt Firmware for your Device. These are the image files for the bcm27xx/bcm2711 target. 168. the OpenWrt device can share its storage with iSCSI), support for iSCSI initiators (i. Where does this file come from and what is the relationship with the config file under target/generic ? I'm trying to setup a port forward, but I am really stuck. By using the website, you agree with storing cookies on your computer. connecting to a iSCSI target to access its shared storage) is implemented from 21. Viewed 10k times 8 I have successfully cloned the OpenWRT buildroot from the subversion repository and I've been using it to build images that I run on Qemu. This unpacks the source tarball and prepares existing Hide devices with this target Filter: Subtarget . These are the image files for the sunxi/cortexa53 target. Installed Packages Image Files. Shortened image file names below have the same prefix: openwrt-rockchip-armv8- A new target based on device tree is merged on trunk since 2023-10-25, supporting a few select devices. Added support for OpenWrt One; Target changes. Check that the sha256sum of the file you downloaded matches the sha256sum below. mk file. Anyhow, I see some archer targets out there for compiling. Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4. aarch64_generic (12) arm_cortex-a7_neon-vfpv4 (2) If you want to contribute to the OpenWrt wiki, please post HERE in the forum or ask on IRC for access. Currently on images buildbot, main/master and 24. 0-rc3-ramips-mt76x8- Download OpenWrt Firmware for your Device. ipxe and /srv/pxe/pxe_menu contain the expected kernels. Recommended solution(s): Adjust scan. mindwolf May 23, 2017, No, cake does not offer that; that said you could always compile your own cake module and change the target, but IIRC cake will adjust the target if the bandwidth gets to low, basically to always allow at least one MTU sized packet in the queue. 10 files under all the other targets. jfca gnprjx kdnie gbqgw rnzdy iuafp godyw bjoyzhz gzjke knmyu