heinzelrumpel

Forum Replies Created

Viewing 30 posts - 1 through 30 (of 32 total)
1 2
  • Back to forum
    Posted in: Allo USB Bundle
  • heinzelrumpel premium
    18. Februar 2019 at 20:11 #44514

    Well, on a fresh image it works, tested it yesterday, but this does not help me getting openHAB runnig on that specific device.

    heinzelrumpel premium
    17. Februar 2019 at 18:13 #44482

    Just manually uninstalled FHEM via apt. Now wanted to install openHAB. Got the plugin and went to menu to install it, but it doesn’t install. No debug shown. Something goes really weird here

    OpenHAB (version 2) installation started
    Installation gestartet – Diese Meldung zeigt den aktuellen Status der Installation aller 3 Sekunden an. Wenn diese abgeschlossen ist verschwindet die Meldung und der Server läuft.

    OK
    Reading package lists…
    Building dependency tree…
    Reading state information…
    Reading package lists…
    Building dependency tree…
    Reading state information…
    You might want to run ‚apt-get -f install‘ to correct these:
    The following packages have unmet dependencies:
    dirmngr : Depends: libassuan0 (>= 2.0.2) but it is not going to be installed
    Depends: libksba8 (>= 1.2.0) but it is not going to be installed
    Depends: libpth20 (>= 2.0.7) but it is not going to be installed
    libssl-dev : Depends: libssl1.0.0 (= 1.0.1t-1+deb8u10) but 1.0.1t-1+deb7u4 is to be installed
    Executing: gpg –ignore-time-conflict –no-options –no-default-keyring –homedir /tmp/tmp.CwPWtcZ23m –no-auto-check-trustdb –trust-model always –keyring /etc/apt/trusted.gpg –primary-keyring /etc/apt/trusted.gpg –recv-key –no-tty –keyserver keyserver.ubuntu.com EEA14886
    deb http://ppa.launchpad.net/webupd8team/java/ubuntu trusty main
    deb-src http://ppa.launchpad.net/webupd8team/java/ubuntu trusty main
    Reading package lists…
    Building dependency tree…
    Reading state information…
    Finished – please click here to reload Page to see Changes

    But under openHAB menu there is nothing afterwards, besides installing openHAB again.

    heinzelrumpel premium
    29. September 2018 at 18:09 #38242

    Und was war die Lösung?

    heinzelrumpel premium
    8. März 2017 at 14:03 #27507

    Hi,

    I would make a Backup with win32diskimager and then try sdcard in new Raspberry.

    • This reply was modified 7 years, 8 months ago by heinzelrumpel.
    heinzelrumpel premium
    7. Februar 2017 at 20:08 #26738

    LogiLink BT0015 USB bluetooth V4.0 EDR Class1 Micro, CSR Chip https://www.amazon.de/dp/B0096Y2HFW/ref=cm_sw_r_cp_apa_TVGMybGX7ES7A

    I bought this one. As I wrote it works better than the integrated one, but still, not close of beeing satisfactoraly. Streaming buffer is one issue, the other one is that echo dot sometimes looses Connection. In Orange Squeeze I then push play for that device again and streaming continues.Very annoying.

    heinzelrumpel premium
    5. Februar 2017 at 20:39 #26686

    Just bought a new external bluetooth adapter. So far it works much better, as long the distance of echo dot ist not more than 4-5m. On problem still persists. When connecting from my win 10 notebook streaming seem to buffer, means, when starting to play a song it takes up to 36 seconds till sound is comming out of the speakers. Same happens, when stopping a song, eg. in groove. The song keeps playing for quite a while.

    heinzelrumpel premium
    31. Januar 2017 at 21:33 #26528

    Hi,

    everything works as expected, that’s why I posted.

    Ciao, Heinzelrumpel

    heinzelrumpel premium
    27. Januar 2017 at 12:03 #26359

    Different PI did not work. Somehow the smartphone can’t see M2P. I suppose the external bluetooth dongle is the problem.

    heinzelrumpel premium
    26. Januar 2017 at 11:14 #26321

    Hi,

    just tried yesterday. Plugged in an additional power supply, then deactivated internal bluetooth, deinstalled bluetooth, plugged in external adapter, installed bluetooth again. M2P sees my smartphone, but not the other way arround. Pairing not possible. The same with Echo dot. So reversed the whole thing and got internal bluetooth up again, but even with 2 power suplies the problem persists. Pffff…… Tried to not stream to LMS server, but instead to audioplayer. In advanced settings I selected pulse, but with this configuration no sound is comming out of AMP+, which I already expected.

    Will try a different PI(Model B) today to see, if streaming might work on that one.

    heinzelrumpel premium
    25. Januar 2017 at 15:37 #26297

    Does the setting under „RPi Einstellungen“ –> “ Turn Bluetooth Off“ only effect internal device, or does it turn off the whole stack?

    heinzelrumpel premium
    25. Januar 2017 at 12:07 #26293

    @flysurfer

    I am using the case for AMP+ I bought in your shop. Distance between devices is only 2-3m. Yes, I am using the power supply for the AMP+. This should be sufficient as to the statement in m2p webshop

    Our promise

    All of our offered hardware is tested extensively and is optimally compatible with the Max2Play image. No Linux knowledge is necessary for our out of the box solutions.

    Ok, that is advertisement. I will try a seperat power supply for the Pi3 and an external dongle for bluetooth.

    heinzelrumpel premium
    25. Januar 2017 at 11:10 #26290

    I am glad, that for some of you streaming seem to work now, but in my case it is still a hassle. Just yesterday I reinstalled and upgraded to 2.40, but nothing got better. My LG G3 starts streaming, but after a while, streaming stops, or worse, all of a sudden LMS plays a song which had been in queue. I am really annoyed of all this. Sorry, at this point I have to say, that m2p is not as it promised to be. There seem to be so many exceptions for the individual setup, that the features advertised on the feature list might work, but not for all and not on all hardware. I explicetly bought my system from m2p to be on the save side. PI3 with AMP+. Streaming via bluetooth was the killer feature why I decided to buy it and for now this is kiling me. Please do not misunderstand my complains. I find this project very interesting and it has great potential, but a this stage it promises more than it can actually fullfil. Just my opinion.

    heinzelrumpel premium
    18. Januar 2017 at 22:53 #26110

    No, the Display is not made for PIN because of the ammount of pins. I just tested it on another Model B.

    heinzelrumpel premium
    18. Januar 2017 at 16:45 #26042

    I already did.

    heinzelrumpel premium
    16. Januar 2017 at 20:28 #25983

    Just disabled internal wifi, then restartet raspberry. Outcome was, tha squeezelite won’t start. Reversed and now it at least plays again.

    Jan 16 19:18:30 max2play mtp-probe: checking bus 1, device 3: „/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1“
    Jan 16 19:18:30 max2play mtp-probe: checking bus 1, device 8: „/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3“
    Jan 16 19:18:30 max2play mtp-probe: bus: 1, device: 8 was not an MTP device
    Jan 16 19:18:30 max2play mtp-probe: bus: 1, device: 3 was not an MTP device
    Jan 16 19:19:11 max2play pulseaudio[1227]: [pulseaudio] bluez4-util.c: org.bluez.Manager.GetProperties() failed: org.freedesktop.DBus.Error.UnknownMethod: Method „GetProperties“ with signature „“ on interface „org.bluez.Manager“ doesn’t exist
    Jan 16 19:19:12 max2play pulseaudio[1227]: [pulseaudio] socket-server.c: bind(): Die Adresse wird bereits verwendet
    Jan 16 19:19:12 max2play pulseaudio[1227]: [pulseaudio] module.c: Failed to load module „module-cli-protocol-unix“ (argument: „“): initialization failed.
    Jan 16 19:19:18 max2play org.gtk.Private.AfcVolumeMonitor[1199]: Volume monitor alive
    Jan 16 19:21:30 max2play pulseaudio[1227]: [bluetooth] module-bluez5-device.c: SBC decoding error (-2)
    Jan 16 19:25:15 max2play mtp-probe: checking bus 1, device 8: „/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3“
    Jan 16 19:25:15 max2play mtp-probe: bus: 1, device: 8 was not an MTP device
    Jan 16 19:25:15 max2play mtp-probe: checking bus 1, device 3: „/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1“
    Jan 16 19:25:15 max2play mtp-probe: bus: 1, device: 3 was not an MTP device
    Jan 16 19:25:26 max2play pulseaudio[971]: [autospawn] core-util.c: Failed to create secure directory (/run/user/1000/pulse): Datei oder Verzeichnis nicht gefunden
    Jan 16 19:25:26 max2play pulseaudio[971]: [autospawn] lock-autospawn.c: Fehler beim Zugriff auf Autostart-Sperre.
    Jan 16 19:25:26 max2play pulseaudio[971]: [pulseaudio] main.c: Failed to acquire autospawn lock
    Jan 16 19:25:49 max2play pulseaudio[1263]: [pulseaudio] bluez4-util.c: org.bluez.Manager.GetProperties() failed: org.freedesktop.DBus.Error.UnknownMethod: Method „GetProperties“ with signature „“ on interface „org.bluez.Manager“ doesn’t exist
    Jan 16 19:26:02 max2play org.gtk.Private.AfcVolumeMonitor[1238]: Volume monitor alive
    Jan 16 19:29:05 max2play pulseaudio[1263]: [bluetooth] module-bluez5-device.c: SBC decoding error (-2)

    Jan 16 19:25:19 max2play kernel: [ 11.611004] Bluetooth: HCI device and connection manager initialized
    Jan 16 19:25:19 max2play kernel: [ 11.611030] Bluetooth: HCI socket layer initialized
    Jan 16 19:25:19 max2play kernel: [ 11.611049] Bluetooth: L2CAP socket layer initialized
    Jan 16 19:25:19 max2play kernel: [ 11.611087] Bluetooth: SCO socket layer initialized
    Jan 16 19:25:19 max2play kernel: [ 11.618574] Bluetooth: HCI UART driver ver 2.3
    Jan 16 19:25:19 max2play kernel: [ 11.618600] Bluetooth: HCI UART protocol H4 registered
    Jan 16 19:25:19 max2play kernel: [ 11.618610] Bluetooth: HCI UART protocol Three-wire (H5) registered
    Jan 16 19:25:19 max2play kernel: [ 11.618824] Bluetooth: HCI UART protocol BCM registered
    Jan 16 19:25:19 max2play kernel: [ 11.880380] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
    Jan 16 19:25:19 max2play kernel: [ 11.880400] Bluetooth: BNEP filters: protocol multicast
    Jan 16 19:25:19 max2play kernel: [ 11.880423] Bluetooth: BNEP socket layer initialized
    Jan 16 19:25:23 max2play kernel: [ 15.858998] FS-Cache: Netfs ‚cifs‘ registered for caching
    Jan 16 19:25:23 max2play kernel: [ 15.859829] Key type cifs.spnego registered
    Jan 16 19:25:23 max2play kernel: [ 15.859892] Key type cifs.idmap registered
    Jan 16 19:25:26 max2play kernel: [ 18.668019] Adding 102396k swap on /var/swap. Priority:-1 extents:7 across:307200k SSFS
    Jan 16 19:25:51 max2play kernel: [ 35.418229] Bluetooth: hci0 command 0x0c24 tx timeout
    Jan 16 19:25:53 max2play kernel: [ 37.418258] Bluetooth: hci0 command 0x0c52 tx timeout
    Jan 16 19:26:24 max2play kernel: [ 68.098617] input: 68:54:FD:88:4F:8A as /devices/virtual/input/input0
    Jan 16 19:29:05 max2play kernel: [ 229.175693] Bluetooth: hci0: Frame reassembly failed (-84)
    Jan 16 19:29:05 max2play kernel: [ 229.175762] Bluetooth: hci0: Frame reassembly failed (-84)
    Jan 16 19:29:05 max2play kernel: [ 229.175851] Bluetooth: hci0: Frame reassembly failed (-84)
    Jan 16 19:29:05 max2play kernel: [ 229.175933] Bluetooth: hci0: Frame reassembly failed (-84)
    Jan 16 19:29:05 max2play kernel: [ 229.176019] Bluetooth: hci0: Frame reassembly failed (-84)
    Jan 16 19:29:05 max2play kernel: [ 229.176107] Bluetooth: hci0: Frame reassembly failed (-84)
    Jan 16 19:29:05 max2play kernel: [ 229.176194] Bluetooth: hci0: Frame reassembly failed (-84)
    Jan 16 19:29:05 max2play kernel: [ 229.176282] Bluetooth: hci0: Frame reassembly failed (-84)
    Jan 16 19:29:05 max2play kernel: [ 229.176369] Bluetooth: hci0: Frame reassembly failed (-84)
    Jan 16 19:29:05 max2play kernel: [ 229.176466] Bluetooth: hci0: Frame reassembly failed (-84)

    • This reply was modified 7 years, 10 months ago by heinzelrumpel.
    • This reply was modified 7 years, 10 months ago by heinzelrumpel.
    heinzelrumpel premium
    16. Januar 2017 at 20:04 #25979

    Yes, all devices have the same issue, more or less. With my LG3 I get the best experience. After installimg from scratch it was the first device connected via bluetooth. Sometimes the connection lasts for 15-20 minutes without interrupts, but sometimes not. Echo dot does sometimes not even play right away. I have to disconnect and reconnect twice to get it work, but still, after a few minutes playing it stops. With fire tablet its the same. Distance is no issue, because m2p and devices are not more than 5m away, no walls etc.With all devices, the actual bluetooth connection is not lost, just the streaming does not produce any output to the speakers via HifiBerry AMp+ . Is there a way I can debug this?

    I could try disabling inernal wifi as you mentioned, but getting the description right, it only moves binding of adapter from wlan0 to wlan1. Dont see any improvements in doing so.

    [img]http://up.picr.de/28039022vn.jpg[/img]

    • This reply was modified 7 years, 10 months ago by heinzelrumpel.
    heinzelrumpel premium
    13. Januar 2017 at 20:04 #25910

    Hi,

    I did exactly as you described. Maybe the problem lies with in the fact, that I was not using an Pi 3. I digged out my Model B from 2012 and display of the same age. That Rassberry has lesser gpio pins than Pi3, so I suppose the watterott Display cannot be use with newer raspberries.

    heinzelrumpel premium
    11. Januar 2017 at 14:05 #25768

    Ja, Du musst die /etc/apache2/sites-enabled/Max2Play.conf anpassen. Stichwort „virtual host“. Danach von deinem Router eine Portweiterleitung dorthin einrichten.

    heinzelrumpel premium
    10. Januar 2017 at 13:28 #25749

    Hat sich erledigt

    
/usr/bin/htpasswd -b -c /var/www/max2play/.htpasswd
    heinzelrumpel premium
    10. Januar 2017 at 11:57 #25729

    @flysurfer

    Hi Castalla,

    it should be really easy – maybe you missed the part where you couple your smartphone with Max2Play? This must be done just once after you installed the Bluetooth plugin and before clicking the “install Bluetooth Streaming to Squeezebox Server” at the bottom of the Bluetooth Plugin (this really needs to know your smartphone as otherwise it will not start streaming).

    Do I have to do this step with every device which should be able to stream to m2play server via bluetooth?

    heinzelrumpel premium
    3. Januar 2017 at 20:25 #25435

    hier mal etwas ausführlicher nach dem jivelite Neustart

    

[  2558.566]    ABI class: X.Org ANSI C Emulation, version 0.4
[  2558.567] (EE) FBDEV(0): FBIOBLANK: Invalid argument
[  2558.569] (==) FBDEV(0): Backing store enabled
[  2558.570] (==) FBDEV(0): DPMS enabled
[  2558.571] (==) RandR enabled
[  2558.653] (II) SELinux: Disabled on system
[  2558.664] (II) AIGLX: Screen 0 is not DRI2 capable
[  2558.665] (EE) AIGLX: reverting to software rendering
[  2559.050] (II) AIGLX: Loaded and initialized swrast
[  2559.051] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[  2559.842] (II) config/udev: Adding input device ADS7846 Touchscreen (/dev/input/event0)
[  2559.844] (**) ADS7846 Touchscreen: Applying InputClass "evdev touchscreen catchall"
[  2559.847] (**) ADS7846 Touchscreen: Applying InputClass "Touchscreen"
[  2559.849] (II) LoadModule: "evdev"
[  2559.853] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[  2559.861] (II) Module evdev: vendor="X.Org Foundation"
[  2559.947]    compiled for 1.17.2, module version = 2.9.2
[  2559.948]    Module class: X.Org XInput Driver
[  2559.948]    ABI class: X.Org XInput driver, version 21.0
[  2559.948] (II) Using input driver 'evdev' for 'ADS7846 Touchscreen'
[  2559.948] (**) ADS7846 Touchscreen: always reports core events
[  2559.949] (**) evdev: ADS7846 Touchscreen: Device: "/dev/input/event0"
[  2559.952] (--) evdev: ADS7846 Touchscreen: Vendor 0 Product 0
[  2559.956] (--) evdev: ADS7846 Touchscreen: Found absolute axes
[  2559.958] (--) evdev: ADS7846 Touchscreen: Found x and y absolute axes
[  2559.960] (--) evdev: ADS7846 Touchscreen: Found absolute touchscreen
[  2559.961] (**) Option "InvertX" "0"
[  2559.964] (**) Option "InvertY" "1"
[  2559.966] (**) Option "SwapAxes" "1"
[  2559.968] (II) evdev: ADS7846 Touchscreen: Configuring as touchscreen
[  2559.969] (**) Option "EmulateThirdButton" "1"
[  2559.970] (**) Option "EmulateThirdButtonTimeout" "1500"
[  2559.973] (**) Option "EmulateThirdButtonMoveThreshold" "30"
[  2559.981] (**) evdev: ADS7846 Touchscreen: YAxisMapping: buttons 4 and 5
[  2559.981] (**) evdev: ADS7846 Touchscreen: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[  2559.983] (**) Option "config_info" "udev:/sys/devices/platform/soc/20204000.spi/spi_master/spi0/spi0.1/input/input0/event0"
[  2559.985] (II) XINPUT: Adding extended input device "ADS7846 Touchscreen" (type: TOUCHSCREEN, id 6)
[  2559.990] (II) evdev: ADS7846 Touchscreen: initialized for absolute axes.
[  2559.994] (**) ADS7846 Touchscreen: (accel) keeping acceleration scheme 1
[  2559.997] (**) ADS7846 Touchscreen: (accel) acceleration profile 0
[  2559.999] (**) ADS7846 Touchscreen: (accel) acceleration factor: 2.000
[  2560.001] (**) ADS7846 Touchscreen: (accel) acceleration threshold: 4
[  2560.008] (II) config/udev: Adding input device ADS7846 Touchscreen (/dev/input/mouse0)
[  2560.011] (**) ADS7846 Touchscreen: Applying InputClass "Touchscreen"
[  2560.013] (II) No input driver specified, ignoring this device.
[  2560.017] (II) This device may have been added with another device file.
[  2560.078] (EE) FBDEV(0): FBIOBLANK: Invalid argument
[  2573.034] (EE) FBDEV(0): FBIOBLANK: Invalid argument
[  2578.045] (EE) FBDEV(0): FBIOBLANK: Invalid argument
[  2578.809] (EE) FBDEV(0): FBIOBLANK: Invalid argument
[  2583.063] (EE) FBDEV(0): FBIOBLANK: Invalid argument
[  2583.837] (EE) FBDEV(0): FBIOBLANK: Invalid argument
[  2588.077] (EE) FBDEV(0): FBIOBLANK: Invalid argument
[  2588.852] (EE) FBDEV(0): FBIOBLANK: Invalid argument
    heinzelrumpel premium
    3. Januar 2017 at 18:15 #25418

    And this is the answer to what question? Sorry, but I cannot see any relation to the start order of squeezeboxserver and kodi.

    heinzelrumpel premium
    22. Dezember 2016 at 22:58 #25184

    I had simulation issues when trying und to connect to my NAS. Forget the Web interface. Just go to /etc/fstab and enter the stuff right into it. Afterwards „mount -a“ and everything should be fine.

    heinzelrumpel premium
    22. Dezember 2016 at 17:19 #25167

    So, hinbekommen. Mehrfach neu gescanned und dann mit dem echo dot verbunden. Im SqueezeBoxServer Webmenü taucht er auch unter Favoruites auf, aber leider kommt kein Ton aus den Lautsprechern. Sehr schade. Verbinde ich mein Handy, dann kommt Sound, aber leider auch nur sehr ruckelig und so nicht zu gebrauchen. Habe mir das ganze System ehrlich gesagt etwas smoother vorgestellt….

    heinzelrumpel premium
    22. Dezember 2016 at 17:15 #25165

    Habe den Schuldigen jetzt ausfindig gemacht. Es liegt an Kodi, dass der Squeezeboxserver sich nicht an Port 9090 binden kann. Komisch bei der Sache ist nur, dass Kodi für sich nur tcp6:9090 beansprucht, der squeezeboxserver aber, wenn er denn dann läuft, nur tcp4:9090 benutzt. Habe per Webmenü tcp6 ausgeschaltet, schein für kodi aber kein Grund zu sein. Jetzt muss ich nur mal schauen, wie ich es hinbekomme, dass der squeezeboxsserver vor kodi gestartet wird. So geht es nämlich. Hat jemand eine Idee, wie man unter Jessie die Startreihenfolge ändert?

    • This reply was modified 7 years, 11 months ago by heinzelrumpel.
    heinzelrumpel premium
    22. Dezember 2016 at 12:00 #25142

    Hi Christoph,

    danke für die Info.

    Ciao, Heinzelrumpel

    heinzelrumpel premium
    22. Dezember 2016 at 11:46 #25141

    HI std,

    das hat ich ja auch gedacht, aber der echo dot. taucht einfach nicht mehr auf und da in der Weboberfläche steht „permanent löschen“ klang es für mich schlüssig, dass das device wohl in einer blacklist steckt, welches ja mit „bt-device –set blocked “ o.ä. so zu erreichen wäre.

    http://manpages.ubuntu.com/manpages/trusty/man1/bt-device.1.html

    heinzelrumpel premium
    22. Dezember 2016 at 9:13 #25136

    Hallo,

    hat denn niemand eine Idee? Irgendwo muss doch eine blacklist existieren.

    Grüße, Heinzelrumpel

    heinzelrumpel premium
    21. Dezember 2016 at 18:42 #25125

    Hi,

    hab mir jetzt erst einmal so geholfen,dass ich den squeezeboxserver auf Port 9091 laufen lasse. Aber irgendwie wird nach dem scannen von Bluetooth Geräten nichts außer einer einzigen MAC Adresse angezeigt. Sehe den Zusammenhang da gerade nicht. Mit dem anderen Port geht ja erstmal,aber es soll keine Dauerlösung sein.Der Fehler sollte ja irgendwie behebbar sein.

    Gruß, heinzelrumpel

    heinzelrumpel premium
    21. Dezember 2016 at 11:27 #25102 
    
root@max2play:/opt/max2play# netstat -ant
Aktive Internetverbindungen (Server und stehende Verbindungen)
Proto Recv-Q Send-Q Local Address           Foreign Address         State
tcp        0      0 0.0.0.0:9000            0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:139             0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:8080            0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:8081            0.0.0.0:*               LISTEN
tcp        0      0 127.0.0.1:52307         0.0.0.0:*               LISTEN
tcp        0      0 127.0.0.1:3350          0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:36666           0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:1786            0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:3483            0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:35517           0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:445             0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:3389            0.0.0.0:*               LISTEN
tcp        0      0 192.168.178.48:42682    192.168.178.48:3483     VERBUNDEN
tcp        0    272 192.168.178.48:22       192.168.178.222:9483    VERBUNDEN
tcp        0      0 192.168.178.48:44862    192.168.178.222:5000    TIME_WAIT
tcp        0      0 192.168.178.48:44864    192.168.178.222:5000    TIME_WAIT
tcp        0      0 192.168.178.48:41634    192.168.178.222:445     VERBUNDEN
tcp        0      0 192.168.178.48:44866    192.168.178.222:5000    VERBUNDEN
tcp        0      0 192.168.178.48:3483     192.168.178.48:42682    VERBUNDEN
tcp        0      0 127.0.0.1:34160         127.0.0.1:6600          VERBUNDEN
tcp6       0      0 :::42688                :::*                    LISTEN
tcp6       0      0 :::9090                 :::*                    LISTEN
tcp6       0      0 :::6600                 :::*                    LISTEN
tcp6       0      0 :::139                  :::*                    LISTEN
tcp6       0      0 :::8080                 :::*                    LISTEN
tcp6       0      0 :::80                   :::*                    LISTEN
tcp6       0      0 :::22                   :::*                    LISTEN
tcp6       0      0 :::36666                :::*                    LISTEN
tcp6       0      0 :::36667                :::*                    LISTEN
tcp6       0      0 :::445                  :::*                    LISTEN
tcp6       0      0 127.0.0.1:6600          127.0.0.1:34160         VERBUNDEN
Viewing 30 posts - 1 through 30 (of 32 total)
1 2