09-16-2010
Usually ifconfig <interface> shows lot of details like dropped pkts, collisions etc. Do you need even more details ?
-Raja
9 More Discussions You Might Find Interesting
1. IP Networking
Not sure if this is the right section for this. Move if necessary
Hey guys,
Just wanting to know if anyone has had a similar experience.
I have a FreeBSD 4.8 gateway machine with a dual boot win98/FreeBSD machine connected to it. When I'm in windows and playing a game, Diablo II or Star... (11 Replies)
Discussion started by: BSeanD
11 Replies
2. SCO
I have got a Sco Unix Server, i want to connect some windows workstations. What configurations do i need to make on server and or workstation? (1 Reply)
Discussion started by: tpurazi1
1 Replies
3. UNIX for Dummies Questions & Answers
Hello,
I have been having a problem with printing to a network printer on my LAN, I am able to ping all ports from the server and the printer. Print request just stay in the print que the only way to print is from the parallel line to the server. Any ideas on what can be going wrong?? Lp sched is... (1 Reply)
Discussion started by: ostac
1 Replies
4. Solaris
Hi
I had installed Sun Solaris 10 on my dell vostro 1400.Problem is iam unable to mount the usb drives as there was no detections at all.And also iam unable to find my network interface or iam not able to install the network card.
If try to type ifconfig -a
It is showing only loop back... (4 Replies)
Discussion started by: testerindia25
4 Replies
5. UNIX for Dummies Questions & Answers
Hello everyone,
In a script, I am using SCP to copy huge file to another host.
scp -qrp hugefile.txt /opt/perf05/tmp
However, we have noticed that this file is not being copied. I am suspecting this was because we are losing connection while copying this... (1 Reply)
Discussion started by: qwarentine
1 Replies
6. IP Networking
Hello,
I'm attempting to setup a test network with a client-server based architecture using a proprietary application. The client works by communicating with the server on separate links (typically cellular connections) and then initiates a tunnel over each active link. However, in place of the... (0 Replies)
Discussion started by: shadyuk
0 Replies
7. HP-UX
Newbie with UNIX here.
Currently troubleshooting a UNIX terminal we have.
I determined it to be bad and swapped it out with a known good terminal. I went in and changed the IP address and host name to reflect the old terminal. Although now there is no connectivity.
I swapped out the NIC... (1 Reply)
Discussion started by: kevinlord190
1 Replies
8. SuSE
Hi Guys,
I have two databases where I copy archivelog files from server A to server B frequently...yesterday we did the VM upgrade now...I am struggling to copy/ship the files from server A to server B...
I manually tested the file transfer but the big files, e.g 46M, stall. I can copy small... (2 Replies)
Discussion started by: Phuti
2 Replies
9. Emergency UNIX and Linux Support
Oflate we are finding a few servers experiencing severe slowness. What would be the commands that I need to try to postmortem the situation? (3 Replies)
Discussion started by: ggayathri
3 Replies
PBFIFO(8) Linux PBFIFO(8)
NAME
pfifo - Packet limited First In, First Out queue
bfifo - Byte limited First In, First Out queue
SYNOPSIS
tc qdisc ... add pfifo [ limit packets ]
tc qdisc ... add bfifo [ limit bytes ]
DESCRIPTION
The pfifo and bfifo qdiscs are unadorned First In, First Out queues. They are the simplest queues possible and therefore have no overhead.
pfifo constrains the queue size as measured in packets. bfifo does so as measured in bytes.
Like all non-default qdiscs, they maintain statistics. This might be a reason to prefer pfifo or bfifo over the default.
ALGORITHM
A list of packets is maintained, when a packet is enqueued it gets inserted at the tail of a list. When a packet needs to be sent out to
the network, it is taken from the head of the list.
If the list is too long, no further packets are allowed on. This is called 'tail drop'.
PARAMETERS
limit Maximum queue size. Specified in bytes for bfifo, in packets for pfifo. For pfifo, defaults to the interface txqueuelen, as speci-
fied with ifconfig(8) or ip(8). The range for this parameter is [0, UINT32_MAX].
For bfifo, it defaults to the txqueuelen multiplied by the interface MTU. The range for this parameter is [0, UINT32_MAX] bytes.
Note: The link layer header was considered when counting packets length.
OUTPUT
The output of tc -s qdisc ls contains the limit, either in packets or in bytes, and the number of bytes and packets actually sent. An
unsent and dropped packet only appears between braces and is not counted as 'Sent'.
In this example, the queue length is 100 packets, 45894 bytes were sent over 681 packets. No packets were dropped, and as the pfifo queue
does not slow down packets, there were also no overlimits:
# tc -s qdisc ls dev eth0
qdisc pfifo 8001: dev eth0 limit 100p
Sent 45894 bytes 681 pkts (dropped 0, overlimits 0)
If a backlog occurs, this is displayed as well.
SEE ALSO
tc(8)
AUTHORS
Alexey N. Kuznetsov, <kuznet@ms2.inr.ac.ru>
This manpage maintained by bert hubert <ahu@ds9a.nl>
iproute2 10 January 2002 PBFIFO(8)