All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phil Oester <kernel@linuxace.com>
To: Alexey Toptygin <alexeyt@freeshell.org>
Cc: "Laurence J. Lane" <ljlane@debian.org>,
	netfilter-devel@lists.netfilter.org
Subject: Re: iptables 1.3.6 not using /etc/networks
Date: Mon, 13 Nov 2006 09:12:36 -0800	[thread overview]
Message-ID: <20061113171236.GA10032@linuxace.com> (raw)
In-Reply-To: <Pine.NEB.4.64.0611130053020.6631@ukato.freeshell.org>

On Mon, Nov 13, 2006 at 12:58:48AM +0000, Alexey Toptygin wrote:
> >But if you use a FQDN such as www.domain.com/24, then shouldn't that
> >then imply <ip of www.domain.com>/24?  That's why I didn't make the
> >exception for letters vs. digits, as it could be used either way.
> 
> I don't understand what you mean. I think if it starts with a digit, it 
> must be an IP (or part of an IP with 0's dropped), else it is a network 
> name or a domain name (since neither of those can start with digits). If 
> it's an IP by the above logic, then pad it with '.0's as necessary (or 
> translate directly into a number without padding first). If it's not an 
> IP, first call getnetbyname on it and if that returns NULL call 
> gethostbyname. I think this algorithm works in all cases, unless I'm 
> missing something.

What I meant was some people might want to include the /24 a host sits
on, and use something like "mydomain.com/24".  When the name gets
translated to 1.2.3.4, the cidr would make it 1.2.3.0/24.

Also, as Martijn points out, just starting with digit doesn't imply
an IP, as hosts can start with digits also.

The difficulty here is we can't easily have /etc/networks be processed
and have shorthand CIDR notation (such as 10.10.10/24) work.

Phil

  parent reply	other threads:[~2006-11-13 17:12 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-12  1:25 iptables 1.3.6 not using /etc/networks Laurence J. Lane
2006-11-12  2:35 ` Laurence J. Lane
2006-11-12 17:33   ` Phil Oester
2006-11-12 19:36     ` Alexey Toptygin
2006-11-12 19:43       ` Phil Oester
2006-11-13  0:58         ` Alexey Toptygin
2006-11-13  7:23           ` Martijn Lievaart
2006-11-13 15:50             ` Alexey Toptygin
2006-11-13 20:20               ` Martijn Lievaart
2006-11-13 21:23                 ` Alexey Toptygin
2006-11-14  9:06                   ` offtopic " Amin Azez
2006-11-14  9:24               ` Benny Amorsen
2006-11-13 17:12           ` Phil Oester [this message]
2006-11-13 17:56             ` Alexey Toptygin
2006-11-13 19:50               ` scott comer (sccomer)
2006-11-18 22:09     ` Laurence J. Lane
2006-11-18 22:12       ` Laurence J. Lane
2006-11-20  0:00       ` Pablo Neira Ayuso
2006-11-23 14:10         ` Patrick McHardy
2006-11-23 20:56           ` Pablo Neira Ayuso
2006-11-24  5:55             ` Phil Oester
2006-11-24  8:43               ` Patrick McHardy
2006-11-29  4:44                 ` Phil Oester
2006-11-29 12:50                   ` Patrick McHardy
2006-11-29 14:09         ` Amin Azez
2006-11-29 14:21           ` Pablo Neira Ayuso
2006-11-19 20:34     ` Pablo Neira Ayuso
  -- strict thread matches above, loose matches on Subject: below --
2006-11-13 17:00 Alexey Toptygin
     [not found] <200611131926.kADJPxur030380@mail3.jubileegroup.co.uk>
2006-11-14 10:17 ` G.W. Haywood
2006-11-14 19:28   ` Grant Coady

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=20061113171236.GA10032@linuxace.com \
    --to=kernel@linuxace.com \
    --cc=alexeyt@freeshell.org \
    --cc=ljlane@debian.org \
    --cc=netfilter-devel@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.