Welcome Guest ( Log In | Register )

Outline · [ Standard ] · Linear+

 Xiaomi Router Mini with full Unifi support, turn into a beast with custom asus rom!

views
     
FameWolf
post Jun 25 2016, 01:29 PM

New Member
*
Junior Member
26 posts

Joined: Jun 2016


Hello folks.

Got the latest version of padavan on my router.....got it swapped out for my old one...have a 8 port gigabit switch hooked up to it...wired connections are working fine and getting net as they should but for whatever reason both the 2.4 and 5ghz clients are showing "no internet" after successfully connection. I've looked but I don't see anything I think I need to set...I'd think the wifi connections would auto bridge to the lan unless you told them different?


*update*

Got things squared away. Had a bad default gateway.

This post has been edited by FameWolf: Jun 25 2016, 02:36 PM
FameWolf
post Jun 26 2016, 09:02 PM

New Member
*
Junior Member
26 posts

Joined: Jun 2016


QUOTE(trix @ Jun 26 2016, 05:44 AM)
yup, working fine. hypptv, ipv6 also works, just like mi mini + padavan
*
Did you also install breed bootloader?

Notice any major improvements over the Xiomi Mi mini?

Youtube reviews seem to indicate more flash and 4 antennas but folks didn't notice a big difference in coverage area although it might handle more simultaneous users at once.

Primary Rom is chinese only or at least it was on May 26th when reviewed so Padavan in english would be a good step up...of course you lose the mi wifi app (which IS in english..go figure).

This post has been edited by FameWolf: Jun 27 2016, 04:38 AM
FameWolf
post Jun 27 2016, 02:18 PM

New Member
*
Junior Member
26 posts

Joined: Jun 2016


QUOTE(trix @ May 28 2016, 04:05 AM)
[url=[/url]
compiled from commit d1ac127 if anyone interested
also contains sample config and board profile for this router

MI-MINI board profile folder and content goes here: rt-n56u/trunk/configs/boards/
inside MI-MINI folder, create symlink to libc.config : ln -s ../uclibc-mipsel.config ./libc.config
*
Do you enable smb client in your builds so the router can mount local network storage?
FameWolf
post Jun 27 2016, 11:50 PM

New Member
*
Junior Member
26 posts

Joined: Jun 2016


QUOTE(trix @ Jun 27 2016, 09:21 AM)
not using breed bootloader, prometheus installed u-boot instead
i'm using mi-mini and mi-3 at 2 different houses, so can't compare them side by side.
but mi-3 replaces tp-link tl-wr1043nd v1, and coverage is much better for 2.4GHz network.
i don't really use the available flash space for anything else, so no comment on that part
previous build, nope
latest (cc58fc3), yes
i've removed QoS since its unsupported and can't be configured from webgui
config file used to build the firmware is also there on my google drive for reference
*
I guess I'm going to have to get familiar with prometheus assuming you used that also for the MI-3 to build padavan unless you are releasing the version for that also? I ordered one but will take about a month to get to me.

I've read posts that say the MI-3 both does and does not come with an english rom installed. Which was it for you originally?

As for qos...since the user has to disable hardware nat for it to work why not implement the folder with the needed scripts but default them to not run (leave out the lines that actually execute the qos on startup)...then the user has the option for either.

Personally I don't need qos so badly I'm giving up hardware nat...I do wish I could prioritize my obihai obi200 voip traffic...I can isolate it to a specific mac or ip address which is static...even isolate it to a specific PORT on the router if I use some of the op's instructions but still don't see a way to prioritize it.

This post has been edited by FameWolf: Jun 27 2016, 11:51 PM
FameWolf
post Jun 29 2016, 06:54 AM

New Member
*
Junior Member
26 posts

Joined: Jun 2016


QUOTE(trix @ Jun 27 2016, 09:21 AM)
[url=[/url]
in russian, but should be understandable to follow
let me know if you need clarification on any part
basically:
1. install developer firmware so ssh can be enabled
2. setup VM for linux (if you already have linux machine, then use that instead. and doesn't have to be vmware workstation, can use others instead like virtualbox)
3. download and run prometheus
4. gain ssh access on router (if this doesn't work, use the steps i gave previously)
5. prometheus to pull source from padavan
6. build toolchain (only needed once, unless there's any update on toolchain source code)
7. configure and build firmware
8. flash firmware
not using breed bootloader, prometheus installed u-boot instead
i'm using mi-mini and mi-3 at 2 different houses, so can't compare them side by side.
but mi-3 replaces tp-link tl-wr1043nd v1, and coverage is much better for 2.4GHz network.
i don't really use the available flash space for anything else, so no comment on that part
previous build, nope
latest (cc58fc3), yes
i've removed QoS since its unsupported and can't be configured from webgui
config file used to build the firmware is also there on my google drive for reference
*
I am on your most recent build. (cc58fc3) (Thanks for making these available!)! I am attempting to use owncloud and lighttpd via entware-ng however it keeps telling me "Note: "smbclient" is not installed. Mounting of SMB / CIFS, SMB / CIFS using OC login is not possible. Please ask your system administrator to install it." under the section to mount external storage. I'm trying to mount some smb shares from my freenas server. Any idea what I need to do to make owncloud recognize it? Running the command via ssh still shows "-sh: smbclient: not found"

I verified that the config has:

### Include CIFS (SMB) client. ~0.2MB
CONFIG_FIRMWARE_INCLUDE_CIFS=y

*update* Solved. I did a search for smb and cifs....and so of course the entware package was called "samba36-client"

This post has been edited by FameWolf: Jun 29 2016, 07:09 AM
FameWolf
post Jul 4 2016, 03:44 PM

New Member
*
Junior Member
26 posts

Joined: Jun 2016


QUOTE(trix @ Jul 3 2016, 09:13 AM)
once prometheus started, press C, then y to delete prometheus config
when it restarts, you'll be able to select a different router
*
Where exactly do we put your config within the path of the prometheus folder? Do we need the Mi-Mini folder? I'm trying to build the MI-3 firmware as a test. If there is a walkthough somewhere even if I have to translate it I'd be appreciative.
FameWolf
post Jul 4 2016, 09:16 PM

New Member
*
Junior Member
26 posts

Joined: Jun 2016


QUOTE(trix @ Jul 4 2016, 04:39 AM)
my config is for mi-mini, not mi-3
for mi-3, if you're using prometheus, no need to use anything from my google drive
dl everything through prometheus
there is a youtube video i posted previously on how to use prometheus to install padavan on mi-3. its in russian, but easy enough to follow without understanding what was being said
*
I'm building both mi-mini and mi-3 so I'd still like to know where I put the file named "config" as I have config.sh and some others in the configs dir but none that just say "config". I think I found my problem with prometheus...I couldn't even get the toolchain compiled because I was working from NAS storage....had to pull the source to a local hd (I use linux mint all the time so no VM).

Thanks for your patience and assistance!




*update* Ok after the toolchain finally built (it was a permissions issue with the nas) I was able to see where to put your config. Is the skin used in your builds the default one?

"Patch for the sources IS NOT VALID, building can lead to errors! " <-- is this an error you see when building the firmware?


I guess ironically enough it runs better on linux IN windows than just on linux.

-------------
MediaTek MT7620/MT7602E/7612E 802.11 AP driver (MT76X2_AP) [M/n/y] m
LED support (MT76X2_AP_LED) [N/y] n
Soft LED support (MT76X2_AP_LED_SOFT) [N/y] n
LLTD (Link Layer Topology Discovery Protocol) (MT76X2_AP_LLTD) [Y/n] y
WDS support (MT76X2_AP_WDS) [Y/n] y
MBSSID support (MT76X2_AP_MBSS) [Y/n] y
New MBSSID mode support (MT76X2_AP_MBSS_NEW_MBSSID_MODE) [Y/n] y
AP-Client support (MT76X2_AP_APCLI) [Y/n] y
AP-Client TGn Cert support (MT76X2_AP_APCLI_CERT) [N/y] n
AP-Client Auto Bandwidth Support (MT76X2_AP_APCLI_AUTO_BW) [N/y] (NEW) aborted!

Console input/output is redirected. Run 'make oldconfig' to update configuration.

make[3]: *** [silentoldconfig] Error 1
make[2]: *** [silentoldconfig] Error 2
make[1]: *** No rule to make target `include/config/auto.conf', needed by `include/config/kernel.release'. Stop.
make[1]: Leaving directory `/home/famewolf/xmwork/rt-n56u/trunk/linux-3.4.x'
make: *** [linux] Error 1
/-------------------------------------------------------------------------------/
AP-Client Auto Bandwidth Support (MT76X2_AP_APCLI_AUTO_BW) [N/y] (NEW) aborted!
make[3]: *** [silentoldconfig] Error 1
make[2]: *** [silentoldconfig] Error 2
make[1]: *** No rule to make target `include/config/auto.conf', needed by `include/config/kernel.release'. Stop.
make: *** [dep] Error 2
make: *** [linux] Error 1
/-------------------------------------------------------------------------------/
Firmware: ERROR
An error occured during the compilation process!
Please copy the logs and then ask questions on 4pda!
Press any key to continue...


This post has been edited by FameWolf: Jul 4 2016, 10:35 PM
FameWolf
post Jul 13 2016, 02:57 AM

New Member
*
Junior Member
26 posts

Joined: Jun 2016


Is anyone willing to share their compiled mi-3 build?


If I understand right we'd have to write to 2 partitions using dd?

This post has been edited by FameWolf: Jul 13 2016, 08:58 PM
FameWolf
post Jul 28 2016, 02:22 PM

New Member
*
Junior Member
26 posts

Joined: Jun 2016


Got Padavan installed onto my MI-3 and finally was able to compile directly on my linux machine. I'll have to upgrade my Xiaomi Mi before I swap them out.

My question is this. Can I backup the "settings" on the Xiaomi Mi wifi in padavan and then restore them in padavan on the Xiaomi Mi wifi 3? I'd like to save haveing to redo alot of the config.



*note*

English speakers may want to review the steps/install here: https://wiki.openwrt.org/toh/xiaomi/mini and use it roughly for the Mi-3. You still have to download the developer version..you still have to REGISTER the router with Xiaomi via the android or iphone app..all this in preparation to download the patch which enables SSH on the router. The instructions on installing the ssh bin are rough...when they say hold the reset till you see the yellow light blink MULTIPLE TIMES thats just what it means...hold it..keep holding it...when you see multiple blinks (not just 1 blink which it does earlier) then you can let go and it will flash the ssh bin file from the usb drive.

All that gets your router ready to accept firmware from the script. On it you still have to update everything..build a toolchain (one time) then build the firmware and finally flash it. Make sure you back up your partitions.

Hope that helps someone cause it took me a LONG time to get everything squared away while trying to follow a video with the person speaking russian.

This post has been edited by FameWolf: Jul 28 2016, 02:29 PM
FameWolf
post Jul 29 2016, 04:43 AM

New Member
*
Junior Member
26 posts

Joined: Jun 2016


QUOTE(irwan6179 @ Jul 13 2016, 02:40 AM)
mine is having problem with using transmission and samba share. So I don't think it's suitable for sharing(plus I don't know how to get the file, linux noob here). If anyone has I'd also like to try them.

Thanks
*
FYI the .trx file is stored in a subdir from the dir that has the start.sh script. startshdir/trx_archive/creationdatetime

I have found out it's dangerous to just use the .trx.

"The firmware file must be divided into several parts before flashing. It is dangerous to do it yourself."


If no one can confirm it's safe to share the settings between the mi and the mi-3 (backup and restore) I suppose I'll have to do them manually. sad.gif

The following script (ran from the router) will create a file that contains the full config for the router in text file format with nvram set commands that can be edited so it is suitable to flash to a new router. The normal binary backup is very dangerous because it will try to assign hardware addresses and other things so you'd want to delete anything except the section you wanted such as the ip ranges, static ip addresses etc....

#!/bin/bash

nvram showall > nvram_settings.txt
rm nvram_settings.tmp
cat nvram_settings.txt | while read i;
do
o=${i%}
echo "nvram set " ${o} >> nvram_settings.tmp
done

sort nvram_settings.tmp > my_settings.txt


This post has been edited by FameWolf: Jul 29 2016, 11:24 PM
FameWolf
post Aug 3 2016, 01:52 AM

New Member
*
Junior Member
26 posts

Joined: Jun 2016


QUOTE(lala_cai @ Aug 2 2016, 12:41 PM)
FrameWolf,

By any chance you have the old developer firmware?
It seems that the newer developer firmware is no longer SSH accessible
*
For which router? The MI-3 required me to jump through some hoops to get ssh access. You have to install the current developer version (which does not have ssh) then you have to pair your router to a xiaomi account via the android app. Finally you have to download a ssh patchfile and save it to a flashdrive then hold down reset when plugging in power to router and continue to hold down until the router blinks the yellow light multiple times (not just once...it does that early and if you continue holding then it finally blinks a couple of times).

I don't think providing you MY downloaded patchfile would work since it's tied to my router.


Instruction originally from:

https://wiki.openwrt.org/toh/xiaomi/mini



This post has been edited by FameWolf: Aug 3 2016, 01:54 AM
FameWolf
post Aug 3 2016, 12:03 PM

New Member
*
Junior Member
26 posts

Joined: Jun 2016


Anyone having a problem with the prometheus script? I can't get it to go beyond commit eaebfec even though several new ones show...it keeps reverting back to the eaebfec.

Updating sources...
Updating eaebfec..1e6e2fc
Fast-forward
trunk/build_firmware | 1 +
trunk/configs/boards/BN750DB/kernel-3.4.x.config | 3 +-
trunk/configs/boards/KN-EXTRA/kernel-3.4.x.config | 3 +-
trunk/configs/boards/KN-GIGA3/kernel-3.4.x.config | 4 +-
trunk/configs/boards/KN-LITE2/kernel-3.4.x.config | 3 +-
trunk/configs/boards/KN-OMNI/kernel-3.4.x.config | 3 +-
trunk/configs/boards/KN-START2/kernel-3.4.x.config | 3 +-
trunk/configs/boards/KN-ULTRA2/kernel-3.4.x.config | 4 +-
trunk/configs/boards/KN-ULTRA2/kernel-3.4.x.wan_as_lan1.config | 4 +-
trunk/configs/boards/KN-VIVA/kernel-3.4.x.config | 3 +-
trunk/configs/boards/RP-AC56/kernel-3.4.x.config | 3 +-
trunk/configs/boards/RT-AC1200/kernel-3.4.x.config | 3 +-
trunk/configs/boards/RT-AC1200HP/kernel-3.4.x.config | 3 +-
trunk/configs/boards/RT-AC51U/kernel-3.4.x.config | 3 +-
trunk/configs/boards/RT-AC54U/kernel-3.4.x.config | 3 +-
trunk/configs/boards/RT-N11P/kernel-3.4.x.config | 3 +-
trunk/configs/boards/RT-N14U/kernel-3.4.x.config | 3 +-
trunk/configs/boards/RT-N56U/kernel-3.4.x.config | 3 +-
trunk/configs/boards/RT-N56UB1/kernel-3.4.x.config | 4 +-
trunk/configs/boards/RT-N65U/kernel-3.0.x.config | 2 +-
trunk/configs/boards/SWR1100/kernel-3.4.x.config | 3 +-
trunk/linux-3.0.x/arch/mips/kernel/signal.c | 13 +-
trunk/linux-3.0.x/arch/mips/kernel/traps.c | 5 +-
trunk/linux-3.0.x/drivers/net/usb/cdc_ether.c | 50 +
trunk/linux-3.0.x/drivers/net/usb/rndis_host.c | 8 +-
trunk/linux-3.0.x/drivers/net/wireless/ralink/rt2860v2_ap/Makefile | 1 +
trunk/linux-3.0.x/drivers/net/wireless/ralink/rt5392_ap/Makefile | 1 +
trunk/linux-3.0.x/drivers/net/wireless/ralink/rt5592_ap/Makefile | 1 +
trunk/linux-3.0.x/drivers/usb/serial/option.c | 3 +
trunk/linux-3.0.x/net/bridge/br_input.c | 7 +
trunk/linux-3.0.x/net/netfilter/nf_conntrack_h323_asn1.c | 3 +-
trunk/linux-3.4.x/arch/mips/kernel/signal.c | 13 +-
trunk/linux-3.4.x/arch/mips/kernel/traps.c | 5 +-
trunk/linux-3.4.x/drivers/net/usb/cdc_ether.c | 51 +
trunk/linux-3.4.x/drivers/net/usb/rndis_host.c | 8 +-
trunk/linux-3.4.x/drivers/net/wireless/ralink/rt2860v2_ap/Makefile | 1 +
trunk/linux-3.4.x/drivers/net/wireless/ralink/rt5392_ap/Makefile | 1 +
trunk/linux-3.4.x/drivers/net/wireless/ralink/rt5592_ap/Makefile | 1 +
trunk/linux-3.4.x/drivers/usb/serial/option.c | 3 +
trunk/linux-3.4.x/net/bridge/br_input.c | 7 +
trunk/linux-3.4.x/net/ipv6/Kconfig | 2 +-
trunk/linux-3.4.x/net/netfilter/nf_conntrack_h323_asn1.c | 3 +-
trunk/proprietary/rt_wifi/rtpci/2.5.X.X/rtpci/ap/ap_data.c | 18 +-
trunk/proprietary/rt_wifi/rtpci/2.5.X.X/rtpci/common/igmp_snoop.c | 159 +-
trunk/proprietary/rt_wifi/rtpci/2.5.X.X/rtpci/include/igmp_snoop.h | 24 +-
trunk/proprietary/rt_wifi/rtpci/2.7.X.X/rt5392_ap/Makefile | 1 +
trunk/proprietary/rt_wifi/rtpci/2.7.X.X/rt5592_ap/Makefile | 1 +
trunk/proprietary/rt_wifi/rtpci/2.7.X.X/rtpci/ap/ap.c | 4 +
trunk/proprietary/rt_wifi/rtpci/2.7.X.X/rtpci/ap/ap_apcli.c | 108 +-
trunk/proprietary/rt_wifi/rtpci/2.7.X.X/rtpci/ap/ap_cfg.c | 26 +-
trunk/proprietary/rt_wifi/rtpci/2.7.X.X/rtpci/ap/ap_data.c | 16 +-
trunk/proprietary/rt_wifi/rtpci/2.7.X.X/rtpci/ap/apcli_assoc.c | 3 +-
trunk/proprietary/rt_wifi/rtpci/2.7.X.X/rtpci/ap/apcli_ctrl.c | 43 +-
trunk/proprietary/rt_wifi/rtpci/2.7.X.X/rtpci/common/cmm_profile.c | 42 +-
trunk/proprietary/rt_wifi/rtpci/2.7.X.X/rtpci/common/igmp_snoop.c | 130 +-
trunk/proprietary/rt_wifi/rtpci/2.7.X.X/rtpci/common/rtmp_init.c | 64 +-
trunk/proprietary/rt_wifi/rtpci/2.7.X.X/rtpci/include/ap_apcli.h | 18 +-
trunk/proprietary/rt_wifi/rtpci/2.7.X.X/rtpci/include/chip/rtmp_mac.h | 6 +-
trunk/proprietary/rt_wifi/rtpci/2.7.X.X/rtpci/include/igmp_snoop.h | 15 +-
trunk/proprietary/rt_wifi/rtpci/2.7.X.X/rtpci/include/mlme.h | 4 +
trunk/proprietary/rt_wifi/rtpci/2.7.X.X/rtpci/include/rtmp.h | 6 +
trunk/proprietary/rt_wifi/rtpci/3.0.X.X/mt7610/ap/ap.c | 12 +-
trunk/proprietary/rt_wifi/rtpci/3.0.X.X/mt7610/ap/ap_apcli.c | 108 +-
trunk/proprietary/rt_wifi/rtpci/3.0.X.X/mt7610/ap/ap_cfg.c | 26 +-
trunk/proprietary/rt_wifi/rtpci/3.0.X.X/mt7610/ap/ap_data.c | 21 +-
trunk/proprietary/rt_wifi/rtpci/3.0.X.X/mt7610/ap/ap_wpa.c | 2 +-
trunk/proprietary/rt_wifi/rtpci/3.0.X.X/mt7610/ap/apcli_assoc.c | 3 +-
trunk/proprietary/rt_wifi/rtpci/3.0.X.X/mt7610/ap/apcli_ctrl.c | 43 +-
trunk/proprietary/rt_wifi/rtpci/3.0.X.X/mt7610/chips/mt76x0.c | 3 +
trunk/proprietary/rt_wifi/rtpci/3.0.X.X/mt7610/common/cmm_asic.c | 23 +-
trunk/proprietary/rt_wifi/rtpci/3.0.X.X/mt7610/common/cmm_data.c | 100 +-
trunk/proprietary/rt_wifi/rtpci/3.0.X.X/mt7610/common/cmm_profile.c | 41 +-
trunk/proprietary/rt_wifi/rtpci/3.0.X.X/mt7610/common/igmp_snoop.c | 129 +-
trunk/proprietary/rt_wifi/rtpci/3.0.X.X/mt7610/common/rtmp_init.c | 57 +-
trunk/proprietary/rt_wifi/rtpci/3.0.X.X/mt7610/common/rtmp_init_inf.c | 17 -
trunk/proprietary/rt_wifi/rtpci/3.0.X.X/mt7610/include/ap_apcli.h | 18 +-
trunk/proprietary/rt_wifi/rtpci/3.0.X.X/mt7610/include/igmp_snoop.h | 15 +-
trunk/proprietary/rt_wifi/rtpci/3.0.X.X/mt7610/include/rtmp.h | 21 +-
trunk/proprietary/rt_wifi/rtpci/3.0.X.X/mt7610/mgmt/mgmt_entrytb.c | 26 +-
trunk/proprietary/rt_wifi/rtpci/3.0.X.X/mt76x2/ap/ap.c | 13 +
trunk/proprietary/rt_wifi/rtpci/3.0.X.X/mt76x2/ap/ap_apcli.c | 160 +-
trunk/proprietary/rt_wifi/rtpci/3.0.X.X/mt76x2/ap/ap_cfg.c | 25 +-
trunk/proprietary/rt_wifi/rtpci/3.0.X.X/mt76x2/ap/ap_data.c | 22 +-
trunk/proprietary/rt_wifi/rtpci/3.0.X.X/mt76x2/ap/ap_wpa.c | 2 +-
trunk/proprietary/rt_wifi/rtpci/3.0.X.X/mt76x2/ap/apcli_ctrl.c | 54 +-
trunk/proprietary/rt_wifi/rtpci/3.0.X.X/mt76x2/ap/apcli_sync.c | 6 +-
trunk/proprietary/rt_wifi/rtpci/3.0.X.X/mt76x2/chips/rt6352.c | 3 +
trunk/proprietary/rt_wifi/rtpci/3.0.X.X/mt76x2/common/cmm_asic.c | 51 +-
trunk/proprietary/rt_wifi/rtpci/3.0.X.X/mt76x2/common/cmm_cfg.c | 2 +-
trunk/proprietary/rt_wifi/rtpci/3.0.X.X/mt76x2/common/cmm_data.c | 100 +-
trunk/proprietary/rt_wifi/rtpci/3.0.X.X/mt76x2/common/cmm_mac_pci.c | 3 +
trunk/proprietary/rt_wifi/rtpci/3.0.X.X/mt76x2/common/cmm_profile.c | 47 +-
trunk/proprietary/rt_wifi/rtpci/3.0.X.X/mt76x2/common/igmp_snoop.c | 216 +-
trunk/proprietary/rt_wifi/rtpci/3.0.X.X/mt76x2/common/ps.c | 6 +-
trunk/proprietary/rt_wifi/rtpci/3.0.X.X/mt76x2/common/rtmp_init.c | 70 +-
trunk/proprietary/rt_wifi/rtpci/3.0.X.X/mt76x2/common/rtmp_init_inf.c | 13 -
trunk/proprietary/rt_wifi/rtpci/3.0.X.X/mt76x2/include/ap_apcli.h | 19 +-
trunk/proprietary/rt_wifi/rtpci/3.0.X.X/mt76x2/include/igmp_snoop.h | 14 +-
trunk/proprietary/rt_wifi/rtpci/3.0.X.X/mt76x2/include/mlme.h | 2 +-
trunk/proprietary/rt_wifi/rtpci/3.0.X.X/mt76x2/include/rtmp.h | 17 +-
trunk/proprietary/rt_wifi/rtpci/3.0.X.X/mt76x2/rate_ctrl/alg_ags.c | 12 +
trunk/proprietary/rt_wifi/rtpci/3.0.X.X/mt76x2/rate_ctrl/alg_grp.c | 19 +-
trunk/proprietary/rt_wifi/rtpci/3.0.X.X/mt76x2/rate_ctrl/alg_legacy.c | 12 +
trunk/proprietary/rt_wifi/rtpci/4.1.X.X/mt76x3/ap/ap.c | 2 +
trunk/proprietary/rt_wifi/rtpci/4.1.X.X/mt76x3/ap/ap_apcli.c | 132 +-
trunk/proprietary/rt_wifi/rtpci/4.1.X.X/mt76x3/ap/ap_cfg.c | 25 +-
trunk/proprietary/rt_wifi/rtpci/4.1.X.X/mt76x3/ap/ap_data.c | 31 +-
trunk/proprietary/rt_wifi/rtpci/4.1.X.X/mt76x3/ap/apcli_ctrl.c | 38 +-
trunk/proprietary/rt_wifi/rtpci/4.1.X.X/mt76x3/common/cmm_profile.c | 41 +-
trunk/proprietary/rt_wifi/rtpci/4.1.X.X/mt76x3/common/igmp_snoop.c | 332 +-
trunk/proprietary/rt_wifi/rtpci/4.1.X.X/mt76x3/common/rtmp_init.c | 11 +-
trunk/proprietary/rt_wifi/rtpci/4.1.X.X/mt76x3/hw_ctrl/cmm_asic_mt.c | 9 +-
trunk/proprietary/rt_wifi/rtpci/4.1.X.X/mt76x3/include/ap_apcli.h | 21 +-
trunk/proprietary/rt_wifi/rtpci/4.1.X.X/mt76x3/include/igmp_snoop.h | 27 +-
trunk/proprietary/rt_wifi/rtpci/4.1.X.X/mt76x3/include/mlme.h | 2 +-
trunk/proprietary/rt_wifi/rtsoc/2.4.X.X/rt2860v2/ap/ap_data.c | 18 +-
trunk/proprietary/rt_wifi/rtsoc/2.4.X.X/rt2860v2/common/igmp_snoop.c | 159 +-
trunk/proprietary/rt_wifi/rtsoc/2.4.X.X/rt2860v2/include/igmp_snoop.h | 24 +-
trunk/proprietary/rt_wifi/rtsoc/2.4.X.X/rt2860v2/os/linux/rbus_main_dev.c | 2 +-
trunk/proprietary/rt_wifi/rtsoc/2.7.X.X/rt2860v2/ap/ap.c | 12 +-
trunk/proprietary/rt_wifi/rtsoc/2.7.X.X/rt2860v2/ap/ap_apcli.c | 107 +-
trunk/proprietary/rt_wifi/rtsoc/2.7.X.X/rt2860v2/ap/ap_cfg.c | 24 +-
trunk/proprietary/rt_wifi/rtsoc/2.7.X.X/rt2860v2/ap/ap_data.c | 21 +-
trunk/proprietary/rt_wifi/rtsoc/2.7.X.X/rt2860v2/ap/ap_wpa.c | 2 +-
trunk/proprietary/rt_wifi/rtsoc/2.7.X.X/rt2860v2/ap/apcli_ctrl.c | 43 +-
trunk/proprietary/rt_wifi/rtsoc/2.7.X.X/rt2860v2/chips/rt6352.c | 3 +
trunk/proprietary/rt_wifi/rtsoc/2.7.X.X/rt2860v2/common/cmm_asic.c | 23 +-
trunk/proprietary/rt_wifi/rtsoc/2.7.X.X/rt2860v2/common/cmm_data.c | 127 +-
trunk/proprietary/rt_wifi/rtsoc/2.7.X.X/rt2860v2/common/cmm_profile.c | 94 +-
trunk/proprietary/rt_wifi/rtsoc/2.7.X.X/rt2860v2/common/igmp_snoop.c | 130 +-
trunk/proprietary/rt_wifi/rtsoc/2.7.X.X/rt2860v2/common/rtmp_init.c | 68 +-
trunk/proprietary/rt_wifi/rtsoc/2.7.X.X/rt2860v2/common/rtmp_init_inf.c | 10 -
trunk/proprietary/rt_wifi/rtsoc/2.7.X.X/rt2860v2/common/rtmp_timer.c | 2 +-
trunk/proprietary/rt_wifi/rtsoc/2.7.X.X/rt2860v2/include/ap_apcli.h | 18 +-
trunk/proprietary/rt_wifi/rtsoc/2.7.X.X/rt2860v2/include/chip/rtmp_mac.h | 7 +-
trunk/proprietary/rt_wifi/rtsoc/2.7.X.X/rt2860v2/include/igmp_snoop.h | 15 +-
trunk/proprietary/rt_wifi/rtsoc/2.7.X.X/rt2860v2/include/mlme.h | 4 +
trunk/proprietary/rt_wifi/rtsoc/2.7.X.X/rt2860v2/include/rtmp.h | 57 +-
trunk/proprietary/rt_wifi/rtsoc/2.7.X.X/rt2860v2/include/rtmp_timer.h | 2 +-
trunk/proprietary/rt_wifi/rtsoc/2.7.X.X/rt2860v2/os/linux/rbus_main_dev.c | 2 +-
trunk/proprietary/rt_wifi/rtsoc/2.7.X.X/rt2860v2_ap/Makefile | 1 +
trunk/proprietary/rt_wifi/rtsoc/4.1.X.X/mt7628/embedded/ap/ap.c | 2 +
trunk/proprietary/rt_wifi/rtsoc/4.1.X.X/mt7628/embedded/ap/ap_apcli.c | 114 +-
trunk/proprietary/rt_wifi/rtsoc/4.1.X.X/mt7628/embedded/ap/ap_cfg.c | 23 +-
trunk/proprietary/rt_wifi/rtsoc/4.1.X.X/mt7628/embedded/ap/ap_data.c | 16 +-
trunk/proprietary/rt_wifi/rtsoc/4.1.X.X/mt7628/embedded/ap/apcli_ctrl.c | 39 +-
trunk/proprietary/rt_wifi/rtsoc/4.1.X.X/mt7628/embedded/common/cmm_profile.c | 32 +-
trunk/proprietary/rt_wifi/rtsoc/4.1.X.X/mt7628/embedded/common/igmp_snoop.c | 300 +-
trunk/proprietary/rt_wifi/rtsoc/4.1.X.X/mt7628/embedded/common/mlme.c | 37 -
trunk/proprietary/rt_wifi/rtsoc/4.1.X.X/mt7628/embedded/common/rtmp_init.c | 11 +-
trunk/proprietary/rt_wifi/rtsoc/4.1.X.X/mt7628/embedded/common/uapsd.c | 2 +-
trunk/proprietary/rt_wifi/rtsoc/4.1.X.X/mt7628/embedded/include/ap_apcli.h | 18 +-
trunk/proprietary/rt_wifi/rtsoc/4.1.X.X/mt7628/embedded/include/iface/rtmp_rbs.h | 2 +
trunk/proprietary/rt_wifi/rtsoc/4.1.X.X/mt7628/embedded/include/igmp_snoop.h | 20 +-
trunk/proprietary/rt_wifi/rtsoc/4.1.X.X/mt7628/embedded/include/mlme.h | 5 +-
trunk/proprietary/rt_wifi/rtsoc/4.1.X.X/mt7628/embedded/include/rtmp.h | 2 +-
trunk/proprietary/rt_wifi/rtsoc/4.1.X.X/mt7628/hw_ctrl/cmm_asic_mt.c | 39 +-
trunk/proprietary/rt_wifi/rtsoc/4.1.X.X/mt7628/include/hw_ctrl/cmm_asic_mt.h | 2 +-
trunk/proprietary/rt_wifi/rtsoc/4.1.X.X/mt7628/rate_ctrl/alg_grp.c | 4 +-
trunk/proprietary/rt_wifi/rtsoc/4.1.X.X/mt7628/rate_ctrl/alg_legacy.c | 10 +-
trunk/user/aria2/ariaweb/index.html | 2 +-
trunk/user/aria2/ariaweb/js/aria2web.min.js | 2 +-
trunk/user/httpd/web_ex.c | 4 +-
trunk/user/openssh/openssh-7.x/.cvsignore | 28 -
trunk/user/openssh/openssh-7.x/.skipped-commit-ids | 11 +
trunk/user/openssh/openssh-7.x/ChangeLog | 11419 +++++++++++++++++++++++++++++++++-------------------------------
trunk/user/openssh/openssh-7.x/INSTALL | 5 +-
trunk/user/openssh/openssh-7.x/Makefile.in | 45 +-
trunk/user/openssh/openssh-7.x/PROTOCOL | 4 +-
trunk/user/openssh/openssh-7.x/PROTOCOL.agent | 24 +-
trunk/user/openssh/openssh-7.x/PROTOCOL.certkeys | 42 +-
trunk/user/openssh/openssh-7.x/PROTOCOL.chacha20poly1305 | 4 +-
trunk/user/openssh/openssh-7.x/README | 2 +-
trunk/user/openssh/openssh-7.x/audit-linux.c | 28 +-
trunk/user/openssh/openssh-7.x/auth-krb5.c | 3 +-
trunk/user/openssh/openssh-7.x/auth-options.c | 13 +-
trunk/user/openssh/openssh-7.x/auth-pam.c | 107 +-
trunk/user/openssh/openssh-7.x/auth-pam.h | 2 +
trunk/user/openssh/openssh-7.x/auth-passwd.c | 19 +-
trunk/user/openssh/openssh-7.x/auth-rh-rsa.c | 11 +-
trunk/user/openssh/openssh-7.x/auth-rhosts.c | 12 +-
trunk/user/openssh/openssh-7.x/auth.c | 151 +-
trunk/user/openssh/openssh-7.x/auth.h | 7 +-
trunk/user/openssh/openssh-7.x/auth2-chall.c | 6 +-
trunk/user/openssh/openssh-7.x/auth2-hostbased.c | 7 +-
trunk/user/openssh/openssh-7.x/auth2.c | 6 +-
trunk/user/openssh/openssh-7.x/authfile.c | 34 +-
trunk/user/openssh/openssh-7.x/canohost.c | 262 +-
trunk/user/openssh/openssh-7.x/canohost.h | 13 +-
trunk/user/openssh/openssh-7.x/channels.c | 12 +-
trunk/user/openssh/openssh-7.x/cipher-bf1.c | 4 +-
trunk/user/openssh/openssh-7.x/cipher.c | 14 +-
trunk/user/openssh/openssh-7.x/clientloop.c | 12 +-
trunk/user/openssh/openssh-7.x/compat.c | 2 +-
trunk/user/openssh/openssh-7.x/config.h.in | 35 +-
trunk/user/openssh/openssh-7.x/configure | 361 +-
trunk/user/openssh/openssh-7.x/configure.ac | 188 +-
trunk/user/openssh/openssh-7.x/contrib/cygwin/README | 1 +
trunk/user/openssh/openssh-7.x/contrib/redhat/openssh.spec | 4 +-
trunk/user/openssh/openssh-7.x/contrib/ssh-copy-id | 10 +-
trunk/user/openssh/openssh-7.x/contrib/suse/openssh.spec | 4 +-
trunk/user/openssh/openssh-7.x/defines.h | 13 +
trunk/user/openssh/openssh-7.x/dh.c | 116 +-
trunk/user/openssh/openssh-7.x/dh.h | 4 +-
trunk/user/openssh/openssh-7.x/kex.c | 8 +-
trunk/user/openssh/openssh-7.x/kex.h | 17 +-
trunk/user/openssh/openssh-7.x/kexc25519.c | 6 +-
trunk/user/openssh/openssh-7.x/kexdh.c | 9 +-
trunk/user/openssh/openssh-7.x/kexdhc.c | 10 +-
trunk/user/openssh/openssh-7.x/kexdhs.c | 10 +-
trunk/user/openssh/openssh-7.x/kexgexs.c | 4 +-
trunk/user/openssh/openssh-7.x/key.c | 4 +-
trunk/user/openssh/openssh-7.x/log.c | 14 +-
trunk/user/openssh/openssh-7.x/log.h | 4 +-
trunk/user/openssh/openssh-7.x/mac.c | 23 +-
trunk/user/openssh/openssh-7.x/mac.h | 4 +-
trunk/user/openssh/openssh-7.x/misc.c | 150 +-
trunk/user/openssh/openssh-7.x/misc.h | 6 +-
trunk/user/openssh/openssh-7.x/moduli | 474 ++-
trunk/user/openssh/openssh-7.x/moduli.0 | 2 +-
trunk/user/openssh/openssh-7.x/monitor.c | 45 +-
trunk/user/openssh/openssh-7.x/monitor_fdpass.c | 8 +-
trunk/user/openssh/openssh-7.x/monitor_wrap.c | 17 +-
trunk/user/openssh/openssh-7.x/monitor_wrap.h | 10 +-
trunk/user/openssh/openssh-7.x/mux.c | 12 +-
trunk/user/openssh/openssh-7.x/myproposal.h | 15 +-
trunk/user/openssh/openssh-7.x/opacket.h | 4 -
trunk/user/openssh/openssh-7.x/openbsd-compat/.cvsignore | 1 -
trunk/user/openssh/openssh-7.x/openbsd-compat/Makefile.in | 2 +-
trunk/user/openssh/openssh-7.x/openbsd-compat/arc4random.c | 4 +-
trunk/user/openssh/openssh-7.x/openbsd-compat/bindresvport.c | 1 +
trunk/user/openssh/openssh-7.x/openbsd-compat/bsd-asprintf.c | 12 -
trunk/user/openssh/openssh-7.x/openbsd-compat/bsd-err.c | 71 +
trunk/user/openssh/openssh-7.x/openbsd-compat/bsd-misc.c | 17 +
trunk/user/openssh/openssh-7.x/openbsd-compat/bsd-misc.h | 11 +
trunk/user/openssh/openssh-7.x/openbsd-compat/bsd-snprintf.c | 12 -
trunk/user/openssh/openssh-7.x/openbsd-compat/inet_aton.c | 10 +-
trunk/user/openssh/openssh-7.x/openbsd-compat/openbsd-compat.h | 35 +
trunk/user/openssh/openssh-7.x/openbsd-compat/port-solaris.h | 1 +
trunk/user/openssh/openssh-7.x/openbsd-compat/regress/.cvsignore | 6 -
trunk/user/openssh/openssh-7.x/openbsd-compat/vis.c | 60 +-
trunk/user/openssh/openssh-7.x/openbsd-compat/vis.h | 5 +-
trunk/user/openssh/openssh-7.x/openbsd-compat/xcrypt.c | 40 +
trunk/user/openssh/openssh-7.x/packet.c | 142 +-
trunk/user/openssh/openssh-7.x/packet.h | 8 +-
trunk/user/openssh/openssh-7.x/pathnames.h | 4 +-
trunk/user/openssh/openssh-7.x/platform-tracing.c | 43 +
trunk/user/openssh/openssh-7.x/platform.c | 10 +-
trunk/user/openssh/openssh-7.x/platform.h | 1 +
trunk/user/openssh/openssh-7.x/progressmeter.c | 19 +-
trunk/user/openssh/openssh-7.x/readconf.c | 264 +-
trunk/user/openssh/openssh-7.x/readconf.h | 14 +-
trunk/user/openssh/openssh-7.x/regress/.cvsignore | 31 -
trunk/user/openssh/openssh-7.x/regress/Makefile | 49 +-
trunk/user/openssh/openssh-7.x/regress/agent-getpeereid.sh | 25 +-
trunk/user/openssh/openssh-7.x/regress/cert-hostkey.sh | 126 +-
trunk/user/openssh/openssh-7.x/regress/cert-userkey.sh | 48 +-
trunk/user/openssh/openssh-7.x/regress/cfginclude.sh | 293 ++
trunk/user/openssh/openssh-7.x/regress/cfgparse.sh | 4 +-
trunk/user/openssh/openssh-7.x/regress/connect-privsep.sh | 7 +-
trunk/user/openssh/openssh-7.x/regress/forwarding.sh | 4 +-
trunk/user/openssh/openssh-7.x/regress/integrity.sh | 4 +-
trunk/user/openssh/openssh-7.x/regress/misc/Makefile | 3 +
trunk/user/openssh/openssh-7.x/regress/misc/kexfuzz/Makefile | 78 +
trunk/user/openssh/openssh-7.x/regress/misc/kexfuzz/README | 28 +
trunk/user/openssh/openssh-7.x/regress/misc/kexfuzz/kexfuzz.c | 410 +++
trunk/user/openssh/openssh-7.x/regress/modpipe.c | 31 +-
trunk/user/openssh/openssh-7.x/regress/netcat.c | 43 +-
trunk/user/openssh/openssh-7.x/regress/sshcfgparse.sh | 29 +
trunk/user/openssh/openssh-7.x/regress/test-exec.sh | 10 +-
trunk/user/openssh/openssh-7.x/regress/unittests/Makefile | 4 +-
trunk/user/openssh/openssh-7.x/regress/unittests/sshbuf/test_sshbuf_misc.c | 31 +-
trunk/user/openssh/openssh-7.x/regress/unittests/sshkey/test_sshkey.c | 4 +-
trunk/user/openssh/openssh-7.x/regress/unittests/test_helper/Makefile | 3 +-
trunk/user/openssh/openssh-7.x/regress/unittests/utf8/Makefile | 12 +
trunk/user/openssh/openssh-7.x/regress/unittests/utf8/tests.c | 82 +
trunk/user/openssh/openssh-7.x/roaming.h | 0
trunk/user/openssh/openssh-7.x/sandbox-seccomp-filter.c | 6 +
trunk/user/openssh/openssh-7.x/scard/.cvsignore | 2 -
trunk/user/openssh/openssh-7.x/scp.0 | 6 +-
trunk/user/openssh/openssh-7.x/scp.1 | 8 +-
trunk/user/openssh/openssh-7.x/scp.c | 53 +-
trunk/user/openssh/openssh-7.x/servconf.c | 60 +-
trunk/user/openssh/openssh-7.x/serverloop.c | 47 +-
trunk/user/openssh/openssh-7.x/session.c | 47 +-
trunk/user/openssh/openssh-7.x/session.h | 4 +-
trunk/user/openssh/openssh-7.x/sftp-client.c | 14 +-
trunk/user/openssh/openssh-7.x/sftp-server.0 | 2 +-
trunk/user/openssh/openssh-7.x/sftp-server.c | 10 +-
trunk/user/openssh/openssh-7.x/sftp.0 | 6 +-
trunk/user/openssh/openssh-7.x/sftp.1 | 8 +-
trunk/user/openssh/openssh-7.x/sftp.c | 77 +-
trunk/user/openssh/openssh-7.x/ssh-add.0 | 2 +-
trunk/user/openssh/openssh-7.x/ssh-agent.0 | 2 +-
trunk/user/openssh/openssh-7.x/ssh-agent.c | 24 +-
trunk/user/openssh/openssh-7.x/ssh-dss.c | 5 +-
trunk/user/openssh/openssh-7.x/ssh-ecdsa.c | 5 +-
trunk/user/openssh/openssh-7.x/ssh-ed25519.c | 5 +-
trunk/user/openssh/openssh-7.x/ssh-keygen.0 | 21 +-
trunk/user/openssh/openssh-7.x/ssh-keygen.1 | 12 +-
trunk/user/openssh/openssh-7.x/ssh-keygen.c | 18 +-
trunk/user/openssh/openssh-7.x/ssh-keyscan.0 | 2 +-
trunk/user/openssh/openssh-7.x/ssh-keyscan.c | 5 +-
trunk/user/openssh/openssh-7.x/ssh-keysign.0 | 2 +-
trunk/user/openssh/openssh-7.x/ssh-pkcs11-helper.0 | 2 +-
trunk/user/openssh/openssh-7.x/ssh-rsa.c | 5 +-
trunk/user/openssh/openssh-7.x/ssh.0 | 27 +-
trunk/user/openssh/openssh-7.x/ssh.1 | 33 +-
trunk/user/openssh/openssh-7.x/ssh.c | 140 +-
trunk/user/openssh/openssh-7.x/ssh1.h | 3 +-
trunk/user/openssh/openssh-7.x/ssh2.h | 6 +-
trunk/user/openssh/openssh-7.x/ssh_api.c | 10 +-
trunk/user/openssh/openssh-7.x/ssh_config.0 | 40 +-
trunk/user/openssh/openssh-7.x/ssh_config.5 | 77 +-
trunk/user/openssh/openssh-7.x/sshbuf-getput-basic.c | 8 +-
trunk/user/openssh/openssh-7.x/sshbuf-misc.c | 25 +-
trunk/user/openssh/openssh-7.x/sshbuf.h | 9 +-
trunk/user/openssh/openssh-7.x/sshconnect2.c | 96 +-
trunk/user/openssh/openssh-7.x/sshd.0 | 2 +-
trunk/user/openssh/openssh-7.x/sshd.c | 179 +-
trunk/user/openssh/openssh-7.x/sshd_config | 3 +-
trunk/user/openssh/openssh-7.x/sshd_config.0 | 41 +-
trunk/user/openssh/openssh-7.x/sshd_config.5 | 28 +-
trunk/user/openssh/openssh-7.x/sshkey.c | 44 +-
trunk/user/openssh/openssh-7.x/sshkey.h | 4 +-
trunk/user/openssh/openssh-7.x/ttymodes.c | 3 +-
trunk/user/openssh/openssh-7.x/ttymodes.h | 5 +-
trunk/user/openssh/openssh-7.x/utf8.c | 290 ++
trunk/user/openssh/openssh-7.x/utf8.h | 24 +
trunk/user/openssh/openssh-7.x/version.h | 6 +-
trunk/user/rc/net_wifi.c | 32 +-
trunk/user/rc/ralink.c | 8 +-
trunk/user/rc/services.c | 3 +
trunk/user/shared/cflags.mk | 3 +-
trunk/user/shared/defaults.c | 2 -
trunk/user/www/n56u_ribbon_fixed/Advanced_System_Content.asp | 2 +-
336 files changed, 12882 insertions(+), 9608 deletions(-)
delete mode 100644 trunk/user/openssh/openssh-7.x/.cvsignore
create mode 100644 trunk/user/openssh/openssh-7.x/.skipped-commit-ids
delete mode 100644 trunk/user/openssh/openssh-7.x/openbsd-compat/.cvsignore
create mode 100644 trunk/user/openssh/openssh-7.x/openbsd-compat/bsd-err.c
delete mode 100644 trunk/user/openssh/openssh-7.x/openbsd-compat/regress/.cvsignore
create mode 100644 trunk/user/openssh/openssh-7.x/platform-tracing.c
delete mode 100644 trunk/user/openssh/openssh-7.x/regress/.cvsignore
create mode 100644 trunk/user/openssh/openssh-7.x/regress/cfginclude.sh
create mode 100644 trunk/user/openssh/openssh-7.x/regress/misc/Makefile
create mode 100644 trunk/user/openssh/openssh-7.x/regress/misc/kexfuzz/Makefile
create mode 100644 trunk/user/openssh/openssh-7.x/regress/misc/kexfuzz/README
create mode 100644 trunk/user/openssh/openssh-7.x/regress/misc/kexfuzz/kexfuzz.c
create mode 100644 trunk/user/openssh/openssh-7.x/regress/sshcfgparse.sh
create mode 100644 trunk/user/openssh/openssh-7.x/regress/unittests/utf8/Makefile
create mode 100644 trunk/user/openssh/openssh-7.x/regress/unittests/utf8/tests.c
delete mode 100644 trunk/user/openssh/openssh-7.x/roaming.h
delete mode 100644 trunk/user/openssh/openssh-7.x/scard/.cvsignore
create mode 100644 trunk/user/openssh/openssh-7.x/utf8.c
create mode 100644 trunk/user/openssh/openssh-7.x/utf8.h
Previous HEAD position was 1e6e2fc... openssh: bump to 7.3p1
HEAD is now at eaebfec... re-implement previous commit


This post has been edited by FameWolf: Aug 3 2016, 12:04 PM
FameWolf
post Aug 4 2016, 03:34 AM

New Member
*
Junior Member
26 posts

Joined: Jun 2016


Be aware the Xiaomi development software is dangerous and you shouldn't stay on it any longer than necessary.

http://en.wooyun.io/2015/07/06/A-Review-of...rs-Browser.html
FameWolf
post Sep 25 2016, 10:20 PM

New Member
*
Junior Member
26 posts

Joined: Jun 2016


QUOTE(TerryZeroX @ Sep 25 2016, 02:44 AM)
Yikes the link for the Breed Bootloader is broken, is there any otherway to obtain it?

EDIT:
Found the link from their site
*
Do they have a version that's all in english yet?
FameWolf
post Sep 28 2016, 12:50 PM

New Member
*
Junior Member
26 posts

Joined: Jun 2016


QUOTE(TerryZeroX @ Sep 27 2016, 11:24 PM)
I don't think so, just follow the guide on the 1st post from this thread you should be fine smile.gif Perfect firmware for the mi wifi mini. After countless try on pandora and openwrt I was about to give up then i saw this.
*
I was referring to the breed bootloader. I have the padavan firmware working fine.
FameWolf
post Oct 7 2016, 04:28 PM

New Member
*
Junior Member
26 posts

Joined: Jun 2016


QUOTE(muncheno @ Oct 7 2016, 03:19 AM)
Hi, I would like to thanks the TS for the thread and sharing here.

On yesterday night I finally find the time and guts to flash my Mi Mini router with Pavadan following the instructions from here and pavadan firmware from <here>.

http://plol.eu/how-to-install-a-full-spec-...mi-router-mini/

I was setting the mini router as repeater (AP + WDS) on 5ghz wifi to my Xiaomi Router 3 (original firmware).
The router was spacing apart with 1 wall, distance around 7-8m apart and I checked the status from pavadan the STA are linking at around 4XX-5XX Mbps which better than my powerplugs.
Within 3m apart, it was link at 7XXMbps which extreme good for me. smile.gif

Overall I'm very happy with it, however problem seem getting from Xiaomi Router 3 which whenever I reboot Mi3 the wifi channel run even I have set it on fix channel. Thus is break the link to the repeater.

So now, I'm thinking to flash my Mi3 (router 3) with pavadan.

Being a newbie to this, I want to know if anyone have build the firmware for Mi3 for sharing here?
I'm not very good with linux and prometheus, worry that I screw up my Mi3.
*
I used the prometheus script to flash padavan to my mi-3. You either have to jump through some hoops or downgrade the firmware on the mi-3 to a version that allows ssh. The script can then interface to build and flash padavan. Not sure what else I could tell you. You can't just share a file. Multiple partitions get flashed on the mi-3. You HAVE to use the script and compile it then let the script do the flashing.

This post has been edited by FameWolf: Oct 7 2016, 04:29 PM
FameWolf
post Oct 11 2016, 01:47 PM

New Member
*
Junior Member
26 posts

Joined: Jun 2016


QUOTE(muncheno @ Oct 11 2016, 12:22 AM)
Update here,

I found the Mi-3 pavadan firmware from  <here>.

http://plol.eu/how-to-install-a-full-spec-...mi-router-mini/

Problem don't know how to flash it.
Whether we can use bleed bootloader for Xiaomi Mini onto Mi-3 or not.
Or just directly flash it using SSH.

Any advises? Wanted to listen to your opinion before I flash my MI-3 tonight or tmr9.
For me that I consider newbie, likely I will use the tested method - Promotheus script.

Thanks.
*
I did alot of research on it before I flashed the MI-3 which I use right now as my primary router. I was told it could NOT successfully be flashed to padavan via a .trx or whatever file...that it required the script because multiple partitions have to be flashed(and possibly resized)...it also installs the uboot firmware...no breed isn't available for it...but the script can take partition backups and makes it pretty bullet proof...you can also use virtualbox...you might check the prometheus.frieze.net side as I think they had a pre-setup vmware image that could be booted...I compiled mine directly on linux since that's what I use. ..the tutorial takes you through a complicated process that involves registering on the xiaomi website..getting a patched file etc...I recommend you skip all that and get your device flashed to the previous version which still allowed ssh to be enabled...once that's working the script is basically numbered...download source, build the toolchain, build the firmware, backup the partitions, write the firmware.
FameWolf
post Oct 11 2016, 02:05 PM

New Member
*
Junior Member
26 posts

Joined: Jun 2016


QUOTE(muncheno @ Oct 11 2016, 12:59 AM)
Agree with your points here.

Question here, when running prometheues scripts, is the your Mi-3 router still connecting to internet as primary while download source, build the toolchain, build the firmware, backup the partitions, write the firmware. ?

Thanks.
*
Well now that it's on padavan and being upgraded yeah...not sure I'd let their factory firmware have access to the net given reports some of it's developer factory xiaomi versions phoned home. The only time it would be down is the actual writing and that takes no more than a minute with about an additional 20 seconds for the router to reboot itself.


Be aware however that the padavan software does NOT include QOS because QOS and hardware NAT are mutually exclusive...if you NEED QOS then you have to disable hardware NAT and then configure some script to setup QOS because the gui won't do it. The cpu in the router is easily powerful enough to do it without issue...I just personally chose to keep the hardware nat going.
FameWolf
post Oct 11 2016, 11:24 PM

New Member
*
Junior Member
26 posts

Joined: Jun 2016


QUOTE(muncheno @ Oct 11 2016, 08:52 AM)
Update here,

I'm flashing my MI-3 to pavadan with Prometheus scripts with Linux Mint on my old netbook.

What I did is follow the instructions given to ssh to MI-3 router.
This is referring to flashing developer firmware 2.11.20 then;
flashing miwifi_ssh.bin with reset button;
and I was using putty.exe to telnet instead ssh, somehow it is mistake here.

Not knowing at the time, I did using these method below as well
Then I recall must use ssh, and from there I manage to access to the router via ssh at 192.168.31.1.

From here onward, I switch to running on linux mint and follow the code:-
Linux system:
1. Open a terminal;
2. Download the script by typing: the wget -O start.sh http://prometheus.freize.net/script/ start-99.sh
3. Enter: the chmod + x start.sh
4. Run the script and follow the instructions in the terminal: ./start.sh

Once the scripts started, it download a bunch of files from the net. I have saw an error half way, it mentions my internet was too slow (something like that) then I could only see header of Prometheus.

So I start again with ./start.sh.

It run again but this time go further and I'm at the Prometheus menu.
Following the nos, I key in (1) to check ssh access to MI-3 router
Then (2) and (3)......

I been waiting more approx 2 hrs for it to build the toolchain now......still building with command from scripts keep flashing on the screen.....................  not sure I should start worry. (note: internet still running on Mi-3 router)

edit: After 2hrs+ only manage to reach build firmware to configure options and skins. Now build firmware.....
*
You only have to build the toolchain once. wink.gif I've got a pretty fast I7 and even with it the compiling takes a little while so sounds about normal.
FameWolf
post Oct 12 2016, 12:04 AM

New Member
*
Junior Member
26 posts

Joined: Jun 2016


QUOTE(infrasonic @ Oct 11 2016, 11:00 AM)
My Xiaomi Router 3 had been sitting in the store for quite a long time after I got my Unifi and it doesn't work on Unifi..

Does the instructions on first post works on Xiaomi Router 3 to flash to OpenWRT?
*
No but the 5 or 6 posts DIRECTLY above yours do.

2 Pages  1 2 >Top
 

Change to:
| Lo-Fi Version
0.0476sec    0.69    7 queries    GZIP Disabled
Time is now: 1st December 2025 - 12:21 AM