> Hi All,
> each time I start tcpdump on HPUX11.0 (32 bit, 64 bit) I get the following
> error.
> tcpdump: WARNING: SIOCGIFADDR: dlpi1: Invalid argumen
>
> Is this a normal error?
If you start tcpdump with a "dlpi" device, it's "normal" in the sense
that it's expected to happen; there are no network interfaces on HP
systems with names that begin with "dlpi" - they have names like "lan0".
libpcap (the library that tcpdump uses) assumes that it can use the
device name supplied to it as a network interface name; that doesn't
work with "dlpi" devices.
> How can I fix it?
Step 1: if the version of tcpdump and libpcap you're running isn't one
of the CVS snapshots from tcpdump.org and isn't from CVS, download one
of the snapshots from tcpdump.org, configure and build libpcap, and
then configure and build tcpdump.
This gives you an improved version of the HP-UX support in libpcap,
which fixes it so that it *can* take interface names as names of devices
on which to capture, rather than requiring you to give a "dlpiN" name.
Step 2: when you run tcpdump, do *NOT* give it "/dev/dlpi1" or "dlpi1"
or anything such as that as the name of the device on which to capture.
If you have only one network interface on your machine, tcpdump
shouldn't require you to specify a device with "-i" - it should use that
one interface by default.
If you have more than one interface, tcpdump should work with "-i" -
it'll probably pick "lan0" as the interface. If the interface it
chooses isn't the one you want, use a "-i" flag, giving the name you
want.
Unfortunately, HP-UX doesn't appear to support "ifconfig -a" as a way of
getting the names of all the interfaces (paging Rick Jones - almost
everybody else does it, see if you can get HP to do it...), so you'd
have to run "/usr/sbin/lanscan". You'd get output such as
Hardware Station Crd Hdw Net-Interface NM MAC HP-DLPI DLPI
Path Address In# State NamePPA ID Type Support Mjr#
8/12/2/0 0x0060B04B835F 2 UP lan2 snap2 1 ETHER Yes 119
10/12/6 0x0060B0830231 0 UP lan0 snap0 2 ETHER Yes 119
8/12/1/0 0x0060B04B835E 1 UP lan1 snap1 3 ETHER Yes 119
The names under "Net-Interface NamePPA" are the ones to use, e.g.
"lan0", "lan1", "lan2".
> if I leave it the way it is, what
> kind of problems should I expect to face. will it affect bp filtering in any
> way?
Yes, it will - it can make filters that require the IP address or
netmask of the interface, such as "ip broadcast", not work, as they
won't have the netmask of the interface and probably won't check the
right bits.
It may also make the "-f" flag not work (as the netmask is used to
determine what a "foreign" Internet address is).
-
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
