Remoteboot von MS-DOS clients

From: Wolfram Schneider <wosch(at)>
Date: Sun, 11 Aug 1996 16:53:50 +0200

Willi Zimmermann writes:
>tcpdump bekomme ich auch nicht zu laufen. Fehlermeldung /dev/bp0 nicht=20
>konfiguriert, ich kann damit nichts anfangen.

Du mußt den FreeBSD Kernel mit der entsprechenden Option für Berkeley
packet filter neu kompilieren.

[Aus dem Handbook (
Part 2: System Administration -> 5. Configuring the FreeBSD Kernel ->
-> 5.3. The Configuration File -> 5.3.8. Networking]

     pseudo-device bpfilter number

        Berkeley packet filter. This pseudo-device allows network
        interfaces to be placed in promiscuous mode, capturing every
        packet on a broadcast network (e.g. an ethernet). These packets
        can be captured to disk and/or examined with the tcpdump(1)
        program. Note that implementation of this capability can
        seriously compromise your overall network security. The number
        after bpfilter is the number of interfaces that can be examined
        simultaneously. Optional, not recommended except for those who
        are fully aware of the potential pitfalls. Not all network
        cards support this capability.

>an meinem Test-PC habe ich ein IDE-CD Laufwerk FX400 von MITSUMI das von=20
>FreeBSD nicht erkannt wird. Gibt es hierf=FCr eine L=F6sung.

[Handbook Part 1: 2. Installing FreeBSD]

  Due to limitations of the PC architecture, it is impossible for
  probing to be 100 percent reliable. In the event that your hardware
  is incorrectly identified, or that the probing causes your computer to
  lock up, first check the ``supported configurations'' section of
  this installation guide to be sure that your hardware is indeed
  supported by FreeBSD.

  If your hardware is supported, reset the computer and when the Boot:
  prompt comes up, type -c. This puts FreeBSD into a configuration mode
  where you can supply hints about your hardware. The FreeBSD kernel on
  the installation disk is configured assuming that most hardware
  devices are in their factory default configuration in terms of IRQs,
  IO addresses and DMA channels. If your hardware has been
  reconfigured, you will most likely need to use the -c option at boot
  to tell FreeBSD where things are.

  It is also possible that a probe for a device not present will cause a
  later probe for another device that is present to fail. In that case,
  the probes for the conflicting driver(s) should be disabled.

  In the configuration mode, you can:

  o List the device drivers installed in the kernel.

  o Disable device drivers for hardware not present in your system.

  o Change the IRQ, DRQ, and IO port addresses used by a device driver.

  While at the config> prompt, type help for more information on the
  available commands. After adjusting the kernel to match how you have
  your hardware configured, type quit at the config> prompt to continue
  booting with the new settings.

  After FreeBSD has been installed, changes made in the configuration
  mode will be permanent so you do not have to reconfigure every time
  you boot. Even so, it is likely that you will want to build a custom
  kernel to optimize the performance of your system. See ``Kernel
  configuration'' for more information on creating custom kernels.
Received on Sun 11 Aug 1996 - 18:46:18 CEST

search this site