I'm not very familiar with the route code, but here is what i came up with.
[EMAIL PROTECTED] mjl]$ sudo route change 10.3.2.1 127.0.0.1
route: writing to routing socket: No such process
change host 10.3.2.1: gateway 127.0.0.1: not in table
the code checks that if changing a host or network route
On Wed, Jul 06, 2005 at 11:46:00PM +0900, [EMAIL PROTECTED] wrote:
> As was reported in
> http://www.freebsd.org/cgi/query-pr.cgi?pr=%0D%0A82974
[snip]
This is definitely a bug, no question about it. RTM_CHANGE should let
you change the next-hop, but not the destination or the netmask. [Sklower]
A
Slightly off topic, but have you had a chance to look at that lock
recursion bug in the routing code that I had reported awhile ago?
Admittedly, I never send-pr'd it. However, I should have the original
information around... Perhaps I will test.
On Wed, 6 Jul 2005 [EMAIL PROTECTED] wrote:
:H
Howdy,
As was reported in
http://www.freebsd.org/cgi/query-pr.cgi?pr=%0D%0A82974
if you do
route change 10.3.2.1 127.0.0.1
on a system with a default route but no route on the 10 network at
all, you wind up setting the default route to 127.0.0.1 which is
rarely what you want. This is due to t
