1. Home
  2. Networking Firewalls
  3. Software Firewall
  4. Page 2

Software Firewall

2000-01-01 00:00:05 - NETGEAR activated Sat, 2000-01-01 00:00:05 - Send out NTP Request to 129.6.15.28 Sat, 2000-01-01 00:00:05 - Receive NTP Reply from 129.6.15.28 Mon, 2006-02-27 19:26:08 - NETGEAR activated Mon, 2006-02-27 19:26:08 - WAN gets IP address:68.196.84.52 Mon, 2006-02-27 19:26:08 - Send out NTP Request to 129.6.15.28 Mon, 2006-02-27 19:26:08 - Receive NTP Reply from 129.6.15.28 Mon, 2006-02-27 19:26:08 - NETGEAR get Time from Internet Mon, 2006-02-27 19:27:04 - UDP packet - Source:192.168.0.2,1026 ,LAN - Destination:167.206.245.19,53[DNS] ,WAN [Forward] - [Outbound Default rule match] Mon, 2006-02-27 19:27:13 - TCP packet - Source:192.168.0.2,1028 ,LAN - Destination:63.111.24.62,80[HTTP] ,WAN [Forward] - [Outbound Default rule match] Mon, 2006-02-27 19:27:13 - TCP packet - Source:192.168.0.2,1029 ,LAN - Destination:63.111.24.62,80[HTTP] ,WAN [Forward] - [Outbound Default rule match] Mon, 2006-02-27 19:27:30 - TCP packet - Source:192.168.0.2,1030 ,LAN - Destination:63.111.66.14,80[HTTP] ,WAN [Forward] - [Outbound Default rule match] Mon, 2006-02-27 19:27:47 - UDP packet - Source:192.168.0.2,1042 ,LAN - Destination:167.206.245.19,53[DNS] ,WAN [Forward] - [Outbound Default rule match] Mon, 2006-02-27 19:27:47 - TCP packet - Source:192.168.0.2,1043 ,LAN - Destination:63.111.24.21,80[HTTP] ,WAN [Forward] - [Outbound Default rule match] Mon, 2006-02-27 19:27:47 - TCP packet - Source:192.168.0.2,1044 ,LAN - Destination:208.45.133.133,80[HTTP] ,WAN [Forward] - [Outbound Default rule match] Mon, 2006-02-27 19:27:48 - TCP packet - Source:192.168.0.2,1045 ,LAN - Destination:208.45.133.152,80[HTTP] ,WAN [Forward] - [Outbound Default rule match] Mon, 2006-02-27 19:27:48 - TCP packet - Source:192.168.0.2,1046 ,LAN - Destination:208.45.133.139,80[HTTP] ,WAN [Forward] - [Outbound Default rule match] Mon, 2006-02-27 19:27:48 - TCP packet - Source:192.168.0.2,1047 ,LAN - Destination:208.45.133.133,80[HTTP] ,WAN [Forward] - [Outbound Default rule match] Mon, 2006-02-27 19:27:49 - TCP packet - Source:192.168.0.2,1048 ,LAN - Destination:63.111.24.53,80[HTTP] ,WAN [Forward] - [Outbound Default rule match] Mon, 2006-02-27 19:27:51 - TCP packet - Source:192.168.0.2,1049 ,LAN - Destination:63.236.66.25,80[HTTP] ,WAN [Forward] - [Outbound Default rule match] Mon, 2006-02-27 19:27:51 - TCP packet - Source:192.168.0.2,1050 ,LAN - Destination:208.45.133.152,80[HTTP] ,WAN [Forward] - [Outbound Default rule match] Mon, 2006-02-27 19:27:51 - TCP packet - Source:192.168.0.2,1051 ,LAN - Destination:208.45.133.139,80[HTTP] ,WAN [Forward] - [Outbound Default rule match] Mon, 2006-02-27 19:27:52 - TCP packet - Source:192.168.0.2,1052 ,LAN - Destination:64.233.161.99,80[HTTP] ,WAN [Forward] - [Outbound Default rule match] Mon, 2006-02-27 19:27:52 - TCP packet - Source:192.168.0.2,1053 ,LAN - Destination:208.45.133.132,80[HTTP] ,WAN [Forward] - [Outbound Default rule match] Mon, 2006-02-27 19:27:52 - TCP packet - Source:192.168.0.2,1054 ,LAN - Destination:208.45.133.132,80[HTTP] ,WAN [Forward] - [Outbound Default rule match] Mon, 2006-02-27 19:27:58 - TCP packet - Source:192.168.0.2,1055 ,LAN - Destination:132.163.4.102,13 ,WAN [Forward] - [Outbound Default rule match] Mon, 2006-02-27 19:28:03 - TCP packet - Source:192.168.0.2,1056 ,LAN - Destination:192.168.1.1,80[HTTP] ,WAN [Forward] - [Outbound Default rule match] Mon, 2006-02-27 19:29:06 - TCP packet - Source:192.168.0.2,1106 ,LAN - Destination:208.45.133.133,80[HTTP] ,WAN [Forward] - [Outbound Default rule match] Mon, 2006-02-27 19:29:06 - TCP packet - Source:192.168.0.2,1107 ,LAN - Destination:208.45.133.152,80[HTTP] ,WAN [Forward] - [Outbound Default rule match] Mon, 2006-02-27 19:29:06 - TCP packet - Source:192.168.0.2,1108 ,LAN - Destination:208.45.133.139,80[HTTP] ,WAN [Forward] - [Outbound Default rule match] Mon, 2006-02-27 19:29:06 - TCP packet - Source:192.168.0.2,1109 ,LAN - Destination:208.45.133.133,80[HTTP] ,WAN [Forward] - [Outbound Default rule match] Mon, 2006-02-27 19:29:06 - TCP packet - Source:192.168.0.2,1110 ,LAN - Destination:63.236.66.25,80[HTTP] ,WAN [Forward] - [Outbound Default rule match] Mon, 2006-02-27 19:29:06 - TCP packet - Source:192.168.0.2,1111 ,LAN - Destination:208.45.133.152,80[HTTP] ,WAN [Forward] - [Outbound Default rule match] Mon, 2006-02-27 19:29:06 - TCP packet - Source:192.168.0.2,1112 ,LAN - Destination:208.45.133.139,80[HTTP] ,WAN [Forward] - [Outbound Default rule match] Mon, 2006-02-27 19:29:06 - TCP packet - Source:192.168.0.2,1113 ,LAN - Destination:64.233.161.99,80[HTTP] ,WAN [Forward] - [Outbound Default rule match] Mon, 2006-02-27 19:29:06 - TCP packet - Source:192.168.0.2,1114 ,LAN - Destination:208.45.133.132,80[HTTP] ,WAN [Forward] - [Outbound Default rule match] Mon, 2006-02-27 19:29:07 - TCP packet - Source:192.168.0.2,1115 ,LAN - Destination:208.45.133.132,80[HTTP] ,WAN [Forward] - [Outbound Default rule match] Mon, 2006-02-27 19:29:16 - TCP packet - Source:192.168.0.2,1116 ,LAN - Destination:12.7.210.242,80[HTTP] ,WAN [Forward] - [Outbound Default rule match] Mon, 2006-02-27 19:29:16 - TCP packet - Source:192.168.0.2,1117 ,LAN - Destination:12.7.210.242,80[HTTP] ,WAN [Forward] - [Outbound Default rule match] Mon, 2006-02-27 19:29:17 - TCP packet - Source:192.168.0.2,1118 ,LAN - Destination:216.239.37.104,80[HTTP] ,WAN [Forward] - [Outbound Default rule match] Mon, 2006-02-27 19:29:24 - TCP packet - Source:192.168.0.2,1119 ,LAN - Destination:12.7.210.241,80[HTTP] ,WAN [Forward] - [Outbound Default rule match] Mon, 2006-02-27 19:29:24 - TCP packet - Source:192.168.0.2,1120 ,LAN - Destination:12.7.210.241,80[HTTP] ,WAN [Forward] - [Outbound Default rule match] Mon, 2006-02-27 19:30:03 - TCP packet - Source:192.168.0.2,1121 ,LAN - Destination:12.7.210.243,21[FTP Control] ,WAN [Forward] - [Outbound Default rule match] Mon, 2006-02-27 19:30:26 - TCP packet - Source:192.168.0.2,1132 ,LAN - Destination:208.45.133.133,80[HTTP] ,WAN [Forward] - [Outbound Default rule match] Mon, 2006-02-27 19:30:26 - TCP packet - Source:192.168.0.2,1133 ,LAN - Destination:208.45.133.152,80[HTTP] ,WAN [Forward] - [Outbound Default rule match] Mon, 2006-02-27 19:30:26 - TCP packet - Source:192.168.0.2,1134 ,LAN - Destination:208.45.133.139,80[HTTP] ,WAN [Forward] - [Outbound Default rule match] Mon, 2006-02-27 19:30:26 - TCP packet - Source:192.168.0.2,1135 ,LAN - Destination:208.45.133.133,80[HTTP] ,WAN [Forward] - [Outbound Default rule match] Mon, 2006-02-27 19:30:27 - TCP packet - Source:192.168.0.2,1136 ,LAN - Destination:63.236.66.25,80[HTTP] ,WAN [Forward] - [Outbound Default rule match] Mon, 2006-02-27 19:30:27 - TCP packet - Source:192.168.0.2,1137 ,LAN - Destination:208.45.133.152,80[HTTP] ,WAN [Forward] - [Outbound Default rule match] Mon, 2006-02-27 19:30:27 - TCP packet - Source:192.168.0.2,1138 ,LAN - Destination:208.45.133.139,80[HTTP] ,WAN [Forward] - [Outbound Default rule match] Mon, 2006-02-27 19:30:27 - TCP packet - Source:192.168.0.2,1139 ,LAN - Destination:64.233.161.104,80[HTTP] ,WAN [Forward] - [Outbound Default rule match] Mon, 2006-02-27 19:30:27 - TCP packet - Source:192.168.0.2,1140 ,LAN - Destination:208.45.133.132,80[HTTP] ,WAN [Forward] - [Outbound Default rule match] Mon, 2006-02-27 19:30:27 - TCP packet - Source:192.168.0.2,1141 ,LAN - Destination:208.45.133.132,80[HTTP] ,WAN [Forward] - [Outbound Default rule match] Mon, 2006-02-27 19:30:39 - TCP packet - Source:192.168.0.2,1142 ,LAN - Destination:69.17.117.156,80[HTTP] ,WAN [Forward] - [Outbound Default rule match] Mon, 2006-02-27 19:30:40 - TCP packet - Source:192.168.0.2,1143 ,LAN - Destination:69.17.117.156,80[HTTP] ,WAN [Forward] - [Outbound Default rule match] Mon, 2006-02-27 19:30:43 - TCP packet - Source:192.168.0.2,1144 ,LAN - Destination:69.17.117.156,80[HTTP] ,WAN [Forward] - [Outbound Default rule match] Mon, 2006-02-27 19:30:43 - TCP packet - Source:192.168.0.2,1145 ,LAN - Destination:64.154.80.132,80[HTTP] ,WAN [Forward] - [Outbound Default rule match] Mon, 2006-02-27 19:30:45 - TCP packet - Source:192.168.0.2,1146 ,LAN - Destination:216.254.95.2,80[HTTP] ,WAN [Forward] - [Outbound Default rule match] Mon, 2006-02-27 19:30:51 - TCP packet - Source:192.168.0.2,1147 ,LAN - Destination:208.45.133.139,80[HTTP] ,WAN [Forward] - [Outbound Default rule match] Mon, 2006-02-27 19:30:51 - TCP packet - Source:192.168.0.2,1148 ,LAN - Destination:208.45.133.133,80[HTTP] ,WAN [Forward] - [Outbound Default rule match] Mon, 2006-02-27 19:30:51 - TCP packet - Source:192.168.0.2,1149 ,LAN - Destination:63.236.66.25,80[HTTP] ,WAN [Forward] - [Outbound Default rule match] Mon, 2006-02-27 19:30:51 - TCP packet - Source:192.168.0.2,1150 ,LAN - Destination:208.45.133.139,80[HTTP] ,WAN [Forward] - [Outbound Default rule match] Mon, 2006-02-27 19:30:51 - TCP packet - Source:192.168.0.2,1151 ,LAN - Destination:208.45.133.132,80[HTTP] ,WAN [Forward] - [Outbound Default rule match] Mon, 2006-02-27 19:30:52 - TCP packet - Source:192.168.0.2,1152 ,LAN - Destination:208.45.133.132,80[HTTP] ,WAN [Forward] - [Outbound Default rule match] Mon, 2006-02-27 19:31:16 - TCP packet - Source:192.168.0.2,1154 ,LAN - Destination:69.28.186.158,119 ,WAN [Forward] - [Outbound Default rule match] Mon, 2006-02-27 19:31:16 - TCP packet - Source:192.168.0.2,1155 ,LAN - Destination:69.28.186.158,119 ,WAN [Forward] - [Outbound Default rule match] Mon, 2006-02-27 19:32:29 - TCP packet - Source:192.168.0.2,1156 ,LAN - Destination:63.111.24.62,80[HTTP] ,WAN [Forward] - [Outbound Default rule match] Mon, 2006-02-27 19:33:26 - TCP packet - Source:192.168.0.2,1157 ,LAN - Destination:69.28.186.158,119 ,WAN [Forward] - [Outbound Default rule match]

"K2NNJ" wrote in message news:sTMMf.605$ snipped-for-privacy@fe08.lga...

Reply to
K2NNJ
Loading thread data ...

The point is if you have malware on the machine and it's sending outbound traffic to a WAN IP and you have detected this because you have reviewed the syslogs and detected or determined that the traffic is dubious in nature, then you can block the outbound traffic to the WAN IP until such time that you find the malware using software tools on the machine to track it down. The malware cannot circumvent or come around the outbound rules that have been set on the router like it can on a host based FW solution such as a personal FW that runs with the O/S. The malware can at the computer boot process with a host based FW solution beat the FW to the TCP/IP connection before the host based FW can even be started to stop the connection. That includes any worthless Application Control in PFW's too. The router with it's outbound rules set to stop outbound if need be is not part of the computer and is not running with the O/S like the PFW or host based solution with the O/S with them being easily defeated.

That is the point.

Duane :)

Reply to
Duane Arnold

So it has a syslog out put and maybe should be using something like Wallwatcher (free) to better organize what you are seeing to help you make determinations or analysis on the network traffic to/from the router.

Duane :)

Reply to
Duane Arnold

Below is all I get on the wireless router.

ALLOW:wrapper.3dgamers.com] Source: 192.168.1.3 M>> I hooked up the FR114P to get a look.

Reply to
K2NNJ

Reply to
K2NNJ

If it were me, I would use the wired router as the gateway router, disable DHCP on the wireless router making it a wire/wireless AP switch still using the MAC and whatever else wireless security the can be enabled as it being a wire/WAP switch and plug it into that wire router. The wire computer seems to have better security and FW features than the wireless has like stopping *outbound*.

You can apply the information in the link to your Netgear equipment as the principles of connecting two routers together are the same no matter if they are two wired, two wireless or wire and wireless routes or brand names.

formatting link
People run out to get a wireless router when they already have a wired router and all they needed was a standalone WAP device plugging it into the wire router to have wireless and went on about their business.

Duane :)

Reply to
Duane Arnold

I was actually thinking of wiring the two together, but I didn't think it could be done. I also didn't think about the WAP scenario either. Oh well, live and learn I guess!

formatting link

Reply to
K2NNJ

Rule of thumb: You ALWAYS need a FW, when connected to ANY net...

It's too difficult to decide when you really don't need one.

Erik

Reply to
erik

No.

No.

Yours, VB.

Reply to
Volker Birk

ah-ha

Reply to
erik

I suspect you don't realise what you know

Reply to
erik
[firewall]

Hm... maybe you're right.

But: if you don't have Windows, but let's say Debian GNU/Linux, SuSE Linux, Fedora, FreeBSD or MacOS X (as an example), then it's even easier not to offer network services to the Internet than to implement a firewall.

If you have Windows 2000, then

formatting link
will help. If you have Windows XP, then SP2 offers an auto-implemented Windows-Firewall, an host based packet filter.

Only if you have a small network with Windows at home, then it is possible while too complicated for a home user to configure sercurely, I'd say.

Then a small router with included firewall really will help. And of course, to have such a filtering router is not an error and at least a good idea for everybody, so you're not too wrong.

Yours, VB.

Reply to
Volker Birk

[compton ~]$ nmap ghotto -p 1- Starting nmap V. 3.93 (
formatting link
) All 65535 scanned ports on ghotto.phx.az.us (192.168.1.229) are: closed Nmap run completed -- 1 IP address (1 host up) scanned in 36 seconds [compton ~]$

There is no firewall on ghotto. It's a UNIX workstation - and it's not running a web server... or any other server. It _does_ have a web browser - three in fact, and from here I can see that one is being used at the moment. Now, what exactly would adding a firewall do?

It took 36 seconds to find out - but if I went over to the keyboard and typed in the command 'netstat -tuan' I'd find the same thing in less than a second. Even windoze supposedly has that command, although the options are different.

I know enough to know that there is more to using a computer than clicking on some icon or URL and "being amazed". They lied to you when they said that even an untrained monkey on crack can use a computer.

Old guy

Reply to
Moe Trin

To appreciate the knowledge involved in all this, try tracing it back to the level of the general user (often, wrongly, indicated by words like stupid, ignorant, dumbo etc, by the high prietsts of ICT)

You can't do it, I suspect.

Again: try to list the knowledge involved in this... examine your own history.

Reply to
erik

The quote at the bottom, which reads:

They lied to you when they said that even an untrained monkey on crack can use a computer.

The general user (and this isn't limited to computers) has been mis-led into the concept that computers (in this case) require no special knowledge to use. This is not true. But even limited knowledge would help.

And whose fault is that?

Old guy

Reply to
Moe Trin

Cabling-Design.com Forums website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.