EF(4) BSD Kernel Interfaces Manual EF(4)NAMEef — pseudo-device driver providing support for multiple ethernet frame
types
SYNOPSIS
pseudo-device efDESCRIPTION
The ef pseudo-device driver clones each ethernet type device with four
additional interfaces. Each of them capable to send or receive only one
predefined frame type.
Names for the new interfaces created by adding fN suffix to an existing
device name. Where N is a device unit which can have one of the following
values:
0 interface with an Ethernet_II frame
1 interface with a Novell Ethernet_802.3 frame
2 interface with an Ethernet_802.2 frame
3 interface with an Ethernet_802.2/SNAP frame support.
For example, device ed0 will be populated with four devices: ed0f0,
ed0f1, ed0f2 and ed0f3.
After that, each device can be configured as usually:
# ifconfig ed0f1 ipx 0x105
This will configure IPX protocol with network number 0x105 and
Ethernet_802.3 frame type.
Please note that it is impossible to configure IPX protocol on the 'raw'
ed0 device after if_ef.ko driver loaded.
EXAMPLES
The ef driver can be loaded via loader.conf(5) file:
if_ef_load="YES"
In this case an ordinary interface configuration commands can be used in
the rc.conf(5) file:
network_interfaces="ed2 lo0 tun0 ed2f0 ed2f1"
ifconfig_ed2f0_ipx="ipx 0x101"
ifconfig_ed2f1_ipx="ipx 0x102"
DIAGNOSTICS
None.
CAVEATS
Avoid to configuring 'raw' ethernet device for IPX protocol after ef
driver is loaded.
SEE ALSOipx(3), ifconfig(8)AUTHORS
Boris Popov ⟨bp@FreeBSD.org⟩.
BSD June 20, 1999 BSD