George, I believe netstat already utilizes the sysctl API to get information about the TCP and UDP control blocks for state information. The modules for tcp and udp already contain sysctl backend routines that do this. Additionally, there is implementation for the ip_divertlist and the raw CBs as well.
Are you referring to something in addition to these? -Anand At 10:48 AM 4/26/02, George V. Neville-Neil wrote: > > We have a sysctl that takes the four tuple as an argument, which can > > be got from netstat -an output. It is used only for deleting a > > connection not modifying it. > > > > for e.g > > sysctl net.inet.tcp.deleteconn="a.b.c.d:80:x.y.z.w:30000". > > > > netstat -Aan gives us the tcp control block address or the inpcb address > > depending on the type of socket. That could also be used for identifying > > the socket. > >Do you mean this is what you'd like or that it exists? I get: > ># sysctl net.inet.tcp.deleteconn="209.157.133.226.4296:216.136.204.21.80" >sysctl: unknown oid 'net.inet.tcp.deleteconn' ># > >when I try it. > >Later, >George > >-- >George V. Neville-Neil [EMAIL PROTECTED] >Neville-Neil Consulting www.neville-neil.com > >"I learn only to be contented." inscription at Ryoan-ji in Kyoto, Japan > > > >To Unsubscribe: send mail to [EMAIL PROTECTED] >with "unsubscribe freebsd-net" in the body of the message ******************************** Anand Narayanan Wind River Systems. http://www.windriver.com ******************************** To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-net" in the body of the message
