Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 7 Aug 2007 15:37:50 -0700
From:      Chuck Swiger <>
To:        Adam J Richardson <>
Cc:, Modulok <>
Subject:   Re: Bizzare routing table entry.
Message-ID:  <>
In-Reply-To: <>
References:  <> <>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On Aug 7, 2007, at 3:13 PM, Adam J Richardson wrote:
> Modulok wrote:
>>   0&0xc0a80132       link#1             UCS         0        0   bge0
> <snip>
>> 1. The first entry, it's not IPv4, IPv6 or a MAC address that I've
>> ever seen, what format is it?
> Hi Modulok,
> It's possible to represent IPv4 addresses as a single number. I  
> don't recall the algorithm for converting that four byte dot- 
> delimited group into an integer, though, so I can't tell you what  
> number it is. Perhaps you can Google the algorithm and do the math  
> to figure out what it is.

aaa.bbb.ccc.ddd => 0xAABBCCDD, where AA = hex(aaa), BB = hex(bbb), etc.
In particular, 0xc0a80132 is the hex equivalent of

An IP address + netmask can normally be represented in the routing  
table via the slash notation-- say meaning a (or 0xffffff00) netmask.  Non-contiguous netmasks are  
represented by "address & netmask", but since no normal network ever  
uses such a netmask, they almost always represent a  
misconfiguration-- someone confused the arguments such that the route  
command interpreted the gateway IP as a netmask instead.


Want to link to this message? Use this URL: <>