xI9Prq0O0edgL1tcCvErj0Auh52K4I4sw=;
b=DubCpjFHsjaax7iocOPnv8Fjs9gbDs3gq7+Qz4V9IlP2nacPSgDm6iWYea2JL7wtDj
5Gv/ZQTnPKGeSxL+28hSPdkLyY6qPeDq6uZYs2Psi8Y3lvNqulfq/Y3f5YhVRS6XfuHN
mwY53d9AlL1/PwQ/j5ic4vZxC9om8tZs+FhEs=
MIME-Version: 1.0
Received: by 10.52.19.166 with SMTP id g6mr173215vde.10.1327548620938; Wed, 25
Jan 2012 19:30:20 -0800 (PST)
Received: by 10.220.210.65 with HTTP; Wed, 25 Jan 2012 19:30:20 -0800 (PST)
In-Reply-To: <20120122115457.GA23380@???>
References: <CAF=eGRi_CyUsmuN1AqG3q0T=mwTm2MZfbEjqCW-Dz3KTKkipiw@???>
<20120122115457.GA23380@???>
Date: Wed, 25 Jan 2012 22:30:20 -0500
Message-ID: <CAL7LUj9u2usZUmt+Wx5XAms5JOa+tKbw_2qVKMUepUYDMB+Vdw@???>
From: S P <sundancecloud@???>
To: users@???
Content-Type: multipart/alternative; boundary=20cf307c9c66f91c4004b765ffbc
X-Virus-Scanner: Scanned by ClamAV on mail.bitfolk.com at Thu,
26 Jan 2012 03:30:28 +0000
X-SA-Exim-Connect-IP: 209.85.212.48
X-SA-Exim-Mail-From: sundancecloud@???
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
spamd0.lon.bitfolk.com
X-Spam-Level:
X-Spam-ASN: AS15169 209.85.212.0/24
X-Spam-Status: No, score=-0.8 required=5.0 tests=DKIM_SIGNED,DKIM_VALID,
DKIM_VALID_AU,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS shortcircuit=no
autolearn=disabled version=3.3.1
X-Spam-Report: * -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/,
low * trust * [209.85.212.48 listed in list.dnswl.org]
* -0.0 SPF_PASS SPF: sender matches SPF record
* 0.0 HTML_MESSAGE BODY: HTML included in message
* -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's * domain
* -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
* 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily
* valid
X-SA-Exim-Version: 4.2.1 (built Wed, 25 Jun 2008 17:14:11 +0000)
X-SA-Exim-Scanned: Yes (on mail.bitfolk.com)
Subject: Re: [bitfolk] Finding out old IP users
X-BeenThere: users@???
X-Mailman-Version: 2.1.11
Precedence: list
List-Id: Users of BitFolk hosting <users.lists.bitfolk.com>
List-Unsubscribe: <https://lists.bitfolk.com/mailman/options/users>,
<mailto:users-request@lists.bitfolk.com?subject=unsubscribe>
List-Archive: <http://lists.bitfolk.com/lurker/list/users.html>
List-Post: <mailto:users@lists.bitfolk.com>
List-Help: <mailto:users-request@lists.bitfolk.com?subject=help>
List-Subscribe: <https://lists.bitfolk.com/mailman/listinfo/users>,
<mailto:users-request@lists.bitfolk.com?subject=subscribe>
X-List-Received-Date: Thu, 26 Jan 2012 03:30:28 -0000
--20cf307c9c66f91c4004b765ffbc
Content-Type: text/plain; charset=ISO-8859-1
Andy,
I got your point about "ip addr del ...", but could you help out with "...
then remove from network configuration ..."?
Thanks,
Sandy
On Sun, Jan 22, 2012 at 6:54 AM, Andy Smith <andy@???> wrote:
> Hi Taavi,
>
> On Sun, Jan 22, 2012 at 01:47:58PM +0200, Taavi Ilves wrote:
> > Has anyone a simple solution for catching where from and which
> > protocol are those connections coming for old IP?
>
> # tcpdump -vpni eth0 'host 212.13.19X.Y'
>
> I've had a quick look and it seems to mostly just be random useless
> traffic. You could avoid being warned again by removing the IP
> address entirely:
>
> # ip addr del 212.13.19X.Y dev eth0
>
> (then remove from network configuration so it doesn't come back next
> time you boot)
>
> Cheers,
> Andy
>
> --
> http://bitfolk.com/ -- No-nonsense VPS hosting
>
> _______________________________________________
> users mailing list
> users@???
> https://lists.bitfolk.com/mailman/listinfo/users
>
--20cf307c9c66f91c4004b
