Re: [bitfolk] Lenny to Squeeze

Top Page

Reply to this message
Author: Joseph Heenan
Date:  
Subject: Re: [bitfolk] Lenny to Squeeze
s (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
>


--20cf307c9c66f91c4004b765ffbc
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Andy,<br><br>I got your point about &quot;ip addr del ...&quot;, but could =
you help out with &quot;... then remove from network configuration ...&quot=
;?<br><br>Thanks,<br>Sandy<br><br><div class=3D"gmail_quote">On Sun, Jan 22=
, 2012 at 6:54 AM, Andy Smith <span dir=3D"ltr">&lt;<a href=3D"mailto:andy@=
bitfolk.com">andy@???</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Hi Taavi,<br>
<div class=3D"im"><br>
On Sun, Jan 22, 2012 at 01:47:58PM +0200, Taavi Ilves wrote:<br>
&gt; Has anyone a simple solution for catching where from and which<br>
&gt; protocol are those connections coming for old IP?<br>
<br>
</div># tcpdump -vpni eth0 &#39;host 212.13.19X.Y&#39;<br>
<br>
I&#39;ve had a quick look and it seems to mostly just be random useless<br>
traffic. You could avoid being warned again by removing the IP<br>
address entirely:<br>
<br>
# ip addr del 212.13.19X.Y dev eth0<br>
<br>
(then remove from network configuration so it doesn&#39;t come back next<br=
>

time you boot)<br>
<br>
Cheers,<br>
Andy<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
--<br>
<a href=3D"http://bitfolk.com/" target=3D"_blank">http://bitfolk.com/</a> -=
- No-nonsense VPS hosting<br>
</font></span><div class=3D"HOEnZb"><div class=3D"h5"><br>
_______________________________________________<br>
users mailing list<br>
<a href=3D"mailto:users@lists.bitfolk.com">users@???</a><br>
<a href=3D"https://lists.bitfolk.com/mailman/listinfo/users" target=3D"_bla=
nk">https://lists.bitfolk.com/mailman/listinfo/users</a><br>
</div></div></blockquote></div><br>

--20cf3