Knock, KnockWhos there? Port Knock! | NetworkWorld.com Community:: to the server, but the service port is closed and the service isnt even running. specific packet sequences, for both opening and closing ports, and remotely http://www.networkworld.com/community/node/25907HOME | 20:40:12 SYSTEM TCP 80.55.167.123 1157 Packet for closed port
20:40:11 SYSTEM UDP 217.232.29.79 4672 Packet for closed
20:40:07 SYSTEM TCP 212.122.213.45 4810 Packet for closed
20:40:06 SYSTEM TCP 212.235.31.34 2852 Packet for closed
20:40:03 SYSTEM TCP 217.132.192.178 3440 Packet for closed
20:40:03 SYSTEM TCP 80.42.117.123 4604 Pakket voor gesloten poort
20:40:03 SYSTEM UDP 80.42.117.123 4672 Pakket voor gesloten poort
20:40:02 SYSTEM TCP 80.53.157.130 3425 Pakket voor gesloten poort Go4Expert - How does Portscanning works?:: port was closed and not behind a firewall the answer would be a RA packet insted. If the port was open or closed it will always respond to a SYN packet. http://www.go4expert.com/forums/printthread.php?t=75HOME |
20:39:59 SYSTEM TCP 81.178.75.71 4802 Pakket voor gesloten poort
20:39:59 SYSTEM UDP 81.178.75.71 4672 Pakket voor gesloten poort
20:39:58 SYSTEM TCP 61.80.226.37 4916 Pakket voor gesloten poort
20:39:55 SYSTEM IGMP 24.132.0.1 0 IP protocol Rule #1
20:39:55 SYSTEM TCP 81.193.19.51 3991 Pakket voor gesloten poort
20:39:53 SYSTEM TCP 212.160.152.35 3906 Pakket voor gesloten poort
20:39:50 SYSTEM TCP 80.178.197.201 3302 Pakket voor gesloten poort
20:39:43 SYSTEM TCP 80.139.189.205 1104 Pakket voor gesloten poort
20:39:42 SYSTEM UDP 83.26.250.155 32797 Pakket voor gesloten poort
20:39:37 SYSTEM TCP 81.101.32.120 1721 Pakket voor gesloten poort
20:39:30 SYSTEM UDP 81.218.46.158 5672 Pakket voor gesloten poort &ZoneAlarm & DSL - Stealth problem? • mozillaZine Forums:: ran a test at Sheilds up and for some reason it only shows my ports as closed if something has dropped the packet, there must be a port there. http://forums.mozillazine.org/viewtopic.php?t=412269HOME | Port Knocking:: When the UDP listener receives a packet it likes, it instructs the firewall to The whole reason for doing this is to keep your ports closed until needed. reply http://www.linuxjournal.com/article.php?sid=6811HOME |
20:39:29 SYSTEM UDP 212.235.124.220 5783 Pakket voor gesloten poort SANS Institute - Intrusion Detection FAQ: How can passive techniques be :: SANS Institute, offering computer security training for system administrators, computer security professionals, and and a UDP packet to a closed port. http://www.sans.org/resources/idfaq/passive_vuln.phpHOME |
20:39:27 SYSTEM UDP 80.230.67.120 5672 Pakket voor gesloten poort
20:39:25 SYSTEM TCP 217.42.232.79 3189 Pakket voor gesloten poort
20:39:22 SYSTEM TCP 212.235.31.34 2259 Pakket voor gesloten poort
20:39:22 SYSTEM TCP 80.139.189.205 1104 Pakket voor gesloten poort
20:39:21 SYSTEM TCP 80.5.219.20 2882 Pakket voor gesloten poort
20:39:20 SYSTEM TCP 67.124.91.91 3590 Pakket voor gesloten poort
20:39:19 SYSTEM TCP 217.132.192.178 3413 Pakket voor gesloten poort
20:39:18 SYSTEM UDP 213.8.160.55 4672 Pakket voor gesloten poort
As you prob. understand, "pakket voor gesloten poort" means Packet for closed port.
What is all this about? This is just a snippet from the log-viewer blocked today. If I would copy/paste the complete list it would be way to big !
please explain.
As the reason suggests, Outpost is blocking data for network connections that have been closed by the application involved. To get full details you need to show the traffic direction and local port (right-click on the log window, select Columns... and check the boxes for these 2 items).
The most likely explanation is that you are running a P2P application which means that others will be connecting to your PC continuously. If you shut down that application the connection attempts will continue (others on the network have no way of knowing you have shut it down) and these can persist for days or weeks.
If you are not, but use dial-up Internet access, then you may have been allocated an IP address used by someone else running P2P - which means you are getting all their access requests also. There is nothing you can do to stop this (although disconnecting and reconnecting may get you another IP address without so much traffic) - just rely on Outpost to block them all.
Please see the 1 FAQ for more details on ports and the 1 FAQ for information on how Outpost handles network traffic.
Red Hat's Rough Recovery From CFO Exit
Windows Live Finds a New, Pre-installed Home
|