Visit Our UNIX and Linux User Community

Linux and UNIX Man Pages

Test Your Knowledge in Computers #445
Difficulty: Easy
Scientific Linux has been loaded onto systems at the International Space Station.
True or False?
Linux & Unix Commands - Search Man Pages

fwe(4) [bsd man page]

FWE(4)							   BSD Kernel Interfaces Manual 						    FWE(4)

NAME
fwe -- Ethernet emulation driver for FireWire SYNOPSIS
To compile this driver into the kernel, place the following lines in your kernel configuration file: device firewire device fwe Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5): if_fwe_load="YES" DESCRIPTION
The fwe driver provides non-standard Ethernet emulation over FireWire (IEEE 1394). firewire(4) and fwohci(4) must be configured in the kernel as well. This driver exploits asynchronous stream over IEEE 1394 to carry Ethernet frames. The stream channel can be specified by the hw.firewire.fwe.stream_ch sysctl(8). This driver supports polling(4) as well if it is compiled with the DEVICE_POLLING option. SEE ALSO
arp(4), firewire(4), fwip(4), fwohci(4), netintro(4), ng_ether(4), polling(4), ifconfig(8), kldload(8), sysctl(8) HISTORY
The fwe device driver first appeared in FreeBSD 5.0. AUTHORS
The fwe driver and this manual page were written by Hidetoshi Shimokawa. BUGS
This driver emulates Ethernet in a very adhoc way and it does not reserve a stream channel using an isochronous manager. Note that this driver uses a protocol which is very different from RFC 2734 (IPv4 over IEEE 1394). BSD
July 16, 2005 BSD

Check Out this Related Man Page

FWOHCI(4)						   BSD Kernel Interfaces Manual 						 FWOHCI(4)

NAME
fwohci -- OHCI FireWire chipset device driver SYNOPSIS
To compile this driver into the kernel, place the following line in your kernel configuration file: device firewire Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5): firewire_load="YES" To disable physical access (see BUGS section for detail), put the following line in loader.conf(5): hw.firewire.phydma_enable=0 HARDWARE
The fwohci driver provides support for PCI/CardBus FireWire interface cards. The driver supports the following IEEE 1394 OHCI chipsets: o Adaptec AHA-894x/AIC-5800 o Apple Pangea o Apple UniNorth o Intel 82372FB o IOGEAR GUF320 o Lucent / Agere FW322/323 o NEC uPD72861 o NEC uPD72870 o NEC uPD72871/2 o NEC uPD72873 o NEC uPD72874 o National Semiconductor CS4210 o Ricoh R5C551 o Ricoh R5C552 o Sony CX3022 o Sony i.LINK (CXD3222) o Sun PCIO-2 (RIO 1394) o Texas Instruments PCI4410A o Texas Instruments PCI4450 o Texas Instruments PCI4451 o Texas Instruments TSB12LV22 o Texas Instruments TSB12LV23 o Texas Instruments TSB12LV26 o Texas Instruments TSB43AA22 o Texas Instruments TSB43AB21/A/AI/A-EP o Texas Instruments TSB43AB22/A o Texas Instruments TSB43AB23 o Texas Instruments TSB82AA2 o VIA Fire II (VT6306) SEE ALSO
firewire(4), fwe(4), fwip(4), sbp(4), fwcontrol(8), kldload(8) HISTORY
The fwohci device driver first appeared in FreeBSD 5.0. AUTHORS
The fwohci device driver was written by Katsushi Kobayashi and Hidetoshi Shimokawa. BUGS
The driver allows physical access from any nodes on the bus by default. This means that any devices on the bus can read and modify any mem- ory space which can be accessed by an IEEE 1394 OHCI chip. It is allowed mostly for sbp(4) devices. This should be changed to allow it only for specific devices. Anyway, FireWire is a bus and not expected to be connected with un-trustable devices because a node can monitor all the traffic. BSD
March 3, 2008 BSD

Featured Tech Videos