From: Curby <curby.public@gmail.com>
To: "isp@cgscomm.net" <isp@cgscomm.net>
Cc: netfilter@lists.netfilter.org
Subject: Re: about dettecting different TTL value
Date: Mon, 24 Apr 2006 03:44:46 -0600 [thread overview]
Message-ID: <5d2f37910604240244r3aa5980ere262fa2e766a42c8@mail.gmail.com> (raw)
In-Reply-To: <1161.202.22.193.97.1145853396.squirrel@202.22.193.97>
On 4/23/06, isp@cgscomm.net <isp@cgscomm.net> wrote:
> Hello,
>
> I am new here. I am working in an ISP. I like to know that how can I
> prevent user to use multiple computer with single internet connection? I
> have searched on the web and found nothing.
>
> I think it is only possible by detecting different TTL value that comes
> from same IP address. And I didn't get any thing from the web. I like to
> know that is it possible to do with IPTABLES?
It is possible but a flawed solution for several reasons:
1) You can use an iptables patch to mangle/reset the TTL of all
outgoing packets (even those of NATed machines), rendering such a
check useless.
2) Your subscribers could spoof packets with varying TTL values to get
other subscribers in trouble.
3) There are cases where a single computer would send outgoing packets
with varying TTL values: traceroutes, sensitive/custom protocols, etc.
Regarding the "problem" itself, remember that increasingly, more and
more households will have wireless laptops in addition to desktop
computers, separate computers for children, networked gaming consoles,
etc. IMHO it would be preferable to adjust your pricing so you are
profitable instead of cutting off an ever-growing demographic of
multi-machine households.
--Curby
next prev parent reply other threads:[~2006-04-24 9:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-24 4:36 about dettecting different TTL value isp
2006-04-24 5:15 ` Bob Sully
2006-04-24 9:44 ` Curby [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-05-03 4:41 isp
2006-05-03 5:18 ` Thomas Kuiper
2006-05-03 5:30 ` Cedric Blancher
2006-05-03 5:53 ` Thomas Kuiper
2006-05-03 7:32 ` Cedric Blancher
2006-05-03 7:50 ` Thomas Kuiper
2006-05-03 8:12 ` Cedric Blancher
2006-05-03 5:23 ` Cedric Blancher
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5d2f37910604240244r3aa5980ere262fa2e766a42c8@mail.gmail.com \
--to=curby.public@gmail.com \
--cc=isp@cgscomm.net \
--cc=netfilter@lists.netfilter.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.