From owner-freebsd-net@FreeBSD.ORG  Wed Mar 29 17:51:38 2006
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
X-Original-To: freebsd-net@freebsd.org
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 8048016A41F
	for <freebsd-net@freebsd.org>; Wed, 29 Mar 2006 17:51:38 +0000 (UTC)
	(envelope-from arcade@synergetica.dn.ua)
Received: from nora.synergetica.dn.ua (synergetica.dn.ua [82.207.115.117])
	by mx1.FreeBSD.org (Postfix) with ESMTP id ABED943D4C
	for <freebsd-net@freebsd.org>; Wed, 29 Mar 2006 17:51:37 +0000 (GMT)
	(envelope-from arcade@synergetica.dn.ua)
Received: from [172.30.0.220] (source.lan [172.30.0.220])
	by nora.synergetica.dn.ua (8.13.4/8.13.4) with ESMTP id k2THpYiH002169
	for <freebsd-net@freebsd.org>; Wed, 29 Mar 2006 20:51:34 +0300 (EEST)
	(envelope-from arcade@synergetica.dn.ua)
Message-ID: <442AC92A.1030507@synergetica.dn.ua>
Date: Wed, 29 Mar 2006 20:51:38 +0300
From: Volodymyr Kostyrko <arcade@synergetica.dn.ua>
Organization: Synergetica OC
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ru-RU;
	rv:1.8.0.1) Gecko/20060130 SeaMonkey/1.0
MIME-Version: 1.0
To: freebsd-net@freebsd.org
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: inet_aton behavior
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Mar 2006 17:51:38 -0000

Hi all.

   Roaming recently through whois database i've stumbled upon the 
following ip-address notations:

   194.134.086.040
   212.223.085.184
   212.129.243.040
   194.134.086.32
   ... etc ...

   Giving this addresses to inet_aton results in exceptions, or address 
misspelling due to:

[man inet_aton]
      All numbers supplied as ``parts'' in a `.' notation may be decimal,
      octal, or hexadecimal, as specified in the C language (i.e., a 
leading 0x
      or 0X implies hexadecimal; otherwise, a leading 0 implies octal; 
other-
      wise, the number is interpreted as decimal).
[man inet_aton]

   However, RFC1166 names addresses as "dotted decimal" and doesn't 
specifies any form of writing 'em with octal or hexadecimal numbers.

   Am I wrong somewhere? Does inet_aton breaks RFC? Is there any other 
common functions to process those "expanded with zeroes" addresses?

-- 
[WBR], Arcade.