[/quote]Originally posted by St0le@Jan 8 2006, 10:10 PM
blocked ports?? ur kidding me...
btw if u really gonna talk to the GM (or Something)...nah! too easy! 😛
[snapback]38638[/snapback]
[/quote]Originally posted by St0le@Jan 9 2006, 09:39 PM
oh! yeah i forgoot about his thread...
dood u jjust scanned the gateway ports...AFAIK they are not supposed to be open...the ports are not blocked...they are closed!
MTNL DOEs not Block Anything!
[snapback]38714[/snapback]
[/quote]Originally posted by max@Jan 9 2006, 09:18 PM
The ports you have scanned aren't anyway blocked by the firewall...Anyway they will show as open if something is actually running on those ports.
[snapback]38703[/snapback]
[/quote]Originally posted by St0le@Jan 9 2006, 11:20 AM
but thats the gateway? isnt it?
u know someting about firmwares? pl help
[snapback]38668[/snapback]
[/quote]Originally posted by max@Jan 11 2006, 12:22 AM
eh? aren't closed ports and blocked ports the same thing?
[snapback]38858[/snapback]
Originally posted by max@Jan 11 2006, 12:22 AM
eh? aren't closed ports and blocked ports the same thing? Check your router settings once again. These cheap routers dont always obey all the commands in the GUI. Even though you have opened/ forwarded those ports to the internal network the IPtables rules might not have been setup correctly...
[/quote]Originally posted by max@Jan 12 2006, 08:54 PM
Netfreak, thanks for the info. I am quite familiar with TCP/IP specs. There seems to be some confusion.
So for me, blocked ports or closed ports mean the same.
dowgMac,
> Secondly if you note I am using a commandline scanner (nmap). Goog it.
How does that make any difference? A GUI or CLI scanner will report the same results. May I know what kind of scan did you run? I usually use this:
nmap -P0 -O -v
Also, instead of using TCPDump, use Ethereal. It has much more functionality than TCPDump.
[snapback]38997[/snapback]