summaryrefslogtreecommitdiff
path: root/pcap_lookupdev.3pcap
Commit message (Collapse)AuthorAgeFilesLines
* Add support for UTF-8 strings on Windows.Guy Harris2020-04-111-0/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add a routine pcap_init() that initializes pcap, specifying whether strings should be treated as being in UTF-8 or a local character encoding. On UN*Xes, we don't change our behavior based on that setting; if there is ever an issue with local character encodings *other* than UTF-8, we can use it. On Windows, the local character encoding is the local ANSI code page; if pcap_init() isn't called, or is called with PCAP_CHAR_ENC_LOCAL, strings are treated as being in the current ANSI code page, as before, otherwise they're treated as being in UTF-8. This includes file path names and error messages. In addition, if pcap_init() is called, regardless of the options, we disable pcap_lookupdev(), making it always return NULL, as it retunred *UTF-16LE* strings (plural!) on Windows NT, and pcap_create() had to check for UTF-16LE strings to work around that. That workaround is unsafe (it will read past the end of the input string if the string is one ASCII character), and is also disabled if pcap_init() is called. We also make rpcapd send UTF-8 error message strings over the wire; sending local code page strings is a Bad Idea, as the client has no idea what the server's code page is. (Do not assume the client and server are necessarily in the same location.) Fix the capitalization of "Winsock" while we're at it; Microsoft appears to spell it "Winsock", rather than "WinSock".
* Style cleanup.Guy Harris2019-11-231-5/+5
| | | | | | | | Use the BSD house style, in which, in foobar() returns 17 on success and 137 on failure. "foobar" is boldfaced but "()" isn't.
* Fix manpage reference formatting to be consistent.Daniel Miller2018-08-241-5/+5
| | | | | | | All manpage references such as pcap_create(3PCAP) will now be formatted with the identifier (e.g. "pcap_create") in **bold** and the section name (e.g. "(3PCAP)") in roman (default) face. This is how most manpages seem to be formatted and makes things more consistent.
* Refine references in some man pages, round 2.Denis Ovsienko2018-07-171-6/+5
| | | | [skip ci]
* Update the timestamp in some man pages.Denis Ovsienko2018-07-111-1/+1
| | | | | | | | In the man pages that since the previous timestamp had meaningful (i.e. not typos or whitespace fixups) changes set the timestamp to the date of such last meaningful change. [skip ci]
* Deprecate this function, and indicate why it's not a good function.Guy Harris2017-09-081-1/+21
|
* update last modified date in man page(s)Denis Ovsienko2015-12-181-1/+1
|
* remove libpcap's own CVS keywordsDenis Ovsienko2014-01-031-2/+0
| | | | | | This change removes CVS keywords that express that the file belongs to libpcap repository. All such keywords represented the revision and timestamp by the end of 2008 or even older.
* Document the new API's, move a bunch of information about libpcapguy2008-04-061-3/+8
| | | | | | concepts to the pcap(3PCAP) man page, refer people to the pcap(3PCAP) man page from the man pages for libpcap functions, and clean up some errors.
* Include <pcap/pcap.h> in the SUMMARY sections - as long as we're goingguy2008-04-051-2/+2
| | | | | | | to 1.0, might as well go with the place where Red Hat stuck the header at one point and where the header "officially" resides. (We should put a "backwards compatibility" note into pcap.3pcap.)
* Split the pcap(3) man page into a bunch of individual man pages forguy2008-04-051-0/+57
functions plus an overall man page for libpcap, and put them all into section 3PCAP. That means you can actually do "man pcap_open_live" and get something meaningful, rather than having to do "man pcap" and then scroll through all the other stuff in the man page.
View Lorry Controller Status