Differential D29951 Diff 88054 documentation/content/el/books/handbook/advanced-networking/_index.adoc
Changeset View
Changeset View
Standalone View
Standalone View
documentation/content/el/books/handbook/advanced-networking/_index.adoc
Show First 20 Lines • Show All 1,022 Lines • ▼ Show 20 Lines | |||||
ubt0: Interface 1 (alt.config 5) endpoints: isoc-in=0x83, isoc-out=0x3, | ubt0: Interface 1 (alt.config 5) endpoints: isoc-in=0x83, isoc-out=0x3, | ||||
wMaxPacketSize=49, nframes=6, buffer size=294 | wMaxPacketSize=49, nframes=6, buffer size=294 | ||||
.... | .... | ||||
[NOTE] | [NOTE] | ||||
==== | ==== | ||||
The Bluetooth stack has to be started manually on FreeBSD 6.0, and on FreeBSD 5.X before 5.5. It is done automatically from man:devd[8] on FreeBSD 5.5, 6.1 and newer. | The Bluetooth stack has to be started manually on FreeBSD 6.0, and on FreeBSD 5.X before 5.5. It is done automatically from man:devd[8] on FreeBSD 5.5, 6.1 and newer. | ||||
Copy [.filename]#/usr/shared/examples/netgraph/bluetooth/rc.bluetooth# into some convenient place, like [.filename]#/etc/rc.bluetooth#. This script is used to start and stop the Bluetooth stack. It is a good idea to stop the stack before unplugging the device, but it is not (usually) fatal. When starting the stack, you will receive output similar to the following: | Copy [.filename]#/usr/share/examples/netgraph/bluetooth/rc.bluetooth# into some convenient place, like [.filename]#/etc/rc.bluetooth#. This script is used to start and stop the Bluetooth stack. It is a good idea to stop the stack before unplugging the device, but it is not (usually) fatal. When starting the stack, you will receive output similar to the following: | ||||
[source,shell] | [source,shell] | ||||
.... | .... | ||||
# /etc/rc.bluetooth start ubt0 | # /etc/rc.bluetooth start ubt0 | ||||
BD_ADDR: 00:02:72:00:d4:1a | BD_ADDR: 00:02:72:00:d4:1a | ||||
Features: 0xff 0xff 0xf 00 00 00 00 00 | Features: 0xff 0xff 0xf 00 00 00 00 00 | ||||
<3-Slot> <5-Slot> <Encryption> <Slot offset> | <3-Slot> <5-Slot> <Encryption> <Slot offset> | ||||
<Timing accuracy> <Switch> <Hold mode> <Sniff mode> | <Timing accuracy> <Switch> <Hold mode> <Sniff mode> | ||||
▲ Show 20 Lines • Show All 449 Lines • ▼ Show 20 Lines | |||||
A FreeBSD machine can boot over the network and operate without a local disk, using file systems mounted from an NFS server. No system modification is necessary, beyond standard configuration files. Such a system is relatively easy to set up because all the necessary elements are readily available: | A FreeBSD machine can boot over the network and operate without a local disk, using file systems mounted from an NFS server. No system modification is necessary, beyond standard configuration files. Such a system is relatively easy to set up because all the necessary elements are readily available: | ||||
* There are at least two possible methods to load the kernel over the network: | * There are at least two possible methods to load the kernel over the network: | ||||
** PXE: The Intel(R) Preboot eXecution Environment system is a form of smart boot ROM built into some networking cards or motherboards. See man:pxeboot[8] for more details. | ** PXE: The Intel(R) Preboot eXecution Environment system is a form of smart boot ROM built into some networking cards or motherboards. See man:pxeboot[8] for more details. | ||||
** The Etherboot port (package:net/etherboot[]) produces ROM-able code to boot kernels over the network. The code can be either burnt into a boot PROM on a network card, or loaded from a local floppy (or hard) disk drive, or from a running MS-DOS(R) system. Many network cards are supported. | ** The Etherboot port (package:net/etherboot[]) produces ROM-able code to boot kernels over the network. The code can be either burnt into a boot PROM on a network card, or loaded from a local floppy (or hard) disk drive, or from a running MS-DOS(R) system. Many network cards are supported. | ||||
* A sample script ([.filename]#/usr/shared/examples/diskless/clone_root#) eases the creation and maintenance of the workstation's root file system on the server. The script will probably require a little customization but it will get you started very quickly. | * A sample script ([.filename]#/usr/share/examples/diskless/clone_root#) eases the creation and maintenance of the workstation's root file system on the server. The script will probably require a little customization but it will get you started very quickly. | ||||
* Standard system startup files exist in [.filename]#/etc# to detect and support a diskless system startup. | * Standard system startup files exist in [.filename]#/etc# to detect and support a diskless system startup. | ||||
* Swapping, if needed, can be done either to an NFS file or to a local disk. | * Swapping, if needed, can be done either to an NFS file or to a local disk. | ||||
There are many ways to set up diskless workstations. Many elements are involved, and most can be customized to suit local taste. The following will describe variations on the setup of a complete system, emphasizing simplicity and compatibility with the standard FreeBSD startup scripts. The system described has the following characteristics: | There are many ways to set up diskless workstations. Many elements are involved, and most can be customized to suit local taste. The following will describe variations on the setup of a complete system, emphasizing simplicity and compatibility with the standard FreeBSD startup scripts. The system described has the following characteristics: | ||||
* The diskless workstations use a shared read-only [.filename]#/# file system, and a shared read-only [.filename]#/usr#. | * The diskless workstations use a shared read-only [.filename]#/# file system, and a shared read-only [.filename]#/usr#. | ||||
+ | + | ||||
The root file system is a copy of a standard FreeBSD root (typically the server's), with some configuration files overridden by ones specific to diskless operation or, possibly, to the workstation they belong to. | The root file system is a copy of a standard FreeBSD root (typically the server's), with some configuration files overridden by ones specific to diskless operation or, possibly, to the workstation they belong to. | ||||
▲ Show 20 Lines • Show All 127 Lines • ▼ Show 20 Lines | |||||
# gmake bin32/devicetype.fd0 | # gmake bin32/devicetype.fd0 | ||||
.... | .... | ||||
_devicetype_ depends on the type of the Ethernet card in the diskless workstation. Refer to the [.filename]#NIC# file in the same directory to determine the right _devicetype_. | _devicetype_ depends on the type of the Ethernet card in the diskless workstation. Refer to the [.filename]#NIC# file in the same directory to determine the right _devicetype_. | ||||
==== Booting with PXE | ==== Booting with PXE | ||||
By default, the man:pxeboot[8] loader loads the kernel via NFS. It can be compiled to use TFTP instead by specifying the `LOADER_TFTP_SUPPORT` option in [.filename]#/etc/make.conf#. See the comments in [.filename]#/usr/shared/examples/etc/make.conf# for instructions. | By default, the man:pxeboot[8] loader loads the kernel via NFS. It can be compiled to use TFTP instead by specifying the `LOADER_TFTP_SUPPORT` option in [.filename]#/etc/make.conf#. See the comments in [.filename]#/usr/share/examples/etc/make.conf# for instructions. | ||||
There are two other [.filename]#make.conf# options which may be useful for setting up a serial console diskless machine: `BOOT_PXELDR_PROBE_KEYBOARD`, and `BOOT_PXELDR_ALWAYS_SERIAL`. | There are two other [.filename]#make.conf# options which may be useful for setting up a serial console diskless machine: `BOOT_PXELDR_PROBE_KEYBOARD`, and `BOOT_PXELDR_ALWAYS_SERIAL`. | ||||
To use PXE when the machine starts, you will usually need to select the `Boot from network` option in your BIOS setup, or type a function key during the PC initialization. | To use PXE when the machine starts, you will usually need to select the `Boot from network` option in your BIOS setup, or type a function key during the PC initialization. | ||||
==== Configuring the TFTP and NFS Servers | ==== Configuring the TFTP and NFS Servers | ||||
If you are using PXE or Etherboot configured to use TFTP, you need to enable tftpd on the file server: | If you are using PXE or Etherboot configured to use TFTP, you need to enable tftpd on the file server: | ||||
▲ Show 20 Lines • Show All 153 Lines • ▼ Show 20 Lines | |||||
The isdn4bsd software allows you to connect to other ISDN routers using either IP over raw HDLC or by using synchronous PPP: either by using kernel PPP with `isppp`, a modified man:sppp[4] driver, or by using userland man:ppp[8]. By using userland man:ppp[8], channel bonding of two or more ISDN B-channels is possible. A telephone answering machine application is also available as well as many utilities such as a software 300 Baud modem. | The isdn4bsd software allows you to connect to other ISDN routers using either IP over raw HDLC or by using synchronous PPP: either by using kernel PPP with `isppp`, a modified man:sppp[4] driver, or by using userland man:ppp[8]. By using userland man:ppp[8], channel bonding of two or more ISDN B-channels is possible. A telephone answering machine application is also available as well as many utilities such as a software 300 Baud modem. | ||||
Some growing number of PC ISDN cards are supported under FreeBSD and the reports show that it is successfully used all over Europe and in many other parts of the world. | Some growing number of PC ISDN cards are supported under FreeBSD and the reports show that it is successfully used all over Europe and in many other parts of the world. | ||||
The passive ISDN cards supported are mostly the ones with the Infineon (formerly Siemens) ISAC/HSCX/IPAC ISDN chipsets, but also ISDN cards with chips from Cologne Chip (ISA bus only), PCI cards with Winbond W6692 chips, some cards with the Tiger300/320/ISAC chipset combinations and some vendor specific chipset based cards such as the AVM Fritz!Card PCI V.1.0 and the AVM Fritz!Card PnP. | The passive ISDN cards supported are mostly the ones with the Infineon (formerly Siemens) ISAC/HSCX/IPAC ISDN chipsets, but also ISDN cards with chips from Cologne Chip (ISA bus only), PCI cards with Winbond W6692 chips, some cards with the Tiger300/320/ISAC chipset combinations and some vendor specific chipset based cards such as the AVM Fritz!Card PCI V.1.0 and the AVM Fritz!Card PnP. | ||||
Currently the active supported ISDN cards are the AVM B1 (ISA and PCI) BRI cards and the AVM T1 PCI PRI cards. | Currently the active supported ISDN cards are the AVM B1 (ISA and PCI) BRI cards and the AVM T1 PCI PRI cards. | ||||
For documentation on isdn4bsd, have a look at [.filename]#/usr/shared/examples/isdn/# directory on your FreeBSD system or at the http://www.freebsd-support.de/i4b/[homepage of isdn4bsd] which also has pointers to hints, erratas and much more documentation such as the http://people.FreeBSD.org/~hm/[isdn4bsd handbook]. | For documentation on isdn4bsd, have a look at [.filename]#/usr/share/examples/isdn/# directory on your FreeBSD system or at the http://www.freebsd-support.de/i4b/[homepage of isdn4bsd] which also has pointers to hints, erratas and much more documentation such as the http://people.FreeBSD.org/~hm/[isdn4bsd handbook]. | ||||
In case you are interested in adding support for a different ISDN protocol, a currently unsupported ISDN PC card or otherwise enhancing isdn4bsd, please get in touch with {hm}. | In case you are interested in adding support for a different ISDN protocol, a currently unsupported ISDN PC card or otherwise enhancing isdn4bsd, please get in touch with {hm}. | ||||
For questions regarding the installation, configuration and troubleshooting isdn4bsd, a link:{freebsd-isdn-url}[freebsd-isdn] mailing list is available. | For questions regarding the installation, configuration and troubleshooting isdn4bsd, a link:{freebsd-isdn-url}[freebsd-isdn] mailing list is available. | ||||
=== ISDN Terminal Adapters | === ISDN Terminal Adapters | ||||
Terminal adapters (TA), are to ISDN what modems are to regular phone lines. | Terminal adapters (TA), are to ISDN what modems are to regular phone lines. | ||||
▲ Show 20 Lines • Show All 916 Lines • Show Last 20 Lines |