(This is now a libpcap issue rather than an Ethereal issue, so I'm
sending it to "tcpdump-workers".)
> > I've never used Token Ring under AIX, so I'm not sure how that beast will
> > work.
>
> Hopefully, Token Ring on AIX supports DLPI. If it doesn't, it'd only be
> sniffable using BPF, and, as Craig says:
>
> > bpf under AIX is totally brain-dead and only supports
> > IBM's hacked and closed source version of tcpdump. Best to avoid /dev/bpf0
> > like the plague.
>
> so that may not work particularly well, either.
>
> I don't know whether Token Ring supports DLPI on AIX, however.
I infer from the page at
http://www.rs6000.ibm.com/doc_link/en_US/a_doc_lib/aixprggd/progcomc/ch2_dlpi.htm
that, at least on AIX 4.3, the Token Ring driver may use DLPI, as that's
a page discussing DLPI and it speaks of Token Ring and DLPI.
It also speaks of "/dev/dlpi/tr" and "/dev/dlpi/fi" as being devices for
Token Ring and FDDI; the page at
http://www.rs6000.ibm.com/doc_link/en_US/a_doc_lib/libs/commtrf2/dlpi.htm
says:
File System Name
Each provider supported by the dlpi driver has a unique name in
the file system. The supported interfaces are:
Driver Name Interface
/dev/dlpi/en Ethernet
/dev/dlpi/et 802.3
/dev/dlpi/tr 802.5
/dev/dlpi/fi FDDI
...
Physical Point of Attachment
The PPA is used to identify one of several of the same type of
interface in the system. It should be a nonnegative integer in
the range 0 through 99.
The dlpi drivers use the network interface drivers to access the
communication adapter drivers. For example, the /dev/dlpi/tr
file uses the network interface driver if_tr (interface tr0,
tr1, tr2, . . . ) to access the token-ring adapter driver.
The PPA value used attaches the device open instance with the
corresponding network interface. For example, opening to the
/dev/dlpi/en device and then performing an attach with PPA value
of 1 attaches this open instance to the network interface en1.
Therefore, choosing a PPA value selects a network interface.
The specific network interface should be active before a certain
PPA value is used.
Examples of client and server dlpi programs are located in the
/usr/samples/dlpi directory.
This isn't what libpcap expects for DLPI devices; it supports either
1) the model used on Solaris, where each provider has an entry
in "/dev" (e.g., "/dev/hme" for the Happy Meal Ethernet
interface - no, I'm not kidding, that's what "hme" stands for
on Suns), and the PPA is the unit number;
2) the model used on HP-UX, where at least some devices have
"/dev/dlpi" as the device for the provider, and you have to
go through a fair bit of work to dredge up the PPA for a
given interface name.
It doesn't support what the above claims is the AIX 4.3 model, where
each provider has an entry in "/dev/dlpi" (which is a directory, not a
character special file as I infer it is in AIX 4.3), and the PPA is the
unit number. (I guess the DLPI standard, whilst it may standardize the
STREAMS messages exchanged between DLPI providers and their clients,
doesn't standardize the names of the devices you use to get at those
providers.)
Craig, I seem to remember that you *did* get libpcap working with DLPI
on some version of AIX, without having added code to it to handle the
provider devices being in a "/dev/dlpi" subdirectory; is that the case,
and, on those other versions of AIX, were the provider devices in
"/dev", Solaris-style?
Arthur, is there a "/dev/dlpi/tr" device on your system?
-
This is the TCPDUMP workers list. It is archived at
http://www.tcpdump.org/lists/workers/index.html
To unsubscribe use mailto:[EMAIL PROTECTED]?body=unsubscribe
