[Fork] Asuswrt-Merlin 374.43 LTS releases (Archive)

[RMerlin]

I have read that after January 01, 2015, the FCC will not allow the use of 802.11d.

This is for the client side however. It doesn't prevent routers from still broadcasting the actual information.

 

[ualdrivr]

More than a few are having problems with IOS 8.1 and disconnects. See this thread http://forums.smallnetbuilder.com/showthread.php?t=20497



One thing that has seemed to help is to set Regulatory mode to 802.11d+h on the Wireless/Professional tab (the default is Off).

Thank you John, the issue I'm having is random reboots, not disconnects. When the phone is on the Network, it stays with it just fine. It just randomly reboots. Today I'm all day in and out different WiFi places in Zurich Switzerland and the phone has been on all the time, no reboots. It just baffles me.

 

[john9527]

Thank you John, the issue I'm having is random reboots, not disconnects. When the phone is on the Network, it stays with it just fine. It just randomly reboots. Today I'm all day in and out different WiFi places in Zurich Switzerland and the phone has been on all the time, no reboots. It just baffles me.

I haven't heard about any reboot issues related to iPhones, but let's see if we can see what is happening. This is a case where the /jffs copy of the syslog may help out. If you have jffs enabled (and have not used the custom nvram switch to disable the copy), there will be two syslog files in the /jffs directory. Next time you see a reboot you can look at those to see if there are any hints as to what caused the reboot.

 

[Muyfa666]

For one and foremost many many security fixes. SDK5 has not been used in quite some time. Bottom line SDK5 did offer excellent signal output but is just not safe to run any longer.

I was under the impression that this fork had backported many security fixes from the new build. Did I misunderstand this?

Does this fork have security issues compared to the new version?

 

[L&LD]

I was under the impression that this fork had backported many security fixes from the new build. Did I misunderstand this?

Does this fork have security issues compared to the new version?

Yes, you're not understanding what was written.

Compared to the latest 376.48.1 (or 48.2 for the N16 router) this fork is as secure as possible, considering the build date.

And much, much more secure than the last official Asus or RMerlin SDK5 based versions.

 

[Muyfa666]

Great. Then I can use any of them. Gonna try the fork I think...

 

[L&LD]

Great. Then I can use any of them. Gonna try the fork I think...

Any of them???

I would also try the latest RMerlin 376.48.1 firmware too. Seems the 'slow' bugs have been ironed out by an order of magnitude since the buggy .46/.47 series were introduced.

 

[Muyfa666]

I am running .48 and so far it's good.

 

[john9527]

L&LD got in before me to answer

What this fork picks up....

Obvious security updates like OpenSSL and the change to remove SSL support for the webui. Also tries to stay relatively current on the supporting modules, such as dropbear just in case.

What the fork doesn't pick up....

Security related items that may be buried in the 'big merges' that Merlin does from ASUS. Flip side of this is that it also doesn't pick up regressions that may occur in the later builds (either security or function related).

 

[reggie14]

Do you know what the status of this build is regarding the media bridge bug? That is, when you configure one device as a media bridge on the 5Ghz radio, the 2.4ghz radio *might* keep broadcasting as an AP.

The newest Merlin builds have this bug, which is really bad if you set up a new device without realizing bug is there. You can easily set up a open wifi AP to your network by accident!

Using your build, I don't see my old SSID. However, using XIRRUS Wi-fi Inspector I do see two hidden APs in the 2.4 GHz band (I have two devices serving as media bridges). They're low power, but there. It really looks like they're coming from my media bridges, although I can't seem to connect to them from any of my devices (at least).

Still, I worry there's a backdoor that some moderately-capable script kiddy could exploit.

Edit: Something is definitely going on. When I shut down one of my media bridges I immediately saw one of the hidden APs disappear. There's almost certainly something transmitting out on the 2.4Ghz radio.

 

[john9527]

Nothing was touched in any of the fork releases that would affect Bridge mode...it is what it was back on the original release.

If you are in a mood to experiment, you might try....

nvram set wl0_radio=0
nvram commit && reboot

This should tell the code to disable the 2.4GHz radio (to set it back to the default, set the value to 1).

 

[hki]

Compared to the latest 376.48.1 (or 48.2 for the N16 router) this fork is as secure as possible, considering the build date.

And much, much more secure than the last official Asus or RMerlin SDK5 based versions.

I am wondering if the above conclusion is correct also when the web gui and ssh/telnet ports are not exposed to WAN and the router does not offer any advanced services as VPN server, etc over WAN connection? Also any ports that are open are redirected to devices in the LAN.

I probably do not know enough about routers and hacking, but it seems to me that if the router does not allow authentication over WAN ports (or has these handled by devices on LAN (e.g.. Synology NAS in my case, that is regularly updated)) there is no substantial risk.

I am currently running the latest fork by John and I am happy with the performance so this is really a hypothetical question.

 

[bluepoint]

Seems the 'slow' bugs have been ironed out by an order of magnitude since the buggy .46/.47 series were introduced.

What slow bugs that was ironed out in Merlin's .46/.47? AFAIK N66U didn't have bugs with Merlin's firmware.

 

[Deleted member 22229]

What slow bugs that was ironed out in Merlin's .46/.47? AFAIK N66U didn't have bugs with Merlin's firmware.

Well with the N66U the 376.xxx builds sure did have a reduction in signal output. No fault of Merlin but Asus them self.

 

[bluepoint]

But that's not what L&LD is saying. All sdk6 non em has the same strength that's why I'm wondering what he's talking about.

 

[Deleted member 22229]

But that's not what L&LD is saying. All sdk6 non em has the same strength that's why I'm wondering what he's talking about.

From what i have read this has nothing to do with EM builds, asus has lowered the output in there new versions to comply with up coming FCC regulations.

 

[bluepoint]

From what i have read this has nothing to do with EM builds, asus has lowered the output in there new versions to comply with up coming FCC regulations.

I'm not sure what you're saying is true. They lowered the output long time ago from sdk5 to sdk6. It didn't happen lately, what they did is removed the ability to change zones after .43.

 

[Deleted member 22229]

I'm not sure what you're saying is true. They lowered the output long time ago from sdk5 to sdk6. It didn't happen lately, what they did is removed the ability to change zones after .43.

You see the new firmware now has no numerical adjustment just a slider. 100% = 80mw that is a reduction.

If i am incorrect about this i am sorry but thats what i have been reading. Also in my testing with the new 376 builds confirms there is a reduction in output with the N66U.

Maybe Merlin or John may have more accurate information on this and will post to confirm.

 

[bluepoint]

You see the new firmware now has no numerical adjustment just a slider. 100% = 80mw that is a reduction.

That's only what we are seeing visibly but the firmware has been dynamically limiting the output depending on where you are.

If i am incorrect about this i am sorry but thats what i have been reading. Also in my testing with the new 376 builds confirms there is a reduction in output with the N66U.

There is now reduction in output because the EM mode was removed.

Maybe Merlin or John may have more accurate information on this and will post to confirm.

That will be good.

 

[shobhitk]

Hi,
i have switched from merlin's 376.48_1 to fork's latest Update-05. do i need to do a factory reset and redo all the settings manually again? or can i keep my original custom settings intact?


Thanks