Operating System - Tru64 Unix
1828138 Members
2579 Online
109975 Solutions
New Discussion

Problems with tcpdump

 
aladar
Occasional Contributor

Problems with tcpdump

tcpdump ends with following error
message:
tcpdump: pfopen: tu0: No such file or directory
tcpdump: your system may not be properly configured; see "man packetfilter"

I have included packet filter support
in the kernel, but no pfilt*** special files
in /dev/pf. What have I do, is calling
'MAKEDEV pfilt' enough, or should I
register created special files somehow
with dsfmgr?

Thanks a lot for advise, ...
10 REPLIES 10
Johan Brusche
Honored Contributor

Re: Problems with tcpdump


cd /dev
./MAKEDEV pfilt

is enough to be able to work with tcpdump.

Johan.

_JB_
Michael Schulte zur Sur
Honored Contributor

Re: Problems with tcpdump

Hi,

since it is not clear, whether you use 4.0X or 5.XX, in 4.0X I think you have to have
options PACKETFILTER
in the config file.

greetings,

Michael
Michael Schulte zur Sur
Honored Contributor

Re: Problems with tcpdump

Well,

forget my last post. I saw too late, that you thought about it already.

Michael
aladar
Occasional Contributor

Re: Problems with tcpdump

When I'm doing such a tash
like 'MAKEDEV pfilt' should I
do it in single user mode,
or it is not necessary?
Michael Schulte zur Sur
Honored Contributor

Re: Problems with tcpdump

Hi,

this would be quite annoying, if you had to bring down the machine for peanuts. No, you can do it anytime. ;-)

greetings,

Michael
Arnaud Veron
Valued Contributor

Re: Problems with tcpdump

don't forget to issue the following command too : pfconfig +p +c tu0
Daniel Pernia
New Member

Re: Problems with tcpdump

Thanks for let me in. I got a sililar problem. We have OS Tru64Unix 4.0F, installed in a Alpha Server.

Well the problem is, in a Historical Server, we have Installed a tapebackup Unit. At this moment we can not acces to the tape backup.

I already checked the /dev traying to find the logical devices nrmt0h, nrmt0a, nrmt0l, nrmt0m, but they are not there.

Eventhout if we look for the raw devices i can get it.
rmt0h, rmt0a/0m/0l,
When i run the MAKEDEV tz14, in order to create the device, i get nrm1h, nrmt1a, ***
if i try again i get nrm2h, nrmt2a, ***.

What can i do to run the MAKEDEV and obtain the right devices, i mean , nrm0h, **

I´m sorry for my write English.
Danie
Johan Brusche
Honored Contributor

Re: Problems with tcpdump

Dani,

So you have the rmt0* (ie the "rewind") special files , but not the nrmt0* (non-rewind) special files.

I guess you will have to delete them all ie:
cd /dev
rm *rmt0*
and then
./MAKEDEV tz14 (if your tape is on bus 1, target 6)

Rgds,
Johan.

_JB_
Michael Schulte zur Sur
Honored Contributor

Re: Problems with tcpdump

Hi,

I would try it a little different.
cd /dev
rm *rmt*
scu show edt
calculate bus*8+target of tape.
./MAKEDEV tz"result"
mt -f /dev/nrmt0h status

greetings,

Michael
Daniel Pernia
New Member

Re: Problems with tcpdump

Thanks for all support given,
I got the solution.
1.- I make a dir into /dev, called /dev/tapedp, then i moved all rmt0* to that directory, and then i rebooted the machine.

2.- After the boot, the initializacion created it seft , the raw devices for the tape backup.
3.- Then when i checked the raw devices, i got the rmt* and the nrmt*.

Again i appreciat all the support given .
Thank at all.
Daniel