[GRLUG] DoS Block on my local IP address

[Eric Beversluis]

On 12/28/2010 8:41 AM, Dan Pilcheck wrote:
> On Tue, Dec 28, 2010 at 8:01 AM, Eric Beversluis
> <ebever at researchintegration.org>  wrote:
>> On 12/28/2010 7:57 AM, Ben Rousch wrote:
>>> On Tue, Dec 28, 2010 at 7:52 AM, Eric Beversluis
>>> <ebever at researchintegration.org>    wrote:
>>>
>>>> Suddenly this morning my Linux box won't reach the internet, although LAN
>>>> is
>>>> working fine. When I look at the firewall log on my Belkin router, it
>>>> shows
>>>> a DoS block on the Linux box IP address. When I talk to Belkin support,
>>>> they
>>>> say that I need to change something in the Linux box to remove the block,
>>>> not something in the Belkin wireless router.
>>>>
>>>> Does anyone know what would be causing this and what I need to do? (I was
>>>> trying unsuccessfully to access the Linux box by terminal server client
>>>> last
>>>> night because of a monitor problem on the box. So I'm wondering if that
>>>> may
>>>> have triggered some response in the Linux box that I need to undo?)
>>>>
>>> Is it possible that your ISP is blocking you so as to draw your
>>> attention to a virus infection or nefarious activity emanating from
>>> your network?
>>>
>> It's the private IP (192.168.2.3) that's showing blocked, and the Windows
>> boxes are getting out to the network fine. I don't think there's any way for
>> TimeWarner to block some of the boxes on my LAN but not others, is there
>>>
>>>> I've tried turning the Linux firewall off an on, turning the Belkin
>>>> firewall
>>>> off and on, powering down and up the Belkin and the cable modem, and
>>>> probably some other things I can't remember.
>>>>
>>>> Running openSUSE 11.2 on Lenovo 3000 N100.
> I'm sure you have, but have you tried assigning a different LAN IP
> address for the linux machine?
>
Update: I turned the router's DHCP off and then back on. Got new IPaddr 
for the Linux box (...6). And that IP addr is now showing "Blocked" in 
the router's firewall log. No Internet but still can reach/ping other 
LAN boxes. I tried booting  from a live Ubuntu CD and got to the 
Internet fine with that.

So I'm coming back to wondering whether my trying to do remote access to 
the box without having it properly configured to accept that could have 
caused it to be behaving differently this morning? I don't see anything 
in the Yast firewall settings page relevant to this (actually tried with 
the firewall turned off, but that didn't help either).

Will try router factory reset and see what that does.

Thanks for all the suggestions.

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.