Interface description support

[Jason Thorpe]

I'd say that we should explicitely mention if we're looking up a name or
a description, to avoid confusion. For example if wm0 has descrition
block in on wm0 from any to any
or
block in on intf_desc "external if" from any to any
netstat -I wm0
netstat -D "external if"
and so on ...

I think that severely limits the utility of the description field.

-- thorpej


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

[Jan Danielsson]

EF> Couldn't you just enforce the description to not match /[a-z]+[0-9]+/?
JT> That breaks down if you want the descriptions to be "wan0", "lan0", "lan1", etc.
But you could use "wan-0", "wan_0" or "WAN 0" or whatever.
Or is there an argument that descriptions ought to be able to look like names?

Weird constraint, imho. Breaks POLS.

"wan0", "lan0", "lan1" are character by character the descriptions I
envisioned using here when I first read the OP's mail.

That said, I would not set fire to anything in protest if those
descriptions aren't allowed.