11-07-2011
How does a NIC driver activate with upper layer mutually?
Hi, all:
How can I know whether the packets recieved from network by my own NIC driver are transmitted to upper layer(IP layer) or not?
How can I know if the packets come from upper layer are passed to my own NIC driver and go out further?
Is there any shell command or utility show that information?
The symptom of my running driver is as if the driver is seperated from the upper layer comletely! The "ping" or "scp" command cannot go through the driver and the received packets by the driver cannot pass to upper layer!
thanks!
li, kunlun
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I'm way confused. I loaded RH 7.1 on an old P-75 Compaq. IT has an EtherExpress pro/100 card in it and I have that attached to the optional port on our firewall with a crossover....I can't seem to get the card to negotiate with the firewall...it's currently 100Meg at Half duplex. I'm at a loss... (3 Replies)
Discussion started by: kwalter
3 Replies
2. UNIX for Advanced & Expert Users
Hi:-
I am trying to install a device driver for Intel NIC card on TurboLinux, but getting following errors,
cc -O -Wall -o eepro100-diag eepro100-diag.c
eepro100-diag.c:72: unistd.h: No such file or directory
eepro100-diag.c:73: stdio.h: No such file or directory
eepro100-diag.c:74:... (1 Reply)
Discussion started by: s_aamir
1 Replies
3. IP Networking
Hi
I need to know how a driver for a network interface card works, I want to learn the basic principles since I know that every driver has its specific implementation.
For example when we speak about the scheduler, we can read an operating system book and learn general design concepts e.g.... (0 Replies)
Discussion started by: Puntino
0 Replies
4. SuSE
Hi All,
I got the following errors when i was trying to restart Infiniband service.
Loading cxgb3 driver :
Loading HCA driver and Access Layer :
The command managed to bring up the services, but without RDMA modules loaded from /etc/init.d/openibd status output. Is the missing of RDMA... (0 Replies)
Discussion started by: dchm
0 Replies
5. SCO
hi
I have a fresh installation of SCO 5.0.6 and I have download a NIC driver for Intel Pro 1000:
ftp://ftp.sco.com/pub/openserver5/507/drivers/eeG_5.0.7g/VOL.000.000
Howto install it using floppy?
---------- Post updated at 04:02 PM ---------- Previous update was at 02:18 PM... (0 Replies)
Discussion started by: ccc
0 Replies
6. Red Hat
Guys,
Can you help me how to verify the current installed NIC driver version in RHEL5.3?
Thanks.:D (1 Reply)
Discussion started by: shtobias
1 Replies
7. Solaris
I couldn't install my nic in solaris 10. I compiled and added
the driver but failed to attach the driver and ifconfig output
shows only loopback dev. Please see the following output and tell
me whether my nic has been detected and why the driver failed to
attach?
My nic is detected in linux... (0 Replies)
Discussion started by: vectrum
0 Replies
8. Solaris
Hi guys
My friend needs nfo driver for his Solaris box. I installed that driver for myself from scratch and he needs that driver in SVR4 format. I downloaded source code and run make and this is the point I don't how to proceed.
How can I recognize which needs go to the package ?
Does make... (0 Replies)
Discussion started by: solaris_user
0 Replies
9. Programming
Hi, all:
My writed NIC driver for rtl8139d adapter on linux 3.0.4 cannot send and recieve simultaneously but is able to send or recieve in parallel respectively. As soon as it send and recieve at the same time, the transmmition rate on both directions gradually decrease to zero b/s and report... (1 Reply)
Discussion started by: liklstar
1 Replies
10. Solaris
In Solaris 10 it was easy, a simple grep through modinfo output and you'd have the version of any loaded module, including your NIC drivers. In my career I've seen many people relying on this information in their scripts. Now I'm on Solaris 11, and where have the version numbers gone? The... (0 Replies)
Discussion started by: cambridge
0 Replies
XPT(4) BSD Kernel Interfaces Manual XPT(4)
NAME
xpt -- CAM transport layer interface
SYNOPSIS
None.
DESCRIPTION
The xpt driver provides a way for userland applications to issue certain CAM CCBs to the kernel.
Since the xpt driver allows direct access to the CAM subsystem, system administrators should exercise caution when granting access to this
driver. If used improperly, this driver can allow userland applications to crash a machine or cause data loss.
KERNEL CONFIGURATION
There is no kernel configuration required for the xpt driver. It is enabled when SCSI support is enabled in the kernel. There is one
instance of the xpt driver per CAM transport layer instance. Since there is currently only one CAM transport layer, there will only be one
instance of this driver.
IOCTLS
CAMIOCOMMAND This ioctl takes certain kinds of CAM CCBs and passes them through to the CAM transport layer for action. Only the following
CCB types are supported:
XPT_SCAN_BUS
XPT_RESET_BUS
XPT_SCAN_LUN
XPT_ENG_INQ
XPT_ENG_EXEC
XPT_DEBUG
XPT_DEV_MATCH
XPT_PATH_INQ
The above CCBs are the only ones supported since it makes more sense to send them through a generic passthrough device rather
than a passthrough device tied to a particular underlying SCSI device.
CAMGETPASSTHRU This ioctl takes an XPT_GDEVLIST CCB, and returns the passthrough device corresponding to the device in question.
FILES
/dev/xpt0 Character device node for the xpt driver.
DIAGNOSTICS
None.
SEE ALSO
cam(3), cam_cdbparse(3), pass(4), camcontrol(8)
HISTORY
The CAM transport layer driver first appeared in FreeBSD 3.0.
AUTHORS
Kenneth Merry <ken@FreeBSD.org>
BSD October 10, 1998 BSD