MiWiFi | Xiaomi Mi-router (R1D) - Discussion | [wifirouter] Settings, Help
Questionnaire
What bugs / glitches happen or happened to your router or did everything go smoothly and without sadness?
Wan falls off [ 82 ] ** [5,77%]
Wi-Fi falls off on a connected device [ 153 ] ** [10,77%]
Wi-Fi falls off / slows down at the router [ 130 ] ** [9,15%]
All interfaces fall off, the router goes into a soft-reboot [ 27 ] ** [1,9%]
Samba falls off [ 26 ] ** [1,83%]
Limits speed [ 146 ] ** [10,28%]
Hard drive crashed [ 22 ] ** [1,55%]
Hardware failure [ 15 ] ** [1,06%]
There are no problems, the router is a model of stability and performance! [ 460 ] ** [32,39%]
I do not know any problems. I stuck the cable, set up the wafer with the password 11111111 and did not climb anywhere else / hard went into my pocket. [ 370 ] ** [26,06%]
Total votes: 1420
 



Rep: (811)
Xiaomi Mi Router (R1D) - Discussion
MiWiFi | Xiaomi Mi-router (R1D) - Firmware | Xiaomi MiWiFi (client for Android) | Xiaomi MiWiFi (client for Windows)
Xiaomi Mi-router (R2D) - Discussion | MiWiFi mini | Xiaomi Mi-router mini | Xiaomi club



Attached Image


Attention!
Description
Additional Images
Attached Image
Attached Image
Attached ImageAttached Image
Attached Image
Attached ImageAttached Image
Attached Image


Productive solution - dual-band smart AC router with internal 1 TB disk.
Official price (in China): 699 е…ѓ (yuan) ~ 115 $ ~ 4000 rub.
Gigabit Wi-Fi came with an AC router! 3 times faster! Supports the latest 802.11ac protocol, using the most powerful Broadcom BCM4709 processor.
Modern equipment fully supports the latest version of Wi-Fi protocol 802.11ac. Has your router entered the era of AC?
miWiFi is a modern dual-band router with the highest data transfer rate - up to 1167 Mbit / s. The Broadcom dual-core CPU and 256MB of Micron / Samsung memory ensure stable high-speed booting, preloading, network acceleration, a wealth of additional applications and superior performance to a 1 TB hard drive.

Specifications
- 2-core processor Broadcom BCM4709 (Cortex-A9) with a frequency of 1 GHz
- 256 MB RAM DDR3
- 1 TB SATA (Toshiba / Samsung) hard drive (internal SATA)
- Supports 802.11ac WiFi in two bands, at 2.4 GHz and 5 GHz
- NFC support
- 1 WAN port
- 2 LAN ports
- holes for 40 mm fans
- A cover at the bottom of the case.
Reviews and Tests
Instructions
Useful
Poll results
Attached Image


Topics CuratorEugener , for questions about filling caps contact in QMS .


Post has been editedAndrewP_1 - 12.09.18, 22:36
Reason for editing: renewal, completed by SKALDEK



Rep: (311)
* lightvik,
TrackScream solved this problem, you need to ask him



Rep: (207)
There was a small question for the Guru of this router. Is it possible to make ready-made firmware instead of the crack, just to select it through the installation and install immediately with the Russian language and access via SSH, as Romz and miui.su do (for phones)?



Rep: (178)
* lightvik, I don’t know what’s wrong with your Russification, the rights to files are in perfect order, you need to look at the nginx logs for what he swears.
* Interfere, technically, there is such an opportunity, but a router is required to create the firmware file, which I do not currently have. There are also pitfalls: the firmware file, as I said, has a digital signature that the router checks before starting the installation. It is not possible to get a signature from Xiaomi, the changed file will have to be signed on its own. Therefore, to install the Russified firmware file using the web-muzzle, you will have to replace the public key in the router, which will lead to the inability to install official OTA updates. I have a suspicion that when flashing firmware using a flash drive (with the reset pressed), the signature is not checked and it is possible in this way to put Russified firmware bypassing digital keys, but this option requires verification.



Rep: (441)
logs
http://rghost.ru/57764285

Post has been editedlightvik - 30.08.14, 14:46



Rep: (178)
* lightvik, forgot to clarify. Despite the settings spelled out by the Chinese, nginx does not write anything in messages. In order to write server logs, you need to edit the file /etc/sysapihttpd/sysapihttpd.conf and before the line "error_log stderr warn;" add the line "error_log /userdisk/sysapihttpd/log/warn.log warn;". After that, reboot the router, the error log will be written accordingly in /userdisk/sysapihttpd/log/warn.log

Post has been editedTrackscream - 30.08.14, 14:55



Rep: (207)
I installed the development firmware today (.37), then updated it to the latest. I tried to access via SSH, it did not work. I wrote a couple about (... refused), but the problem was that now the IP address settings are not saved. I enter them, click save, it seems that the cheto saves, but in the end, nothing was saved. After a huge number of times, the settings were saved. I rolled back the firmware an ode back, got access via SSH, but the ip settings are not saved again and again after a huge number of attempts were saved. Now I want to drive in the white IP address and it does not save again. Tell me where to dig and what could be the problem?

upd: Found what the problem is. for some reason, he does not want to save the subnet mask as 255.255.255.192, saved from 0 at the end.

Post has been editedInterfere - 30.08.14, 16:57
Reason for editing: upd:



Rep: (441)
/userdisk/sysapihttpd/log/warn.log

warn.log did not appear. error file:
1970/01/01 21:00:14 [info] 4113 # 0: cache_dir: / userdisk / cachecenter / cache_dir /, next_location: / http_proxy /. in /tmp/sysapihttpdconf/sysapihttpd.conf{98
1970/01/01 21:00:14 [warn] 4113 # 0: the "log_format" directive may be used only on "http" level in /tmp/sysapihttpdconf/sysapihttpd.confrige19
1970/01/01 21:00:14 [info] 4113 # 0: next_location: / proxy /. in /tmp/sysapihttpdconf/sysapihttpd.confrige26
1970/01/01 21:00:14 [warn] 4141 # 0: the "log_format" directive may be used only on "http" level in /tmp/sysapihttpdconf/sysapihttpd.confrige19
1970/01/01 21:00:11 [info] 3289 # 0: cache_dir: / userdisk / cachecenter / cache_dir /, next_location: / http_proxy /. in /tmp/sysapihttpdconf/sysapihttpd.conf{98
1970/01/01 21:00:11 [warn] 3289 # 0: the "log_format" directive may be used only on "http" level in /tmp/sysapihttpdconf/sysapihttpd.confrige19
1970/01/01 21:00:11 [info] 3289 # 0: next_location: / proxy /. in /tmp/sysapihttpdconf/sysapihttpd.confrige26
1970/01/01 21:00:11 [warn] 3363 # 0: the "log_format" directive may be used only on "http" level in /tmp/sysapihttpdconf/sysapihttpd.conf:419
1970/01/01 21:00:11 [info] 3421 # 0: cache_dir: / userdisk / cachecenter / cache_dir /, next_location: / http_proxy /. in /tmp/sysapihttpdconf/sysapihttpd.conf{98
1970/01/01 21:00:11 [warn] 3421 # 0: the "log_format" directive may be used only on "http" level in /tmp/sysapihttpdconf/sysapihttpd.confrige19
1970/01/01 21:00:11 [info] 3421 # 0: next_location: / proxy /. in /tmp/sysapihttpdconf/sysapihttpd.confrige26
1970/01/01 21:00:12 [warn] 3488 # 0: the "log_format" directive may be used only on "http" level in /tmp/sysapihttpdconf/sysapihttpd.confrige19
1970/01/01 19:00:11 [info] 3345 # 0: cache_dir: / userdisk / cachecenter / cache_dir /, next_location: / http_proxy /. in /tmp/sysapihttpdconf/sysapihttpd.conf{98
1970/01/01 19:00:11 [warn] 3345 # 0: the "log_format" directive may be used only on "http" level in /tmp/sysapihttpdconf/sysapihttpd.confrige19
1970/01/01 19:00:11 [info] 3345 # 0: next_location: / proxy /. in /tmp/sysapihttpdconf/sysapihttpd.confrige26
1970/01/01 19:00:11 [warn] 3363 # 0: the "log_format" directive may be used only on "http" level in /tmp/sysapihttpdconf/sysapihttpd.confrige19


Post has been editedlightvik - 30.08.14, 17:07



Rep: (207)
I apologize for a possibly stupid question, but I did not find it in the topic. What do you need to register commands for mounting through? In the instructions, a variant with the winSCP program is offered, can you crack crack through this program?



Rep: (178)
* lightvik, There are no error entries here. When an error fell out due to a previous translation, the log was like this:
2014/08/29 04:16:58 [error] 1628 # 0: * 16 FastCGI sent in stderr: "fcgi-cgi.c: 387: couldn't execve '/ www / cgi-bin / luci': Permission denied "; ACT = 'reading response header from upstream'; CLI = '192.168.1.111'; SRV = '0.0.0.0: 80'; REQUEST = 'GET / cgi-bin / luci /; stok = 904a4ccb0146ade1647632bf37c34728 / web / home HTTP /1.1';UPSTREAM='fastcgi://unix:/tmp/fcgi-cgi.sock:';HOST='miwifi.com '
2014/08/29 04:16:58 [error] 1628 # 0: * 16 upstream prematurely closed FastCGI stdout; ACT = 'reading response header from upstream'; CLI = '192.168.1.111'; SRV = '0.0.0.0: 80 '; REQUEST =' GET / cgi-bin / luci /; stok = 904a4ccb0146ade1647632bf37c34728 / web / home HTTP / 1.1 '; UPSTREAM =' fastcgi: // unix: /tmp/fcgi-cgi.sock: '; HOST =' miwifi.com '


* Interfere, You can connect to the ssh console using the putty program. how to upload the archive to the device is written in the instructions: you can use a USB flash drive, you can upload it to the internal hard drive using standard windows tools (type in the address bar of the windows explorer "\\ 192.168.31.1" (the ip address of the router with two backslashes) and press Enter) .

Post has been editedTrackscream - 30.08.14, 17:24



Rep: (207)
I will write a short instruction for dummies like me.
To access the router via SSH, you need the PuTTY program, you can download it in Google. Then after I got access through the instructions in the header. Launched this program. I entered the word root in the first line, in the next line I entered the password that I used to check access through winSCP. And after that I entered all the commands that are in the instructions for Russification. Everything was done without problems, I updated the page in the browser and everything became in Russian. It may be useful to beginners and those who will be the first time to do all this, like me.

Post has been editedInterfere - 30.08.14, 17:57



Rep: (207)
* EuGenEr, How did you solve the problem with Internal Server Error after rebooting?



Rep: (441)
Interfere @ 08/30/2014, 9:26 PM*
EuGenEr, how did you solve the problem with Internal Server Error after rebooting?

yes, we haven’t decided it yet. I generally have the web admin died, I think how better to flash / fix the web interface.
Something is not right in 0.7.58 with Russification. there were no problems before.

Trackscream, please highlight the commands using the code tag, something like this:
error_log /userdisk/sysapihttpd/log/warn.log warn;

otherwise I thought that the extra quotes

in general, after editing the file, and rebooting the log did not appear. the web server died altogether - there is no response from either Lucy's native or aria. web transmission works (well, it is separate from uhttpd).

Post has been editedlightvik - 30.08.14, 19:01



Rep: (81)
Nobody tried with 4g?



Rep: (178)
* lightvik, this is already very strange. The web server will not die from this line. And if you try to start manually?
/ bin / sh /usr/sbin/sysapihttpd.loader

You can roll back firmware using a flash drive, or upload a file to the router’s disk and give a command to flash:
/bin/flash.sh /path/to/miwifi.bin 0

at the end 0 - restart the router after the firmware, 1 - do not restart.



Rep: (441)
TrackScream @ 08/30/2014, 10:05 PM*
And if you try to start manually?

/ bin / sh /usr/sbin/sysapihttpd.loader
INFO: main conf: /tmp/sysapihttpdconf/sysapihttpd.conf

but at the address of the router the admin does not open. I even returned the native files to the place.
TrackScream @ 08/30/2014, 10:05 PM*
either upload the file to the router’s disk and give the command for firmware:

will nothing disappear from my HDD? After all, if you sew from a flash drive, it formats the HDD.

the whole problem is that tomorrow to fly to Russia, revive the web-gui and go quietly on business: mellow :.

update:
removed the line - started (returned the China admin panel to the place for the time being)

Post has been editedlightvik - 30.08.14, 19:40



Rep: (13)
TrackScream @ 08.28.2014, 22:39*
only under the beeline you have to tinker with manual configuration (for the L2TP beeline as far as I remember).

No messing around there, sort of. By default, connection parameters are entered and that’s it. Another question is how stable it will work. I just had a problem with the constant disconnection. :( It was not possible to overcome it - I use an ordinary router.

Post has been editedVlRUS - 03.09.14, 12:41



Rep: (441)
Interfere @ 08/30/2014, 9:26 PM*
How did you solve the problem with Internal Server Error after rebooting?

download 2 archives from this postMiWiFi | Xiaomi Mi-router (Post # 33887047)
put them in the root of the disk accessible to the user
enter in turn
mount -o remount, rw /

tar -zxvf /userdisk/data/lua.tar.gz -C /

tar -zxvf /userdisk/data/www.tar.gz -C /


The router will become backin EnglishChinese. I’ll come from Russia to my homeland - I will find where I broke something in translation (although I changed in such places that it seems to me that I have nothing to do with it)

Post has been editedlightvik - 30.08.14, 19:47



Rep: (178)
* VlRUS, that’s just why you need to climb your hands inside. My provider distributes PPPoE for me, and rejects encryption and pap- and mschap-authorization. The connection was not established at all, it was necessary to manually rewrite the generated lucie config.

* lightvik, So I didn’t find anything criminal in your translation. At first glance, everything should work without problems.

Post has been editedTrackscream - 30.08.14, 19:50



Rep: (207)
By the way, I used the translation from a reputable TrackScream. Therefore, I think that the problem is in Chinese firmware.



Rep: (178)
* Interfere, Yes, in this case, the problem lies somewhere in the bowels of the firmware itself. It's hard to judge anything without logs, I can fix it at best in a couple of weeks

Post has been editedTrackscream - 30.08.14, 20:54


Full version    

Help     rules

Now: 09/16/19, 15:39