OpenWrt Forum Archive

Topic: Kamikaze 7.09 and ASUS WL-500g Premium slow/poor connections?

The content of this topic has been archived on 21 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

I recently bought a WL-500g Premium and installed Kamikaze 7.09 (kernel 2.4). From that point on, web connections via wired and wireless were very slow. Firefox would usually eventually connect, but often the status bar would show "Waiting for google.com" or something similar. When connections were eventually made, transfer speed was normal (bandwidth tests didn't show any slowdown), but there seemed to be big problems establishing/maintaining connections. I'm pretty sure my configuration was fine as I've use White Russian quite a bit and, once I figured out the config file system, all settings were the same and I really didn't mess with anything outside of configuring IPs, DHCP, DNS, etc.

I have since reflashed with the latest ASUS firmware and connections are working as they should be. I'm going to try White Russian next as I was previously using that on my WRT54GS with no problems.

Has anybody seen this type of behavior before? I couldn't find any reference to similar problems or known issues with Kamikaze.

I would also appreciate any suggestions on how to troubleshoot the Kamikaze issues. I'm not sure where to even start.

i have the excat same router with no issues .. my wan is static , but even if your useing dhcp you could staticly put your ip's dns in it , may help .. a traceroute from both the router and a connected computer to somthing well knowin ( google.com ) would help to pin down where it's dieing .. also installing tcpdump will give a good deal of info

#### WAN configuration
        config interface        wan
        option ifname   "eth0.1"
        option proto    static
        option ipaddr   66.92.xxx.xxx
        option netmask  255.255.255.0
        option gateway  66.92.xxx.xxx
        option dns      216.254.xxx.xxx

The only time i experienced something like this is when i had set the QoS bandwidth settings way too low smile

The discussion might have continued from here.