Firewall causing problems downloading?

[Guest]

Archived from groups: comp.security.firewalls (More info?)

I've noticed recently that anytime I try to download a file of any size
(> 2MB), I tend to lose my internet connectivity. I can *always* solve
this problem by unplugging my cable modem and letting it sit for a few
seconds before plugging it back in.

I'm also using Windows XP firewall, and recently started logging to the
pfirewall.log file just to see if it might be a firewall-related issue.

Here is an excerpt from that file:

2005-08-20 07:51:02 DROP UDP 192.168.1.1 192.168.1.255 6386 162 122 - -
- - - - - RECEIVE
2005-08-20 07:51:07 DROP UDP 192.168.1.1 192.168.1.255 6387 162 122 - -
- - - - - RECEIVE
2005-08-20 07:51:12 DROP UDP 192.168.1.1 192.168.1.255 6388 162 122 - -
- - - - - RECEIVE
2005-08-20 07:51:12 DROP UDP 192.168.1.1 192.168.1.255 6389 162 145 - -
- - - - - RECEIVE
2005-08-20 07:51:14 DROP UDP 192.168.1.1 192.168.1.255 6390 162 143 - -
- - - - - RECEIVE


The only thing that concerns me is the seemingly sequential ports that
are being dropped - 6386, 6387, 6388, etc...

Could all of this somehow be related to my problem downloading?

 

[Frankster]

Archived from groups: comp.security.firewalls (More info?)

Since it is only traffic within your own system, you might as well unblock
it and find out.

-Frank

<bravodelta73@comcast.net> wrote in message
news:1124555731.441796.31060@g47g2000cwa.googlegroups.com...
> I've noticed recently that anytime I try to download a file of any size
> (> 2MB), I tend to lose my internet connectivity. I can *always* solve
> this problem by unplugging my cable modem and letting it sit for a few
> seconds before plugging it back in.
>
> I'm also using Windows XP firewall, and recently started logging to the
> pfirewall.log file just to see if it might be a firewall-related issue.
>
> Here is an excerpt from that file:
>
> 2005-08-20 07:51:02 DROP UDP 192.168.1.1 192.168.1.255 6386 162 122 - -
> - - - - - RECEIVE
> 2005-08-20 07:51:07 DROP UDP 192.168.1.1 192.168.1.255 6387 162 122 - -
> - - - - - RECEIVE
> 2005-08-20 07:51:12 DROP UDP 192.168.1.1 192.168.1.255 6388 162 122 - -
> - - - - - RECEIVE
> 2005-08-20 07:51:12 DROP UDP 192.168.1.1 192.168.1.255 6389 162 145 - -
> - - - - - RECEIVE
> 2005-08-20 07:51:14 DROP UDP 192.168.1.1 192.168.1.255 6390 162 143 - -
> - - - - - RECEIVE
>
>
> The only thing that concerns me is the seemingly sequential ports that
> are being dropped - 6386, 6387, 6388, etc...
>
> Could all of this somehow be related to my problem downloading?
>

 

[Guest]

Archived from groups: comp.security.firewalls (More info?)

"Frankster" <Frank@SPAM2TRASH.com> wrote in
news:2MudnS2AZO4Rw5reRVn-tA@giganews.com:

> Since it is only traffic within your own system, you might as well
> unblock it and find out.
>
> -Frank
>
> <bravodelta73@comcast.net> wrote in message
> news:1124555731.441796.31060@g47g2000cwa.googlegroups.com...
>> I've noticed recently that anytime I try to download a file of any
>> size (> 2MB), I tend to lose my internet connectivity. I can
>> *always* solve this problem by unplugging my cable modem and letting
>> it sit for a few seconds before plugging it back in.
>>
>> I'm also using Windows XP firewall, and recently started logging to
>> the pfirewall.log file just to see if it might be a firewall-related
>> issue.
>>
>> Here is an excerpt from that file:
>>
>> 2005-08-20 07:51:02 DROP UDP 192.168.1.1 192.168.1.255 6386 162 122 -
>> - - - - - - RECEIVE
>> 2005-08-20 07:51:07 DROP UDP 192.168.1.1 192.168.1.255 6387 162 122 -
>> - - - - - - RECEIVE
>> 2005-08-20 07:51:12 DROP UDP 192.168.1.1 192.168.1.255 6388 162 122 -
>> - - - - - - RECEIVE
>> 2005-08-20 07:51:12 DROP UDP 192.168.1.1 192.168.1.255 6389 162 145 -
>> - - - - - - RECEIVE
>> 2005-08-20 07:51:14 DROP UDP 192.168.1.1 192.168.1.255 6390 162 143 -
>> - - - - - - RECEIVE
>>
>>
>> The only thing that concerns me is the seemingly sequential ports
>> that are being dropped - 6386, 6387, 6388, etc...
>>
>> Could all of this somehow be related to my problem downloading?
>>
>
>
>

udp 162 is snmp traps, so 192.168.1.1 is broadcasting (dest of
192.168.1.255). Is the source your home router?