Recent content by SN_

Blocking was working fine for me but after less than 1 day adsuck stopped to functioning properly. Got also the 'can't convert wire packet to struct' messages. Not listening to /etc/resolv.conf as it should and throwing error messages after such a short time. I gave up from adsuck...

I had the same problem to get adsuck running and found the following solution: Creating '/jffs/configs/dnsmasq.conf.add' with content: no-resolv server=127.0.0.1#65053 and in /jffs/scripts adding a file 'wan-start' with content: #!/bin/sh # send SIGHUP to adsuck to reread...

Cant reproduce the issue. After downgrading, making a hard reset, uploading configuration and upgrading to beta6-sdk5 again everything runs fine now.

Here an interesting observation with 33_beta6-sdk5 that may help to track down the low txpower problems: With this beta i do have the same drop in txpower for 2.4GHz as with sdk6 based FW. Setting txpower is not possible at all and everything related to txpower seems to have the same...

I always do a hard reset.

Well, i moved staight back to 33 beta 1 without a need to do a nvram reset. Just uploaded the old config file and signal strength was back to normal.

Sorting out all the different feedback regarding tx power, it looks to me like a typical problem of an uninitialized pointer. Without having access to the technical documentation there is no way to fix it and also no way to find out whom to blame. Maybe ASUS does not properly initialize the...

Slowly, slowly ;) I think we do refer to two different problems. The one i observed is related to 3.0.0.4.374.33_beta3-sdk5 only. With 3.0.0.4.374.33_beta3b i noticed a different problem: Setting 20/40Mhz mode is switching to auto channel. No real problem for me as i dont use that mode.

At least my router seems to be less stubborn than yours as it went back to normal tx power with country setting US while yours does not care for country settings at all ;) Regarding the drop in signal strength our routers seem to be in the same range. Mine dropped level by 10 to 12dB...

That was with 3.0.0.4.374.33_beta3-sdk5 right? i had the same problem. The Wlan web page returned immediately without changing any value. I downloaded the source archive and tried to make my own build but the src archive is also broken. Several files in kernel sub folders are missing. So i...

As said in a previous post, 'wl -i eth1 country "US"' did all the magic on its own. I did not enter any other commands. But the default country of my device is EU maybe thats the reason. BTW, with SDK6 'wl -i eth1 txpwr1 XX' is a NOP and totally useless.

I wonder where this difference comes from. Thought the country default settings are part of the bootloader and not of the FW... strange but maybe a hint for the experts. I am using similar settings for 2.4GHz like you. BTW my previous router was also a WRT54GL. A rock solid device. Had never...

You are located in Netherlands and there is only a slight decrease in 2.4GHz signal strenght? Wow i am confused now ;) What does the command 'wl country' report on your router? Mine returns 'EU (EU/3) EUROPEAN UNION'. BTW I have tried setting country to EU, DE, FR, RU and even CA without...

Sure, thats why i dont use it and switched back to 33b1. Anyway my point on this was a different one. With SDK6 changing the country region immediately changed tx power and is so far the only way i found out to change it. On the other hand with SDK5 it changes only the limit but does not...

Forgot to mention, "wl -i eth2 txpwrlimit" was before and after the command "1 mW (0.0 dBm)". This should make clear that txpwrlimit is irrelevant with SDK6.