Bizzare routing table entry.

[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 1                        route 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 1                        route 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