scorz nuclearcat wrotebad checksum in wireshark, for tx, IMO only wireshark glitch and not source of issue, as soon as u can open from computer router web-interface or other local resources @nuclearcat Can it be a NAT issue then?
nuclearcat It is difficult to say, it depends on router. I know how this routers made, and how crap software are inside. Hardware is OEM, so sometimes, if they are enough opensource - u can flash openwrt and you can be sure it is at least software part is good, and troubleshooting hardware problems are easier. hussam, can you tell me full name of router? model, revision, etc
hussam 192.168.1.1 says: Firmware Version: 4.7.13 Build 101203 Rel.42256n Hardware Version: WR541G/542G v7 081540EF the router says: 54M wireless router TL-WR542G tp-link
hussam pci card: driver: 8139too version: 0.9.28 firmware-version: bus-info: 0000:02:05.0 supports-statistics: yes supports-test: no supports-eeprom-access: no supports-register-dump: yes supports-priv-flags: no btw, turning off tcp checksumming on onboard card didn't help..
hussam ok, I bought a realtek USB wireless adapter. it drops pings a lot but it will allow me to test if this is an interface problem or a router problem. I will know 26 hours from now
scorz btw, turning off tcp checksumming on onboard card didn't help.. I guess we were on the wrong track then. As nuclearcat said, router's firmware sucks. I have openwrt/ddwrt on all my routers.
hussam ok, my sister's laptop has been on the router for over 31 hours without a problem. USB wireless adapter connection on my computer stopped working after 31 hours. so it's not completely a router problem...