Re: Backgroun dnoise

From: Leonid Rosenboim (My_1st_name@Consultant.Com)
Date: 10/10/02


From: "Leonid Rosenboim" <My_1st_name@Consultant.Com>
Date: Thu, 10 Oct 2002 11:55:50 +0200

Wolfgang is right, and I really dont understand the reason
for ignorant people to try and solve other people's problems
for free.

Anyway, background noise is a problem with all firewalls.

Especially when a routing outage happens somewhere,
and you have connections effected by that ouitage, as short
as it may be, there are going to be very late packets which
where part of a valid connection, but where stuck in
routers' queue or in temporary routing loops, that
eventually get delivered, after the firewall/NAT
has alredy timed that session out.

It happens with ZomeArlam, it happens with the Intel Wireless
Gateway I got at home, and it happens with Cisco IOS/FW,
as well as Checkpoint FW-1. Even if session timeout is set
at 2 minutes (the recommended timeout in many RFCs),
there will still be these false alarms.

The cost of setting session timeouts too long is high -
there would be a need for much more memory to keep
track for terminated session for a longer period, and
thus the total number of entries in the session tables
would need to be increased.

-- HTH
-----------------------------------------------------------------------
   Leonid Rosenboim Visit: http://www.masada2000.org/
        Consultant Email: my first name at consultant dot com

"Wolfgang Kueter" <wolfgang@shconnect.de> wrote in message
news:ao2nit$vj4$1@news.shlink.de...
> taharka wrote:
>
> > The following link is a security report on that addy at
mynetwatchman.com
> > : http://www.mynetwatchman.com/LID.asp?IID=8254594
> > Looks like this guys been at it for a while.
> >
> > Here is the info on that addy's ISP:
> >
> > 206.13.29.12 (dns1-la.lsan03.pacbell.net)
>
> > [a lot of totally irrelevat stuff deleted]
>
> > Port 1099:RATs: Blood Fest Evolution, RAT
> > Download portref.zip from: wilders.org for a full port reference
listing.
> >
> > If the firewall is blocking internet access to that addy, there is
nothing
> > to worry about. Probably that nasty ole NETBIOS/e-mail worm looking for
> > open shares.
>
> Sorry, complete nonsense. I might sound harsh, but your posting shows that
> you are completely clueless. Instead of posting some whois entries you
> should simply have looked at the ports and protocols used:
>
> It is udp, it is directed to Port 1099 and uses source port 53 coming from
>
> wk@heart-of-gold:~/patch/rh73> host 206.13.29.12
> 12.29.13.206.IN-ADDR.ARPA domain name pointer dns1-la.lsan03.pacbell.net
>
> which looks much like a DNS server. And something like
>
> wk@heart-of-gold:~> nslookup www.google.com dns1-la.lsan03.pacbell.net
> Server: dns1-la.lsan03.pacbell.net
> Address: 206.13.29.12
>
> Non-authoritative answer:
> Name: www.google.com
> Address: 216.239.35.101wk@heart-of-gold:~/patch/rh73> nslookup
> www.google.com dns1-la.lsan03.pacbell.net
> Server: dns1-la.lsan03.pacbell.net
> Address: 206.13.29.12
>
> Non-authoritative answer:
> Name: www.google.com
> Address: 216.239.35.101
>
> even shows you that it _is_ a DNS server.
>
> So what this stupid piece of firewall simulation did, was simply to
> misinterpret a late DNS answer packet as an attack.
>
> The only question here is what is more stupid, this firewall simulation
> giving false alarms or you, who is not able to distinguish between a late
> DNS answer and an attack.
>
> Read a book about network protocols.
>
> Wolfgang



Relevant Pages

  • Re: SSH connection thru corporate firewall to home sshd on Port 80
    ... > session and perhaps someone can explain this to me. ... > I have a FreeBSD server running sshd listening on port 80 at home. ... > internet to this SSHD:80 server (no firewall involved). ...
    (comp.security.ssh)
  • Re: SuSeFirewall config
    ... I do have a good reason for running a dns server:) It's for my ... I've tested by running nslookup from my home pc with our dns server set ... With the firewall started, ... I cannot telnet or ssh into port 53 from home regardless. ...
    (alt.os.linux.suse)
  • Re: SuSeFirewall config
    ... > I've tested by running nslookup from my home pc with our dns server set ... > With the firewall started, ... > I cannot telnet or ssh into port 53 from home regardless. ...
    (alt.os.linux.suse)
  • Re: RRAS packet filtering, what isTCP(established)?
    ... Windows host inside the firewall. ... port, the listener then sends a message back to the Oracle ... Windows/Oracle host to enter on any port. ... >from establishing a session. ...
    (microsoft.public.win2000.ras_routing)
  • Re: SuSeFirewall config
    ... > I've tested by running nslookup from my home pc with our dns server set ... > With the firewall started, ... > I cannot telnet or ssh into port 53 from home regardless. ...
    (alt.os.linux.suse)