Re: Bizzare routing table entry.

2007-08-08 Thread Dan Nelson
In the last episode (Aug 07), Modulok said:
> I have a bizarre entry in the routing table on one my machines. What
> is it, and how do I delete it? The output of "netstat -rnf inet" is
> shown below:
> 
>   DestinationGatewayFlagsRefs  Use  Netif Expire
>   0&0xc0a80132   link#1 UCS 00   bge0
>   127.0.0.1  127.0.0.1  UH  0  557lo0
>   ...
> 
> QUESTIONS
> 1. The first entry, it's not IPv4, IPv6 or a MAC address that I've
> ever seen, what format is it?

It's in IPAddress&Netmask format.

$ echo "ibase=16;C0;A8;01;32" | bc
192
168
1
50

Someone probably ran "ifcofig bge0 netmask 192.168.1.50" or some script
did it to you.

> 2. How do I delete it? According to route(8) it is not a "valid
> address" and when I attempt to delete it, route(8) gets very upset:
> 
> root# route delete 0&0xc0a80132
> 
>   [1] 37343
>   route: writing to routing socket: No such process
>   delete net 0: not in table
>   0xc0a80132: Command not found.
>   [1]  + Exit 1route delete 0

& is a shell metacharacter; try this:  route delete "0&0xc0a80132"
 
-- 
Dan Nelson
[EMAIL PROTECTED]
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: Bizzare routing table entry.

2007-08-08 Thread jdow

From: "Josh Carroll" <[EMAIL PROTECTED]>


root# route delete 0&0xc0a80132

  [1] 37343
  route: writing to routing socket: No such process
  delete net 0: not in table
  0xc0a80132: Command not found.
  [1]  + Exit 1route delete 0



root# route delete 0&0xc0a80132

  [1] 37343
  route: writing to routing socket: No such process
  delete net 0: not in table
  0xc0a80132: Command not found.
  [1]  + Exit 1route delete 0


I've no idea whether that is a valid route or not, but the reason
you're getting that funkiness is that the shell is eating the & and
thinks you are sending the route process to the background. Try:

route delete '0&0xc0a80132'


There goes 192.168.1.50.

{^_-}Joanne


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: Bizzare routing table entry.

2007-08-08 Thread Ian Smith
On Tue, 7 Aug 2007 15:37:50 -0700 Chuck Swiger <[EMAIL PROTECTED]> wrote:
 > On Aug 7, 2007, at 3:13 PM, Adam J Richardson wrote:
 > > Modulok wrote:
 > >>   0&0xc0a80132   link#1 UCS 00   bge0
 > > 
 > >> 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 192.168.1.50.
 > 
 > An IP address + netmask can normally be represented in the routing  
 > table via the slash notation-- say 192.168.1.50/24 meaning a  
 > 255.255.255.0 (or 0xff00) 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.

Been there; in my case it was a rogue route added by an ifconfig with an
incorrect - as you say, non-contiguous - netmask.  In this case it might
have been specified/interpreted as 0.0.0.0 netmask 192.168.1.50 ?

Cheers, Ian

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: Bizzare routing table entry.

2007-08-08 Thread Modulok
You guys are sweethearts. We're ship-shape again :)

Thanks all who contributed.
-Modulok-

On 8/7/07, Modulok <[EMAIL PROTECTED]> wrote:
> I have a bizarre entry in the routing table on one my machines. What
> is it, and how do I delete it? The output of "netstat -rnf inet" is
> shown below:
>
>   DestinationGatewayFlagsRefs  Use  Netif Expire
>   0&0xc0a80132   link#1 UCS 00   bge0
>   127.0.0.1  127.0.0.1  UH  0  557lo0
>   ...
>
> QUESTIONS
> 1. The first entry, it's not IPv4, IPv6 or a MAC address that I've
> ever seen, what format is it?
> 2. How do I delete it? According to route(8) it is not a "valid
> address" and when I attempt to delete it, route(8) gets very upset:
>
> root# route delete 0&0xc0a80132
>
>   [1] 37343
>   route: writing to routing socket: No such process
>   delete net 0: not in table
>   0xc0a80132: Command not found.
>   [1]  + Exit 1route delete 0
>
> Thoughts?
> -Modulok-
>
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: Bizzare routing table entry.

2007-08-07 Thread Chuck Swiger

On Aug 7, 2007, at 3:13 PM, Adam J Richardson wrote:

Modulok wrote:

  0&0xc0a80132   link#1 UCS 00   bge0



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 192.168.1.50.

An IP address + netmask can normally be represented in the routing  
table via the slash notation-- say 192.168.1.50/24 meaning a  
255.255.255.0 (or 0xff00) 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.


--
-Chuck

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: Bizzare routing table entry.

2007-08-07 Thread Adam J Richardson

Modulok wrote:

  0&0xc0a80132   link#1 UCS 00   bge0



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.


HtH,
Adam J Richardson
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: Bizzare routing table entry.

2007-08-07 Thread Chuck Swiger

On Aug 7, 2007, at 12:10 PM, Modulok wrote:

I have a bizarre entry in the routing table on one my machines. What
is it, and how do I delete it? The output of "netstat -rnf inet" is
shown below:

  DestinationGatewayFlagsRefs  Use   
Netif Expire

  0&0xc0a80132   link#1 UCS 00   bge0
  127.0.0.1  127.0.0.1  UH  0  557lo0
  ...

QUESTIONS
1. The first entry, it's not IPv4, IPv6 or a MAC address that I've
ever seen, what format is it?


It looks a default IPv4 route using a non-contiguous netmask.  It's  
almost certainly the result of running route with the wrong  
arguments, rather than something you would intend to do.



2. How do I delete it? According to route(8) it is not a "valid
address" and when I attempt to delete it, route(8) gets very upset:

root# route delete 0&0xc0a80132

  [1] 37343
  route: writing to routing socket: No such process
  delete net 0: not in table
  0xc0a80132: Command not found.
  [1]  + Exit 1route delete 0


The "&" is confusing the shell; you can probably do a "route delete  
default" to nuke it.


--
-Chuck

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: Bizzare routing table entry.

2007-08-07 Thread Josh Carroll
> root# route delete 0&0xc0a80132
>
>   [1] 37343
>   route: writing to routing socket: No such process
>   delete net 0: not in table
>   0xc0a80132: Command not found.
>   [1]  + Exit 1route delete 0

> root# route delete 0&0xc0a80132
>
>   [1] 37343
>   route: writing to routing socket: No such process
>   delete net 0: not in table
>   0xc0a80132: Command not found.
>   [1]  + Exit 1route delete 0

I've no idea whether that is a valid route or not, but the reason
you're getting that funkiness is that the shell is eating the & and
thinks you are sending the route process to the background. Try:

route delete '0&0xc0a80132'

And see if it lets you remove the entry.

Josh
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Bizzare routing table entry.

2007-08-07 Thread Modulok
I have a bizarre entry in the routing table on one my machines. What
is it, and how do I delete it? The output of "netstat -rnf inet" is
shown below:

  DestinationGatewayFlagsRefs  Use  Netif Expire
  0&0xc0a80132   link#1 UCS 00   bge0
  127.0.0.1  127.0.0.1  UH  0  557lo0
  ...

QUESTIONS
1. The first entry, it's not IPv4, IPv6 or a MAC address that I've
ever seen, what format is it?
2. How do I delete it? According to route(8) it is not a "valid
address" and when I attempt to delete it, route(8) gets very upset:

root# route delete 0&0xc0a80132

  [1] 37343
  route: writing to routing socket: No such process
  delete net 0: not in table
  0xc0a80132: Command not found.
  [1]  + Exit 1route delete 0

Thoughts?
-Modulok-
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"