Discussion in 'HyperWRT Firmware' started by Avenger20, Jan 8, 2005.
If you find any bugs in 2.0b4, post them here :wink:
can't login to router after a day or two.. need to reboot every time to access it...
Hey there! I just upgraded from b3 to b4, and now using FireFox I get an error message whole trying to use https mode to connect to the admin site:
You have received an invalid certificate. Please contact the server administrator or email correspondant and give them the following information:
Your certificate contains the same serial number as another certificate issued by the certificate authority. Please get a new certificate containing a unique serial number.
P.S. Can't post attachments?
You did a really good job with this firmware.
I have only problems with the
Dyndns - Dynamic IPÂ´s
Because when I enter the Dyndns datas and I want to update the IP, the router still write the 10.0.0.2
I am connecting to the internet via PPTP and the router doesnÂ´t know the right IP Adress. He only knows the IP 10.0.0.2
The firmware from sveasoft alchemy RC 6 can do this correct, but the features from the hyperwrt are better for me. So maybe you can take the correct code from DynDNS from the alchemy to implement it to the hyperwrt firmware.
That would be great.
Please give a short reply if this is in progress or not.
Thx and best regards
P.S. Only a wish from me no bug: A feature for the DHCP would be great that I can give some Mac Adresses a static IP Adress. That was the only good point from my old router (D-Link 604)
Hello, its a very good firmware hack! But I have the problem that in the incoming log is nothing. In the original there was logs when there was incoming traffic. In HyperWRT 2.0b4 not.
In official firmware the incoming logs are broken too. However there is a workaround, see http://www.linksysinfo.org/modules.php?name=Forums&file=viewtopic&t=1878
I created a stratup script which contain single quote charaters ('). The file /tmp/startup.sh is updated, everything is ok. If I reopen the startup script windows from the web interface the single quote characters are replaced by & #39;
If I then save the startup script, the file /tmp/startup.sh is update with the bad characters & #39;
echo -e 'if [ `ps | grep -c kaid` -lt 3 ]; then /tmp/kaid -d -c /tmp/kaid.conf; fi;' >> /tmp/chk_k.sh
becomes after save and reload of the startup script window :
echo -e & #39;if [ `ps | grep -c kaid` -lt 3 ]; then /tmp/kaid -d -c /tmp/kaid.conf; fi;& #39; >> /tmp/chk_k.sh
Same problem, i lost Wifi connectivity after 24/48h ...
go back to 2.03b and no problem
If at all possible I'd like to see the Log fixed in the firmware. I don't want to use any other software added to accomplish Logging.
Just encountered strange bug :
- I changed user password for my PPPoE connection ( WRT54G v1.0 US) to empty (by mistake) and hit "Save" , it gave message that password can't be empty then I entered right password and hit "Save" again .
It loaded only the top (header) of the page and nothing ... freezed
When I rebooted it (by disconnecting the power) all the settings reverted to factory defaults
in the last week i bricked my v2 Router.. no trick works to revive it, no shorting pins... all the things i know and found in the net didnt work.. so i had to use my v1 for the inet-connection until the wrt54gs comes which i bought..
flashed the v1 with the hyperwrt 2.04b, did a hard reset befor and after flash.. following problems occur:
- inet-connection is slow (got a DSL 1024/128 Flat) with certain speedtest-programms only got 50 kb/s and no programs where running
- no way to run emule or other p2p soft.. get connection but no download for about 24h
- to get an ip with pppoe its the same as you play black-jack
.. so i flashed back to hyperwrt 1.4g
and full-inet-speed, emule works.. all is just fine..
Maybe your fixes fÃ¼r the connections (lowering the time, more conns) did not work right on the old v1 models??
btw, great work... keep on patching ;-)
with WRT54G v2 hardware I encountered a bug
-2.0b4 giving me packetloss on certain IP range adresses and I had some time to waste to see the firmware is the cause.
-flashing back to latest official solves the problem
Can't seem to set the MTU mannually?
"DROP" rules in "Port Range Forward"
Two issues... the first is that there is a problem when you untick a ruleset in the "Port Range Forward" screen it turns the ACCEPT rule in to a blanket DROP rule. The issue here is that these rules are parsed before UPnP rules, so that if I have a ruleset to allow audio on MSN (5004-65535) and turn it off when I am not using it, then nothing else can use those ports as they will be blocked.
The seconds seems to be a bug in the above DENY code... say I have a ruleset that allows 11000-11010 for both UDP/TCP to 192.168.1.100, if the rule is ticked then I get:
ACCEPT tcp -- 0.0.0.0/0 192.168.1.100 tcp dpts:11000:11010
ACCEPT udp -- 0.0.0.0/0 192.168.1.100 udp dpts:11000:11010
If the rule is unticked, then this turns into:
DROP tcp -- 192.168.1.100 0.0.0.0/0 tcp spts:11000:11010
DROP udp -- 0.0.0.0/0 192.168.1.100 udp dpts:11000:11010
The TCP rule seems to be backwards... and this is likely to be the result of the first problem I described. I think it would be best to just ignore rules that are not enabled, rather than use FROP rules.
Please summit these bugs to linksys too, as they are most likely in their code base as well.
I am having the same problems. But what I noticed is that the incoming log only recognizes current connections and doesn't save them. One of those "it was there last night" sort of things.
*edit* Whoops skipped over a reply. :lol:
Time setting inconsistency with help
In the Setup > Basic page, the only visible time related setting is the time-zone. The help also mentions a manual or automatic (NTP) time setting.
The HTML source has the time setting, but there is an HTML syntax error making it invisible for IE. (... </TR--> ...).
FireFox doesn't want to show the router page at all due to the certificate issue :-( (somehow this is fixed. FireFox also doesn't show the time setting)
This might also be an issue in the official Linksys firmware, but I'm not downgrading just to check.
Fred Jan Kraan