I have slack 13, 184.108.40.206 kernel running on a realtek 81850 (or something) model USB wireless with a belkin54g access point.
At boot time it connects and runs flawlessly after logging in, ping, make http connections, wget stuff, nslookup it all works.
Usually after being up and sometimes after some real heavy traffic (it seems stuff like electricsheep screensaver, video downloads etc cause the connection to get borked...
When it starts failing I can still access all local devices fine ... i can RDP to a local windows box, I can web admin the router at my internel class C address works great. Whois still works for WAN sites, ping, nslookup still works.
But all incoming external wan HTTP connections fail... slashdot.org will not connect
I get the standard, timed out, the server did not respond, you might be firewalled etc...
I have the realtek module configured staticly, and i have iptables modules/netfilter modules, ipv4 and ipv6 mods all compiled but no iptables or firewall configured locally
The routers firewall and NAT is up and enabled with 2 rules for a windows box
This happens even when there's no traffic from the other machines on the network. so there's not allot of connections through the nat/firewall
My slackware box is configured statically to an address outside the routers dhcp servers allocation range
I have a constant DoS attack being logged in the router from an external class A address (whois showed IANA-IP-ARIN or w/e internet backbone people)
Thu Dec 17 23:22:11 2009 1 Blocked by DoS protection 10.113.192.1
Anyway that's pretty constant and I can't see how its causing my http requests to get blocked/fail.
When it stops working every http request it seems fails all over the www..
. slashdot, msn, google, happypenguin.org everyone...
Also I can shutdown and restart the wlan interface on slack and this doesn't fix it, running or restarting dhcpclient on the wlan interface doesn't work either... but restarting the router does fix. A full reboot of slack without restarting the router will not fix.
Wondering if anyone else has encountered the same issue... I think this has sorta happened to the windows box's here too but they sorta fail more gracefully and recover without a restart of the router