Posted: Sat Jan 06, 2018 8:50 Post subject: E1200 V2 on Firmware: DD-WRT v3.0-r29519 mega (04/25/16)
Hi guys,
I had recently converted my E1200 V2 into wireless bridge as per firmware above following the guide on this link.
https://www.dd-wrt.com/wiki/index.php/Wireless_Bridge
I had followed all the steps except I had turned on SPI firewall as I need to allow multicast enabled checked.
So far i had no issue with the repeater, but the rate reported on the status page is only around 54-65MbPS (I had used NG mixed)
and some error reported on the RX.
Of course, there is another issue where i cannot used my LAN port, where the client connected are actually assigned an 169.XX IP. I had read through this page
https://www.dd-wrt.com/wiki/index.php/Linksys_E1500#Recovering_from_Management_Mode_Firmware_Recovery_or_No_ethernet_connection
which i guess it is a potential fixed for my problem. However, i just loafing this thread and found this topic and realized that there is a very latest build (3XXXX) which I can see somebody had tried it.
Here's some question of mine
1) What is the latest supported DD-WRT firmware for this device (E1200 V2)
2) What is the update procedure the latest supported firmware in (1) ?
Appreciate guys
***UPDATE***
I had flashed my E1200 to Build 33555 and mysteriously, the wired LAN issue solved.
So far had been running 2 days with this version and seems no issue.
On my fairly vanilla configuration I have 2 full days of uptime, 16,000MB of ingress, and 800MB of egress behind me. I'm using the default settings aside from changing the root password, renaming the SSID, enabling WPA2 Personal wireless security, and pointing DNS at DNS.WATCH's resolvers. An hour ago I also enabled the OpenVPN client, and it has been solid aside from the significantly reduced ingress capability of about 3Mbps (which at a glance appears to be bottlenecked at the router CPU, although I have not yet attempted to diagnose and could be a result of many factors external to the router).
The only two issues I have observed are trivial:
1. After applying Restore Factory Defaults, it is necessary to power cycle the router in order to bring it back to life. During the process of flashing from the original Linksys firmware to DD-WRT, I also observed this behavior on at least one of the older builds along the way. I've seen it mentioned in this Forum several times, so it is a known nuance.
2. Enabling HTTPS web access to the DD-WRT Control Panel does not appear to work. I'm not exposing the Control Panel to the outside, so https is not absolutely necessary for me, this is just something I noticed.
I am just writing this to share my experience with DD-WRT 33986 on the Linksys E1200 v2 router, and to thank jpp for sharing his experience with this build - I am not writing to ask for help at this time. I wanted to try configuring OpenVPN on a router current enough to have vulnerabilities like KRACK addressed, which lead me to DD-WRT. Perhaps the above will be useful to someone with similar thoughts.
I am using : DD-WRT v3.0-r34929 mega 02/12/18 on two e1200v2 and i am getting a few errors on the logs related to igmp:
user.warn igmpproxy[1585]: MRT_DEL_MFC; Errno(2): No such file or directory
user.warn igmpproxy[1585]: No interfaces found for source 0.0.0.0
igmpproxy[2306]: select() failure; Errno(4): Interrupted system call
Any thoughts?
My HP printer has some connectivity problems with the same router and i read that printer uses multicast / bonjour / mdns settings to work.
Posted: Tue Oct 09, 2018 13:07 Post subject: K2.6 mini support for JFFS2
This might be a little off topic so let me know if I need to start a new thread.
I'm trying to install Shadowsocks on my Linksys E1200 v.2 router using DD-WRT but all the mega builds do not have JFFS2 support nor does it leave enough space for JFFS2 to be incorporated after installing Entware. According to this list, I would need to install the K.2.6 mini build to obtain JFFS2 support and it is currently available for download for this router.
Should I flash this factory flash firmware over my current DD-WRT firmware and use it as is?
Posted: Tue Oct 09, 2018 16:16 Post subject: Re: K2.6 mini support for JFFS2
konker wrote:
This might be a little off topic so let me know if I need to start a new thread.
I'm trying to install Shadowsocks on my Linksys E1200 v.2 router using DD-WRT but all the mega builds do not have JFFS2 support nor does it leave enough space for JFFS2 to be incorporated after installing Entware. According to this list, I would need to install the K.2.6 mini build to obtain JFFS2 support and it is currently available for download for this router.
Should I flash this factory flash firmware over my current DD-WRT firmware and use it as is?
Okay, I found out I was wrong. The mega and big builds do have JFFS2 support in the K2.6 firmware. But whatever I tried to flash that version over the current Firmware: DD-WRT v3.0-r36698 mega (08/22/1 does not seem to work. I also discovered that the v3.0 firmware has JFFS2 support but no matter what I did, I could not mount the jffs partition. Any ideas?
I'm using the Firmware: DD-WRT v3.0-r37405 mega (10/16/1
I have 60mb/6mb
When I'm playing, my ping keep spiking too much...
I did a ping 192.168.1.1 and I saw this:
Code:
Resposta de 192.168.1.1: bytes=32 tempo=116ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo=11ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo=39ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo<1ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo<1ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo<1ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo<1ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo<1ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo<1ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo<1ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo<1ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo=12ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo=13ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo<1ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo<1ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo<1ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo<1ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo<1ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo<1ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo<1ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo=1ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo<1ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo<1ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo=49ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo<1ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo<1ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo<1ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo<1ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo<1ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo<1ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo<1ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo=1ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo<1ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo=13ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo=11ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo<1ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo<1ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo<1ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo<1ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo<1ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo<1ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo<1ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo<1ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo=124ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo<1ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo<1ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo<1ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo<1ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo<1ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo<1ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo<1ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo<1ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo<1ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo=8ms TTL=64
Estatísticas do Ping para 192.168.1.1:
Pacotes: Enviados = 3764, Recebidos = 3759, Perdidos = 5 (0% de
perda),
Aproximar um número redondo de vezes em milissegundos:
Mínimo = 0ms, Máximo = 409ms, Média = 6ms
does not seem to work. I also discovered that the v3.0 firmware has JFFS2 support but no matter what I did, I could not mount the jffs partition. Any ideas?