Hallo,
ich möchte gerne eine bluetooth PAN (private area network) einrichten, um mit meinem IPAQ PocketPC via BT auf den webserver meines vdr zugreifen zu können (für live, Display o.a. für Musik-Server etc). Als Testsystem benutze ich zuerst Ubuntu 9.04 und später soll es dann auf einem easyvdr 0.6 laufen. Mein Problem ist, dass ich trotz Anleitung nicht auf das Internet zugreifen kann. Jetzt kommen erstmal ein "paar" Infos zur Konfiguration und Log-Einträge.
Mein Bt-Dongle wird schonmal erkannt:
Code
xxx@xxx:~$ hciconfig -a
hci0: Type: USB
BD Address: 00:02:5B:01:03:21 ACL MTU: 384:8 SCO MTU: 64:8
UP RUNNING PSCAN
RX bytes:1098 acl:0 sco:0 events:44 errors:0
TX bytes:437 acl:0 sco:0 commands:44 errors:0
Features: 0xff 0xff 0x8f 0xfe 0x9b 0xf9 0x00 0x80
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: 'jolly-desktop-0'
Class: 0x0a0104
Service Classes: Networking, Capturing
Device Class: Computer, Desktop workstation
HCI Ver: 2.0 (0x3) HCI Rev: 0x7a6 LMP Ver: 2.0 (0x3) LMP Subver: 0x7a6
Manufacturer: Cambridge Silicon Radio (10)Danach bin ich erstmal nach dieser Anleitung vorgegangen. Die geänderten Dateien auf dem Ubuntusystem sehen dann wie folgt aus:
Die hcid.conf gibt es bei Ubuntu 9 nicht mehr, deshalb in /etc/bluetooth/main.conf (anscheinend der Ersatz für hcid.conf):
Code
[General]
# List of plugins that should not be loaded on bluetoothd startup
#DisablePlugins = network,input
# Default adaper name
# %h - substituted for hostname
# %d - substituted for adapter id
Name = %h-%d
#selber eingefuegt für bt pan
lm = accept, master
# Default device class. Only the major and minor device class bits are
# considered.
Class = 0x000100
# How long to stay in discoverable mode before going back to non-discoverable
# The value is in seconds. Default is 180, i.e. 3 minutes.
# 0 = disable timer, i.e. stay discoverable forever
DiscoverableTimeout = 0
# How long to stay in pairable mode before going back to non-discoverable
# The value is in seconds. Default is 0.
# 0 = disable timer, i.e. stay pairable forever
PairableTimeout = 0
# Use some other page timeout than the controller default one
# which is 16384 (10 seconds).
PageTimeout = 8192
# Discover scheduler interval used in Adapter.DiscoverDevices
# The value is in seconds. Defaults is 0 to use controller scheduler.
DiscoverSchedulerInterval = 0
# What value should be assumed for the adapter Powered property when
# SetProperty(Powered, ...) hasn't been called yet. Defaults to true
InitiallyPowered = true
# Remember the previously stored Powered state when initializing adapters
RememberPowered = true
# Use vendor, product and version information for DID profile support.
# The values are separated by ":" and VID, PID and version.
#DeviceID = 1234:5678:abcd
# Do reverse service discovery for previously unknown devices that connect to
# us. This option is really only needed for qualification since the BITE tester
# doesn't like us doing reverse SDP for some test cases (though there could in
# theory be other useful purposes for this too). Defaults to true.
ReverseServiceDiscovery = true/etc/default/bluetooth
Code
# Defaults for bluez
# start bluetooth on boot?
# compatibility note: If this variable is not found bluetooth will
# start
BLUETOOTH_ENABLED=1
#selber eingefuegt für bluetooth PAN
PAND_ENABLED=1
PAND_OPTIONS="--listen --role=NAP --devup /etc/bluetooth/pan/dev-up"
# This setting will switch HID devices (e.g mouse/keyboad) to HCI mode, that is
# you will have bluetooth functionality from your dongle instead of only HID.
# Note that not every bluetooth dongle is capable of switching back to HID
# mode, see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=355497
HID2HCI_ENABLED=1
HID2HCI_UNDO=1/etc/bluetooth/pan/dev-up
Bash
#!/bin/sh
echo 1 > /proc/sys/net/ipv4/ip_forward
ifup bnep0
sleep 2
/etc/init.d/dhcp3-server restart/etc/network/interfaces
Code
auto lo
iface lo inet loopback
# eringefuegt für bluetooth pan
iface bnep0 inet static
address 192.168.254.1
netmask 255.255.255.240
post-up iptables -t nat -A POSTROUTING -s 192.168.254.0/24 -j MASQUERADE
post-up iptables -A FORWARD -i bnep0 -o eth0 -j ACCEPT
post-up iptables -A FORWARD -o bnep0 -i eth0 -j ACCEPT
pre-down /etc/init.d/dhcp3-server stop
Hier habe ich die Adresse geändert, damit das PAN besser ins lokale Netz passt (192.168.0.xxx). Kann man das so machen?
Code
# The ddns-updates-style parameter controls whether or not the server will
# attempt to do a DNS update when a lease is confirmed. We default to the
# behavior of the version 2 packages ('none', since DHCP v2 didn't
# have support for DDNS.)
ddns-update-style none;
# option definitions common to all supported networks...
# option domain-name "example.org";
# option domain-name-servers ns1.example.org, ns2.example.org;
#eingefuegt für bluetooth pan
option domain-name "search.b.superkabel.de";
option domain-name-servers 83.169.184.161, 83.169.184.225, 192.168.0.1;
default-lease-time 600;
max-lease-time 7200;
#eingefuegt für bluetooth pan
subnet 192.168.254.0 netmask 255.255.255.0 {
range 192.168.254.1 192.168.254.10;
option domain-name-servers 192.168.1.1;
option domain-name "bluetoothap.int.yourdomain.com";
option routers 192.168.254.1;
option broadcast-address 192.168.254.255;
default-lease-time 600;
max-lease-time 7200;
}
Die IPs sind angepasst an das Schema aus der Antleitung. Kann man als domain wählen, was man will?
Vielleicht ist auch noch diese Datei von Interesse
/etc/bluetooth/network.conf :
Code
# Configuration file for the network service
# This section contains options which are not specific to any
# particular interface
[General]
# Disable link encryption: default=false
#DisableSecurity=true
[PANU Role]
# Network interface name for PANU for connections. default:bnep%d
# (up to 16 characters)
# Do reverse service discovery for previously unknown devices that connect to
# us. This option is really only needed for qualification since the BITE tester
# doesn't like us d
#Interface=
# PAN user connection interface up script. default:none
Script=avahi-autoipd
[GN Role]
# Network Interface name for Group Network server. default:pan0
#Interface=
# Group Network connection interface up script. default:none
Script=avahi-autoipd
[NAP Role]
# Network Interface name for Network Access Point server. default:pan1
Interface=pan0
# Network Access Point connection interface up script. default:none
Script=dhclientNun soll ich laut Anleitung mit dem PDA über den PC ins Netz. Tut aber nicht !? Ich kann PDA und PC pairen und der PDA findet auch einen BlueZ NAP service, den ich verbinden kann. Der PDA sagt, das alles in Ordnung ist (Konnektivität Internet verbunden). Aber ich komme nicht ins Netz. Hier noch mal ein paar relevante syslog Einträge nach dem booten:
Code
Jul 11 14:09:07 xxx bluetoothd[2973]: Bluetooth daemon
Jul 11 14:09:07 xxx bluetoothd[2973]: Starting SDP server
Jul 11 14:09:07 xxx kernel: [ 17.511808] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Jul 11 14:09:07 xxx kernel: [ 17.511811] Bluetooth: BNEP filters: protocol multicast
Jul 11 14:09:07 xxx bluetoothd[2973]: bridge pan0 created
Jul 11 14:09:07 xxx bluetoothd[2973]: Starting experimental netlink support
Jul 11 14:09:07 xxx bluetoothd[2973]: Failed to find Bluetooth netlink family
Jul 11 14:09:07 xxx kernel: [ 17.551616] Bridge firewalling registered
Jul 11 14:09:07 xxx bluetoothd[2973]: Registered interface org.bluez.Service on path /org/bluez/2973/any
Jul 11 14:09:07 xxx bluetoothd[2973]: HCI dev 0 registered
Jul 11 14:09:07 xxx bluetoothd[2973]: HCI dev 0 up
Jul 11 14:09:07 xxx bluetoothd[2973]: Starting security manager 0
Jul 11 14:09:07 xxx bluetoothd[2973]: Registered interface org.bluez.NetworkPeer on path /org/bluez/2973/hci0
Jul 11 14:09:07 xxx bluetoothd[2973]: Registered interface org.bluez.NetworkHub on path /org/bluez/2973/hci0
Jul 11 14:09:07 xxx bluetoothd[2973]: Registered interface org.bluez.NetworkRouter on path /org/bluez/2973/hci0
Jul 11 14:09:07 xxx bluetoothd[2973]: Registered interface org.bluez.Service on path /org/bluez/2973/hci0
Jul 11 14:09:07 xxx bluetoothd[2973]: Registered interface org.bluez.SerialProxyManager on path /org/bluez/2973/hci0
Jul 11 14:09:07 xxx bluetoothd[2973]: Registered interface org.bluez.Network on path /org/bluez/2973/hci0/dev_08_00_17_16_A0_76
Jul 11 14:09:07 xxx bluetoothd[2973]: Registered interface org.bluez.Serial on path /org/bluez/2973/hci0/dev_08_00_17_16_A0_76
Jul 11 14:09:07 xxx bluetoothd[2973]: Adapter /org/bluez/2973/hci0 has been enabled
Jul 11 14:09:10 xxx dhcpd: Internet Systems Consortium DHCP Server V3.1.1
Jul 11 14:09:10 xxx dhcpd: Copyright 2004-2008 Internet Systems Consortium.
Jul 11 14:09:10 xxx dhcpd: All rights reserved.
Jul 11 14:09:10 xxx dhcpd: For info, please visit http://www.isc.org/sw/dhcp/
Jul 11 14:09:10 xxx kernel: [ 20.257663] warning: `dhcpd3' uses 32-bit capabilities (legacy support in use)
Jul 11 14:09:10 xxx dhcpd: Internet Systems Consortium DHCP Server V3.1.1
Jul 11 14:09:10 xxx dhcpd: Copyright 2004-2008 Internet Systems Consortium.
Jul 11 14:09:10 xxx dhcpd: All rights reserved.
Jul 11 14:09:10 xxx dhcpd: For info, please visit http://www.isc.org/sw/dhcp/
Jul 11 14:09:10 xxx dhcpd: Internet Systems Consortium DHCP Server V3.1.1
Jul 11 14:09:10 xxx dhcpd: Copyright 2004-2008 Internet Systems Consortium.
Jul 11 14:09:10 xxx dhcpd: All rights reserved.
Jul 11 14:09:10 xxx dhcpd: For info, please visit http://www.isc.org/sw/dhcp/
Jul 11 14:09:10 xxx dhcpd: Wrote 0 leases to leases file.
Jul 11 14:09:10 xxx dhcpd:
Jul 11 14:09:10 xxx dhcpd: Not configured to listen on any interfaces!
Jul 11 14:09:11 xxx kernel: [ 21.122178] fglrx_pci 0000:01:00.0: irq 2299 for MSI/MSI-X
Jul 11 14:09:11 xxx kernel: [ 21.131690] [fglrx] Firegl kernel thread PID: 3105
Jul 11 14:09:11 xxx kernel: [ 21.143875] [fglrx] Gart USWC size:1883 M.
Jul 11 14:09:11 xxx kernel: [ 21.143878] [fglrx] Gart cacheable size:60 M.
Jul 11 14:09:11 xxx kernel: [ 21.143882] [fglrx] Reserved FB block: Shared offset:0, size:1000000
Jul 11 14:09:11 xxx kernel: [ 21.143884] [fglrx] Reserved FB block: Unshared offset:fc27000, size:3d9000
Jul 11 14:09:11 xxx kernel: [ 21.143886] [fglrx] Reserved FB block: Unshared offset:1fffb000, size:5000
Jul 11 14:09:12 xxx NetworkManager: <info> starting...
Jul 11 14:09:12 xxx avahi-daemon[3152]: Found user 'avahi' (UID 110) and group 'avahi' (GID 121).
Jul 11 14:09:12 xxx avahi-daemon[3152]: Successfully dropped root privileges.
Jul 11 14:09:12 xxx avahi-daemon[3152]: avahi-daemon 0.6.23 starting up.
Jul 11 14:09:12 xxx avahi-daemon[3152]: Successfully called chroot().
Jul 11 14:09:12 xxx avahi-daemon[3152]: Successfully dropped remaining capabilities.
Jul 11 14:09:12 xxx NetworkManager: <info> (eth0): new Ethernet device (driver: 'r8169')
Jul 11 14:09:12 xxx NetworkManager: <info> (eth0): exported as /org/freedesktop/Hal/devices/net_00_21_85_11_6b_43
Jul 11 14:09:12 xxx NetworkManager: <info> Trying to start the supplicant...
Jul 11 14:09:12 xxx NetworkManager: <info> Trying to start the system settings daemon...
Jul 11 14:09:12 xxx avahi-daemon[3152]: No service file found in /etc/avahi/services.
Jul 11 14:09:12 xxx avahi-daemon[3152]: Network interface enumeration completed.
Jul 11 14:09:12 xxx avahi-daemon[3152]: Registering HINFO record with values 'X86_64'/'LINUX'.
Jul 11 14:09:12 xxx avahi-daemon[3152]: Server startup complete. Host name is xxx.local. Local service cookie is 2280285506.
Jul 11 14:09:13 xxx anacron[3310]: Anacron 2.3 started on 2009-07-11
Jul 11 14:09:17 xxx NetworkManager: <info> (eth0): device state change: 1 -> 2
Jul 11 14:09:17 xxx NetworkManager: <info> (eth0): bringing up device.
Jul 11 14:09:17 xxx NetworkManager: <info> (eth0): preparing device.
Jul 11 14:09:17 xxx NetworkManager: <info> (eth0): deactivating device (reason: 2).
Jul 11 14:09:17 xxx NetworkManager: <info> (eth0): carrier now ON (device state 2)
Jul 11 14:09:17 xxx NetworkManager: <info> (eth0): device state change: 2 -> 3
Jul 11 14:09:17 xxx kernel: [ 27.078773] r8169: eth0: link up
Jul 11 14:09:17 xxx kernel: [ 27.078782] r8169: eth0: link up
Jul 11 14:09:17 xxx NetworkManager: <info> Activation (eth0) starting connection 'Auto eth0'
Jul 11 14:09:17 xxx NetworkManager: <info> (eth0): device state change: 3 -> 4
Jul 11 14:09:17 xxx NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
Jul 11 14:09:17 xxx NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) started...
Jul 11 14:09:17 xxx NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled...
Jul 11 14:09:17 xxx NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete.
Jul 11 14:09:17 xxx NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting...
Jul 11 14:09:17 xxx NetworkManager: <info> (eth0): device state change: 4 -> 5
Jul 11 14:09:17 xxx NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) successful.
Jul 11 14:09:17 xxx NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
Jul 11 14:09:17 xxx NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete.
Jul 11 14:09:17 xxx NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) started...
Jul 11 14:09:17 xxx NetworkManager: <info> (eth0): device state change: 5 -> 7
Jul 11 14:09:17 xxx NetworkManager: <info> Activation (eth0) Beginning DHCP transaction.
Jul 11 14:09:17 xxx NetworkManager: <info> dhclient started with pid 3518
Jul 11 14:09:17 xxx NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete.
Jul 11 14:09:17 xxx dhclient: Internet Systems Consortium DHCP Client V3.1.1
Jul 11 14:09:17 xxx dhclient: Copyright 2004-2008 Internet Systems Consortium.
Jul 11 14:09:17 xxx dhclient: All rights reserved.
Jul 11 14:09:17 xxx dhclient: For info, please visit http://www.isc.org/sw/dhcp/
Jul 11 14:09:17 xxx dhclient:
Jul 11 14:09:17 xxx NetworkManager: <info> DHCP: device eth0 state changed (null) -> preinit
Jul 11 14:09:17 xxx dhclient: Listening on LPF/eth0/00:21:85:11:6b:43
Jul 11 14:09:17 xxx dhclient: Sending on LPF/eth0/00:21:85:11:6b:43
Jul 11 14:09:17 xxx dhclient: Sending on Socket/fallback
Jul 11 14:09:18 xxx avahi-daemon[3152]: Registering new address record for fe80::221:85ff:fe11:6b43 on eth0.*.
Jul 11 14:09:21 xxx dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
Jul 11 14:09:21 xxx dhclient: DHCPOFFER of 192.168.0.2 from 192.168.0.1
Jul 11 14:09:21 xxx dhclient: DHCPREQUEST of 192.168.0.2 on eth0 to 255.255.255.255 port 67
Jul 11 14:09:21 xxx dhclient: DHCPACK of 192.168.0.2 from 192.168.0.1
Jul 11 14:09:21 xxx NetworkManager: <info> DHCP: device eth0 state changed preinit -> bound
Jul 11 14:09:21 xxx NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP Configure Get) scheduled...
Jul 11 14:09:21 xxx NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP Configure Get) started...
Jul 11 14:09:21 xxx NetworkManager: <info> address 192.168.0.2
Jul 11 14:09:21 xxx NetworkManager: <info> prefix 24 (255.255.255.0)
Jul 11 14:09:21 xxx NetworkManager: <info> gateway 192.168.0.1
Jul 11 14:09:21 xxx NetworkManager: <info> nameserver '83.169.184.161'
Jul 11 14:09:21 xxx NetworkManager: <info> nameserver '83.169.184.225'
Jul 11 14:09:21 xxx NetworkManager: <info> nameserver '192.168.0.1'
Jul 11 14:09:21 xxx NetworkManager: <info> domain name 'search.b.superkabel.de'
Jul 11 14:09:21 xxx NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) scheduled...
Jul 11 14:09:21 xxx NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP Configure Get) complete.
Jul 11 14:09:21 xxx NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) started...
Jul 11 14:09:21 xxx avahi-daemon[3152]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.0.2.
Jul 11 14:09:21 xxx dhclient: bound to 192.168.0.2 -- renewal in 298114 seconds.
Jul 11 14:09:21 xxx avahi-daemon[3152]: New relevant interface eth0.IPv4 for mDNS.
Jul 11 14:09:21 xxx avahi-daemon[3152]: Registering new address record for 192.168.0.2 on eth0.IPv4.
Jul 11 14:09:22 xxx NetworkManager: <info> (eth0): device state change: 7 -> 8
Jul 11 14:09:22 xxx NetworkManager: <info> Policy set 'Auto eth0' (eth0) as default for routing and DNS.
Jul 11 14:09:22 xxx NetworkManager: <info> Activation (eth0) successful, device activated.
Jul 11 14:09:22 xxx NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) complete.Und folgendes meldet sich im syslog, wenn ich auf dem PDA den BlueZ NAP service verbinde.
Code
Jul 11 14:50:33 xxx bluetoothd[2973]: link_key_request (sba=00:02:5B:01:03:21, dba=08:00:17:16:A0:76)
Jul 11 14:50:34 xxx bluetoothd[2973]: Added new connection: bnep0
Jul 11 14:50:34 xxx bluetoothd[2973]: bridge pan0: interface bnep0 added
Jul 11 14:50:34 xxx kernel: [ 2504.236727] device bnep0 entered promiscuous mode
Jul 11 14:50:34 xxx kernel: [ 2504.239266] pan0: port 1(bnep0) entering learning state
Jul 11 14:50:35 xxx avahi-daemon[3152]: Registering new address record for fe80::202:5bff:fe01:321 on pan0.*.
Jul 11 14:50:35 xxx avahi-daemon[3152]: Registering new address record for fe80::202:5bff:fe01:321 on bnep0.*.
Jul 11 14:50:44 xxx kernel: [ 2514.736007] pan0: no IPv6 routers present
Jul 11 14:50:44 xxx kernel: [ 2514.813026] bnep0: no IPv6 routers present
Jul 11 14:50:49 xxx kernel: [ 2519.236007] pan0: topology change detected, propagating
Jul 11 14:50:49 xxx kernel: [ 2519.236012] pan0: port 1(bnep0) entering forwarding state
Ausgabe ifconfig
Code
xxx@xxx:~$ ifconfig
bnep0 Link encap:Ethernet Hardware Adresse 00:02:5b:01:03:21
inet6-Adresse: fe80::202:5bff:fe01:321/64 Gültigkeitsbereich:Verbindung
UP BROADCAST RUNNING MULTICAST MTU:1500 Metrik:1
RX packets:9 errors:0 dropped:0 overruns:0 frame:0
TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlänge:1000
RX bytes:1449 (1.4 KB) TX bytes:64 (64.0 B)
eth0 Link encap:Ethernet Hardware Adresse 00:21:85:11:6b:43
inet Adresse:192.168.0.2 Bcast:192.168.0.255 Maske:255.255.255.0
inet6-Adresse: fe80::221:85ff:fe11:6b43/64 Gültigkeitsbereich:Verbindung
UP BROADCAST RUNNING MULTICAST MTU:1500 Metrik:1
RX packets:1661 errors:0 dropped:0 overruns:0 frame:0
TX packets:1782 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlänge:1000
RX bytes:1097931 (1.0 MB) TX bytes:349930 (349.9 KB)
Interrupt:252 Basisadresse:0xa000
lo Link encap:Lokale Schleife
inet Adresse:127.0.0.1 Maske:255.0.0.0
inet6-Adresse: ::1/128 Gültigkeitsbereich:Maschine
UP LOOPBACK RUNNING MTU:16436 Metrik:1
RX packets:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlänge:0
RX bytes:480 (480.0 B) TX bytes:480 (480.0 B)
pan0 Link encap:Ethernet Hardware Adresse 00:02:5b:01:03:21
inet6-Adresse: fe80::202:5bff:fe01:321/64 Gültigkeitsbereich:Verbindung
UP BROADCAST RUNNING MULTICAST MTU:1500 Metrik:1
RX packets:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlänge:0
RX bytes:824 (824.0 B) TX bytes:468 (468.0 B)Beim PDA habe ich bei der Netzwerkkarte "Bluetooth PAN User Driver" folgende Einstellung: "Vom Server zugewiesene IP-Adresse" und Automatische Namensserverzuweiseung, falls DHCP auf dem Adapter aktiviert ist" (kein DNS oder WINS angegeben).
Kann jemand sagen, was ich falsch mache?
LG
Joachim
Der dhcp-server startet nicht, weil er offenbar nicht richtig konfiguriert ist. Er weiß nicht, an welchem interface er lauschen soll und bricht den Startversuch ab.
.