diff options
| author | Cal Peake | 2006-04-01 01:46:12 +0200 |
|---|---|---|
| committer | Adrian Bunk | 2006-04-01 01:46:12 +0200 |
| commit | 3d79c33bbd1dd12d420fd84facfd0ba96261e595 (patch) | |
| tree | ecedc7d60e146b6509f75f5634325098bf326a3e | |
| parent | 6585fa8aa58c7cd9f90f1c795a9dfc8db5f13906 (diff) | |
BFP->BPF in Documentation/networking/tuntap.txt
BFP should be BPF (BSD Packet Filter)
Signed-off-by: Cal Peake <cp@absolutedigital.net>
Signed-off-by: Adrian Bunk <bunk@stusta.de>
| -rw-r--r-- | Documentation/networking/tuntap.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/networking/tuntap.txt b/Documentation/networking/tuntap.txt index ec3d109d787a..76750fb9151a 100644 --- a/Documentation/networking/tuntap.txt +++ b/Documentation/networking/tuntap.txt @@ -138,7 +138,7 @@ This means that you have to read/write IP packets when you are using tun and ethernet frames when using tap. 5. What is the difference between BPF and TUN/TAP driver? -BFP is an advanced packet filter. It can be attached to existing +BPF is an advanced packet filter. It can be attached to existing network interface. It does not provide a virtual network interface. A TUN/TAP driver does provide a virtual network interface and it is possible to attach BPF to this interface. |