iptables -L -vn
Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
183 11421 DROP all -- * * ...
Type: Posts; User: bumper
iptables -L -vn
Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
183 11421 DROP all -- * * ...
If I only forward ports 65530, 65531 and 83, shouldn't those be the only ones that reach my internal machine?
Hi Guys,
I've doublechecked, UPNP is disabled, Internet Firewall is enabled. My DSL modem is configured to send all incoming traffic to the Asus.
I have configured several ports 65530, 65531...
I have not seen this for previous versions, then again, didn't look to hard for it either.
Recently, I have noticed that a lot of traffic is still hitting my software firewall on ports that are...
So far so good, after upgrading to this firmware last thursday, my wan-port hasn't died on my since (it did with prior 1.8 versions once a day on average) If I hit the one week mark (would be record...
Well, the router still dies on me, and even more frequently now it seems compared to the ASUS 1.8 version....
Strangely enough, I can see the router still talking and synching with the NTP server...
For all others who may be struggling out there.
I have had a lot of problems with my WL500G, and it came very very close to being sent back to the vendor. WAN port dying was most frequent but LAN...
never mind, this thing keeps dying on me, either the wan port freezes, or the lan port... it will never stay alive for more then 12 hours. One way ticket for trashcan and no more asus
I used to have this issue too (amongst others) and just upgraded to version 1.8.1.7 hoping my wan port will finally stay up, but is modifying this setting still required in this version? and, if so,...