Simple to know, the American versions in the 5Ghz band have the 149,157 channels and they have a power of 30db. In the European version in the 5Ghz band there are no such channels, only goes to channel 140 in the original firmware. If you are using Davic502 firmware see the transmission power on channel 149 if is 13db is the router is the European version. Now if you are at 30db, then you are fortunate to own a router in the European version. lol
1 Like
That's when I bought on eBay I found that the router was defective by the low wireless signal transmission power at 2.4 and 5GHz. But searching the forums I found that the wrt3200acm had two variants European and American. I saw that in Europe there are restrictions on the propagation of signals. But after much research frustrated me because this limitation of signal strength is recorded in eeprom memory and not in firmware. Then I got upset and bought another but the American version. The coverage of the wifi is much better the American by the signal strength ... I live in Brazil but I found out of this signal irradiation policy in Europe. I even tried to return the router to the seller on eBay, but he declined. EBay didn't help me at all ...
In theory the issues currently happening are not complete show stoppers, most have been fixed with a Browser cache clean however the 404 Error reported by @Krazta is pointing the issue to the theme, I also have just tested this and confirm that the issue is with only my theme.
Its doing something funky with links.
Once i have done my compile of 19.07 i will go looking on the master branch (Which hasn't been compiling because of issues related to luaposix).
If you wish to keep it the default theme i don't mind, just don't want your Thread being bombarded with this that and the other not working with this theme.
1 Like
My issue is that the 5ghz keeps failing. Some of the archived forms say that this happens due to open wrt having a mixture of regulatory zones and hitting dts channels which drops tx to 13db or kills the 5ghz altogether, which is what I'm getting. I want to set the US regulatory zone through the eeprom to avoid all this trouble and fix the poor range. I realise that it's not a bug and due to eu regs but I can't seriously see someone knocking on my door because I reprogram an eeprom for slightly better WiFi. You can buy a us wrt32x from the US amazon and get it shipped to the UK.
It isn't defective, it's working according to the legal limits in Europe (if you aren't living in Europe, but a FCC region instead, it should have never been sold to you); no other device would be allowed to exceed these limits if sold in Europe either[0].
--
[0] slightly simplified, as there is a difference between "merely selling/ buying" (which is technically legal) and "operating" (which certainly is not and is prosecuted) a non-compliant device from a legal point of view. Buyers of non-compliant devices have been visited by the regulatory bodies/ law enforcement in the past, to ensure that they aren't going to operate the affected devices in Europe (legal to own, illegal to use).
(Complains) Says there is a dependency of lua-bit32, but it does exist, so I don't know what's going on there.
Appreciate the feedback... I'm going to keep your theme like it is. Not going to build again until this Saturday, so that does give more time as well.
Thanks,
David
1 Like
Yep that's the error, it kills the whole compile of even the toolkit.
Will have a look after my 19.07 compile. It might be a good time to base from scratch the theme I think 
that way two 
's with one stone.
Will level the repo for theme as is and just use Dev for patching and another branch for basing.
Edit: Right so i uninstalled the atmaterial theme and then installed it from the software section and the Error 404 has gone.
Edit 2: I comes back to haunt me that error 404.
Edit: I have found the troubles of the UCI changes error 404, going to update the github now
Now i have to find away to fix it.
@davidc502 can you confirm the repo you use is the master branch or dev branch?
@Krazta can you please clear your caches and confirm the issue is still present after please as well.
also try in ssh
uci set luci.ccache.enable=0
uci commit lucifollowed by
rm /tmp/.luci-indexcacheThen close the browser and re-open it and see if the issue is still there.
Another edit: I think I managed to fix error 404 bug and it's on the master branch.
1 Like
In terminal type:
strings /dev/mtd3|sed -ne 's/^cert_region=//p'
2 Likes
Well, I thought I had two sources listed in feeds, but this is what I have right now.
# Solidus Theme
src-git atmeterial git://github.com/solidus1983/luci-theme-atmaterial.git
1 Like
That is the correct one, that should default to master.
The one your possibly thinking of is luci-theme-linksysmaterial which is basically luci-theme-atmaterial but without the OpenWRT logo and has the Linksys "Router Model" which i will sort once i have the main luci-theme-atmaterial theme sorted as they share the same code base.
1 Like
Typically the eeprom is write once protected by an eFuse. I sincerely doubt it is rewritable.
I am looking to buy the wrt32x model but wanted to understand why it costs cheaper than the wrt3200acm model? Both have the same hardware and the same specifications. Could anyone answer?
There's no real difference other than wrt32x is all black, has a different NAND partition setup and has different firmware with killer prioritasion (QoS). The partitioning is really the only important difference between the two if you intend to use custom firmware as they require different firmware images.
Thanks. I'm sure there must be a way though even if it means buying a chip and replacing it. If you can read the chip there must be a way to write a dump of an American eeprom. Maybe I'm just naive though as allot of cleaver people have tried and failed to work it out.
Replacing the chip is probably the only way, but who knows if it would work.
eFuse's are designed to be permanent. They literally burn out the circuit required to write to the chip.
Not to be rude or abrupt, but if you're asking these questions you aren't qualified to take it on.
How do you disable DNS Crypt correctly in your build?
I have disabled DNS Crypt by disabling the service and adding option resolvfile '/tmp/resolv.conf.auto' to the DHCP config file. This seemed to fix my only issue I had. I couldn't see the add videos in a game to get more time in a game. I know, stupid, but if things don't work it drives me mad haha.
When I tested it doing that same game on my cell service, it constantly worked and now it seems to work again with seemingly having disabled DNS Crypt correctly, but checking this: https://oldwiki.archive.openwrt.org/inbox/dnscrypt there should be more options to be changed than I did. Hence my question on how to disable it correctly and have a good working router.
Not rude at all. It's 100% correct. I thought that someone here would be able to explain why it's not possible, or point me in the right direction. Looks like it's not possible though, at least at the moment. Thanks for the info
WLAN LED support appears to be broken for Rango.
echo anything from the list of /sys/class/leds/rango:white:wlan_2g/triggers to triggers cause spam of following events in syslog\dmesg and 2g dies until reboot.
Mon Aug 19 23:29:07 2019 kern.err kernel: [ 581.848409] ieee80211 phy1: buffer is NULL for tx done ring
Mon Aug 19 23:29:07 2019 kern.err kernel: [ 581.927693] ieee80211 phy1: adapter does not exist
I just wanted to turn of (or on) wlan 2g and 5g leds since they are blinking too fast an cause noise in nearby speakers.
A little history here... The line of questioning (discussions) and actions taken by the opensource community (In the past) to over-ride the default behavior of Wifi by taking it out of specification (defined by regulation) as well as European specifications is why these routers were locked down to begin with. When the FCC mandated router/switch manufactures lock down the firmware is why some left the opensource community completely. It was a blow to OpenWrt.
My recommendation would be to look at alternative methods of extending rang that are legal. Otherwise continued actions to bypass regulations put the entire project at risk. Other projects too.
I'm not trying to be a jerk here, so please don't take it that way. It is just that the FCC, in the US for example, takes things like this very very seriously, and if observed, will shut it down no questions asked. As someone who has and maintains a FCC license, I studied for that certification, and can tell you the FCC doesn't mess around, and it sounds to me like the European counterpart to the FCC doesn't mess around either.
Once again, please keep it legal and play by the rules we all have to play by. If not for your sake then to OpenWrt and Opensource projects like these.
Best Regards,
David
11 Likes
I am trying to replace a theme, and there is no change.
I cleaned up Cash, another browser, nothing.