Hi!

Does anyone have an idea what is going on here?

: # route add -host 10.0.0.13 -iface sl8
: add host 10.0.0.13: gateway sl8
: # netstat -rn | grep ^10.0.0.13
: 10.0.0.13          sl8                UHS         0        0      sl8
: # arp -s 10.0.0.13 1:1:1:1:1:1 pub
: # netstat -rn | grep ^10.0.0.13
: 10.0.0.13          sl8                UHS         0        0      sl8
: 10.0.0.13          1.1.1.1.1.1        UHS2        0        0      sl9
: # route delete -host 10.0.0.13
: delete host 10.0.0.13
: # netstat -rn | grep ^10.0.0.13
: 10.0.0.13          1.1.1.1.1.1        UHS2        0        0      sl9
: # route delete -host 10.0.0.13
: route: writing to routing socket: No such process
: delete host 10.0.0.13: not in table
: # netstat -rn | grep ^10.0.0.13
: 10.0.0.13          1.1.1.1.1.1        UHS2        0        0      sl9
: # arp -d 10.0.0.13
: delete: can't locate 10.0.0.13
: # netstat -rn | grep ^10.0.0.13
: 10.0.0.13          1.1.1.1.1.1        UHS2        0        0      sl9
  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Now, I can't delete this entry!

In the `route -v -n -d flush' output it looks like:

: RTM_GET: Report Metrics: len 164, pid: 0, seq 0, errno 0, 
:flags:<UP,HOST,STATIC,PROTO2>
: locks:  inits: 
: sockaddrs: <DST,GATEWAY>
:  10.0.0.13 1.1.1.1.1.1

Trying to delete this entry results in:

: # route -v -n delete -host 10.0.0.13 -iface -proto2
: u: inet 10.0.0.13; 
: RTM_DELETE: Delete Route: len 108, pid: 0, seq 1, errno 0, 
:flags:<UP,HOST,STATIC,PROTO2>
: locks:  inits: 
: sockaddrs: <DST>
:  10.0.0.13
: route: writing to routing socket: No such process
: delete host 10.0.0.13: not in table


Thanks,
-- 
Ruslan Ermilov          Sysadmin and DBA of the
[EMAIL PROTECTED]        United Commercial Bank,
[EMAIL PROTECTED]          FreeBSD committer,
+380.652.247.647        Simferopol, Ukraine

http://www.FreeBSD.org  The Power To Serve
http://www.oracle.com   Enabling The Information Age


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Reply via email to