Mailing List Archive

Q about networking after recent networking improvements in master
Peter,

After upgrade mythtv-master from r380 to r385 I started to have many following entries in FE log:

……………
2017-04-12 19:46:47.563426 E Failed listening on TCP [::]:5000 - Error 10: Protocol type not supported
……………

see below full fe log

My FE is minimyth2. It has no IPv6 compiled within kernel.
Is it possible that this is cause?

Or maybe new code needs to change something in BE config?

Anyway - pls be aware that some users may have similar problem.

If it is result of not adequate BE config - then I believe it is good practice to set new defaults in a way guarantying myth behavior exactly like before Your’s networking improvements.
This may help to avoid storm of user complains about issue like this…


2017-04-12 19:46:43.928556 I Setup Interrupt handler
2017-04-12 19:46:43.928589 I Setup Terminated handler
2017-04-12 19:46:43.928594 I Setup Segmentation fault handler
2017-04-12 19:46:43.928598 I Setup Aborted handler
2017-04-12 19:46:43.928603 I Setup Bus error handler
2017-04-12 19:46:43.928608 I Setup Floating point exception handler
2017-04-12 19:46:43.928611 I Setup Illegal instruction handler
2017-04-12 19:46:43.928617 I Setup Real-time signal 0 handler
2017-04-12 19:46:43.928623 I Setup User defined signal 1 handler
2017-04-12 19:46:43.928627 I Setup User defined signal 2 handler
2017-04-12 19:46:43.928631 I Setup Hangup handler
2017-04-12 19:46:43.928764 C mythfrontend version: master [v29-pre-385-g65f9928] www.mythtv.org
2017-04-12 19:46:43.928771 C Qt version: compile: 5.4.1, runtime: 5.4.1
2017-04-12 19:46:43.928774 N Enabled verbose msgs: general playback audio
2017-04-12 19:46:43.928790 N Setting Log Level to LOG_INFO
2017-04-12 19:46:43.939273 I Added logging to the console
2017-04-12 19:46:43.939283 N Using runtime prefix = /usr
2017-04-12 19:46:43.939287 N Using configuration directory = /home/minimyth/.mythtv
2017-04-12 19:46:43.939341 I Assumed character encoding: en_US.UTF-8
2017-04-12 19:46:43.939869 N Empty LocalHostName.
2017-04-12 19:46:43.939876 I Using localhost value of FE-IntelNUC
2017-04-12 19:46:43.939923 I Start up testing connections. DB 192.168.1.221, BE , attempt 0, status dbAwake
2017-04-12 19:46:45.980520 N Setting QT default locale to en_US
2017-04-12 19:46:45.980534 I Current locale en_US
2017-04-12 19:46:45.980583 N Reading locale defaults from /usr/share/mythtv//locales/en_us.xml
2017-04-12 19:46:45.999820 I Starting process manager
2017-04-12 19:46:45.999848 I Starting IO manager (read)
2017-04-12 19:46:45.999857 I Starting process signal handler
2017-04-12 19:46:46.000409 I Starting IO manager (write)
2017-04-12 19:46:46.050205 I ScreenSaverX11Private: XScreenSaver support enabled
2017-04-12 19:46:46.051219 I ScreenSaverX11Private: DPMS is disabled.
2017-04-12 19:46:46.064586 N Desktop video mode: 1280x1024 60.020 Hz
2017-04-12 19:46:46.084691 I max_width: 1280 max_height: 1024
2017-04-12 19:46:46.116266 I Listening on TCP 0.0.0.0:6547
2017-04-12 19:46:46.116944 E Failed listening on TCP [::]:6547 - Error 10: Protocol type not supported
2017-04-12 19:46:46.116987 E MediaRenderer: HttpServer Create Error
2017-04-12 19:46:46.134190 I Loading en_us translation for module mythfrontend
2017-04-12 19:46:46.145706 I LIRC: Successfully initialized '/dev/lircd' using '/home/minimyth/.mythtv/lircrc' config
2017-04-12 19:46:46.145747 I UDPListener: Enabling
2017-04-12 19:46:46.146785 I Binding to UDP 0.0.0.0:6948
2017-04-12 19:46:46.147523 E Failed binding to UDP [::]:6948 - Error 10: Protocol type not supported
2017-04-12 19:46:46.162814 I Using Frameless Window
2017-04-12 19:46:46.162817 I Using Full Screen Window
2017-04-12 19:46:46.174641 I UI Screen Resolution: 1280 x 1024
2017-04-12 19:46:46.221004 W OpenGL: Could not determine whether Sync to VBlank is enabled.
2017-04-12 19:46:46.224993 I Trying the OpenGL 2.0 render
2017-04-12 19:46:46.228697 I OpenGL painter using existing OpenGL context.
2017-04-12 19:46:46.234513 I OpenGL2: GLSL supported
2017-04-12 19:46:46.234559 I OpenGL: OpenGL vendor : Intel Open Source Technology Center
2017-04-12 19:46:46.234564 I OpenGL: OpenGL renderer: Mesa DRI Intel(R) Ivybridge Mobile
2017-04-12 19:46:46.234566 I OpenGL: OpenGL version : 3.0 Mesa 17.0.3
2017-04-12 19:46:46.234572 I OpenGL: Max texture size: 16384 x 16384
2017-04-12 19:46:46.234574 I OpenGL: Max texture units: 8
2017-04-12 19:46:46.234577 I OpenGL: Direct rendering: Yes
2017-04-12 19:46:46.234586 I OpenGL: Extensions Supported: 1e1b
2017-04-12 19:46:46.234589 I OpenGL: PixelBufferObject support available
2017-04-12 19:46:46.255749 I OpenGL: Initialised MythRenderOpenGL
2017-04-12 19:46:47.343268 I MythCoreContext::ConnectCommandSocket(): Connecting to backend server: 192.168.1.221:6543 (try 1 of 1)
2017-04-12 19:46:47.348707 I MythCoreContext::CheckProtoVersion(): Using protocol version 91 BuzzOff
2017-04-12 19:46:47.502654 I MythUIWebBrowser: Loading css from - file:///usr/share/mythtv/themes/default/htmls/mythbrowser.css
2017-04-12 19:46:47.515298 I MythUIWebBrowser: enabling plugins
2017-04-12 19:46:47.562353 I RAOP Device: Created RAOP device objects.
2017-04-12 19:46:47.562474 I Listening on TCP 0.0.0.0:5000
2017-04-12 19:46:47.563183 I AirPlay: Created airplay objects.
2017-04-12 19:46:47.563407 I Listening on TCP 0.0.0.0:5100
2017-04-12 19:46:47.563426 E Failed listening on TCP [::]:5000 - Error 10: Protocol type not supported
2017-04-12 19:46:47.563531 I Listening on TCP 0.0.0.0:5001
2017-04-12 19:46:47.564172 E Failed listening on TCP [::]:5100 - Error 10: Protocol type not supported
2017-04-12 19:46:47.564234 I Listening on TCP 0.0.0.0:5101
2017-04-12 19:46:47.564589 E Failed listening on TCP [::]:5001 - Error 10: Protocol type not supported
2017-04-12 19:46:47.564643 I Listening on TCP 0.0.0.0:5002
2017-04-12 19:46:47.565194 E Failed listening on TCP [::]:5101 - Error 10: Protocol type not supported
2017-04-12 19:46:47.565253 I Listening on TCP 0.0.0.0:5102
2017-04-12 19:46:47.565510 E Failed listening on TCP [::]:5002 - Error 10: Protocol type not supported
2017-04-12 19:46:47.565573 I Listening on TCP 0.0.0.0:5003
2017-04-12 19:46:47.565973 E Failed listening on TCP [::]:5102 - Error 10: Protocol type not supported
2017-04-12 19:46:47.566030 I Listening on TCP 0.0.0.0:5103
2017-04-12 19:46:47.566625 E Failed listening on TCP [::]:5003 - Error 10: Protocol type not supported
2017-04-12 19:46:47.566686 I Listening on TCP 0.0.0.0:5004
2017-04-12 19:46:47.566815 E Failed listening on TCP [::]:5103 - Error 10: Protocol type not supported
2017-04-12 19:46:47.566865 I Listening on TCP 0.0.0.0:5104
2017-04-12 19:46:47.567488 E Failed listening on TCP [::]:5004 - Error 10: Protocol type not supported
2017-04-12 19:46:47.567534 I Listening on TCP 0.0.0.0:5005
2017-04-12 19:46:47.567712 E Failed listening on TCP [::]:5104 - Error 10: Protocol type not supported
2017-04-12 19:46:47.567762 I Listening on TCP 0.0.0.0:5105
2017-04-12 19:46:47.568269 E Failed listening on TCP [::]:5005 - Error 10: Protocol type not supported
2017-04-12 19:46:47.568317 I Listening on TCP 0.0.0.0:5006
2017-04-12 19:46:47.568588 E Failed listening on TCP [::]:5105 - Error 10: Protocol type not supported
2017-04-12 19:46:47.568641 I Listening on TCP 0.0.0.0:5106
2017-04-12 19:46:47.568760 I Current MythTV Schema Version (DBSchemaVer): 1347
2017-04-12 19:46:47.569047 E Failed listening on TCP [::]:5006 - Error 10: Protocol type not supported
2017-04-12 19:46:47.569108 I Listening on TCP 0.0.0.0:5007
2017-04-12 19:46:47.569366 E Failed listening on TCP [::]:5106 - Error 10: Protocol type not supported
2017-04-12 19:46:47.569430 I Listening on TCP 0.0.0.0:5107
2017-04-12 19:46:47.569758 E Failed listening on TCP [::]:5007 - Error 10: Protocol type not supported
2017-04-12 19:46:47.569800 I Listening on TCP 0.0.0.0:5008
2017-04-12 19:46:47.573494 E Failed listening on TCP [::]:5008 - Error 10: Protocol type not supported
2017-04-12 19:46:47.573567 I Listening on TCP 0.0.0.0:5009
2017-04-12 19:46:47.574370 E Failed listening on TCP [::]:5009 - Error 10: Protocol type not supported
2017-04-12 19:46:47.574423 I Listening on TCP 0.0.0.0:5010
2017-04-12 19:46:47.575118 E Failed listening on TCP [::]:5010 - Error 10: Protocol type not supported
2017-04-12 19:46:47.575166 I Listening on TCP 0.0.0.0:5011
2017-04-12 19:46:47.575354 I FilterManager: GetFilterInfo(greedyhdeint) returning: 0x2580f10
2017-04-12 19:46:47.575364 I FilterManager: GetFilterInfo(greedyhdoubleprocessdeint) returning: 0x1ff0de0
2017-04-12 19:46:47.575863 E Failed listening on TCP [::]:5011 - Error 10: Protocol type not supported
2017-04-12 19:46:47.575919 I Listening on TCP 0.0.0.0:5012
2017-04-12 19:46:47.576136 I VDP: decoder<->render support: ffmpeg null opengl opengl-lite vdpau nullvdpau nullvaapi openglvaapi
2017-04-12 19:46:47.576144 I VDP: decoder<->render support: vdpau vdpau nullvdpau
2017-04-12 19:46:47.576150 I VDP: decoder<->render support: vaapi nullvaapi openglvaapi
2017-04-12 19:46:47.576615 E Failed listening on TCP [::]:5012 - Error 10: Protocol type not supported
2017-04-12 19:46:47.576660 I Listening on TCP 0.0.0.0:5013
2017-04-12 19:46:47.576906 E Failed listening on TCP [::]:5107 - Error 10: Protocol type not supported
2017-04-12 19:46:47.576961 I Listening on TCP 0.0.0.0:5108
2017-04-12 19:46:47.577345 E Failed listening on TCP [::]:5013 - Error 10: Protocol type not supported
2017-04-12 19:46:47.577388 I Listening on TCP 0.0.0.0:5014
2017-04-12 19:46:47.577660 E Failed listening on TCP [::]:5108 - Error 10: Protocol type not supported
2017-04-12 19:46:47.577710 I Listening on TCP 0.0.0.0:5109
2017-04-12 19:46:47.578117 E Failed listening on TCP [::]:5014 - Error 10: Protocol type not supported
2017-04-12 19:46:47.578169 I Listening on TCP 0.0.0.0:5015
2017-04-12 19:46:47.578399 E Failed listening on TCP [::]:5109 - Error 10: Protocol type not supported
2017-04-12 19:46:47.578451 I Listening on TCP 0.0.0.0:5110
2017-04-12 19:46:47.578880 E Failed listening on TCP [::]:5015 - Error 10: Protocol type not supported
2017-04-12 19:46:47.578921 I Listening on TCP 0.0.0.0:5016
2017-04-12 19:46:47.579132 E Failed listening on TCP [::]:5110 - Error 10: Protocol type not supported
2017-04-12 19:46:47.579184 I Listening on TCP 0.0.0.0:5111
2017-04-12 19:46:47.579615 E Failed listening on TCP [::]:5016 - Error 10: Protocol type not supported
2017-04-12 19:46:47.579658 I Listening on TCP 0.0.0.0:5017
2017-04-12 19:46:47.579851 E Failed listening on TCP [::]:5111 - Error 10: Protocol type not supported
2017-04-12 19:46:47.579903 I Listening on TCP 0.0.0.0:5112
2017-04-12 19:46:47.580358 E Failed listening on TCP [::]:5017 - Error 10: Protocol type not supported
2017-04-12 19:46:47.580399 I Listening on TCP 0.0.0.0:5018
2017-04-12 19:46:47.580542 N VDP: Ignoring profile item 962 (renderer xv-blit is not supported w/decoder ffmpeg (supported: null,opengl,opengl-lite,vdpau,nullvdpau,nullvaapi,openglvaapi))
2017-04-12 19:46:47.580579 E Failed listening on TCP [::]:5112 - Error 10: Protocol type not supported
2017-04-12 19:46:47.580629 I Listening on TCP 0.0.0.0:5113
2017-04-12 19:46:47.580691 N VDP: Ignoring profile item 963 (renderer xv-blit is not supported w/decoder ffmpeg (supported: null,opengl,opengl-lite,vdpau,nullvdpau,nullvaapi,openglvaapi))
2017-04-12 19:46:47.580735 N VDP: Ignoring profile item 964 (renderer quartz-blit is not supported w/decoder ffmpeg (supported: null,opengl,opengl-lite,vdpau,nullvdpau,nullvaapi,openglvaapi))
2017-04-12 19:46:47.580787 N VDP: Ignoring profile item 965 (renderer quartz-blit is not supported w/decoder ffmpeg (supported: null,opengl,opengl-lite,vdpau,nullvdpau,nullvaapi,openglvaapi))
2017-04-12 19:46:47.581120 E Failed listening on TCP [::]:5018 - Error 10: Protocol type not supported
2017-04-12 19:46:47.581173 I Listening on TCP 0.0.0.0:5019
2017-04-12 19:46:47.581310 E Failed listening on TCP [::]:5113 - Error 10: Protocol type not supported
2017-04-12 19:46:47.581363 I Listening on TCP 0.0.0.0:5114
2017-04-12 19:46:47.581894 E Failed listening on TCP [::]:5019 - Error 10: Protocol type not supported
2017-04-12 19:46:47.581946 I Listening on TCP 0.0.0.0:5020
2017-04-12 19:46:47.582016 N VDP: Ignoring profile item 966 (renderer xv-blit is not supported w/decoder ffmpeg (supported: null,opengl,opengl-lite,vdpau,nullvdpau,nullvaapi,openglvaapi))
2017-04-12 19:46:47.582044 E Failed listening on TCP [::]:5114 - Error 10: Protocol type not supported
2017-04-12 19:46:47.582096 I Listening on TCP 0.0.0.0:5115
2017-04-12 19:46:47.582151 N VDP: Ignoring profile item 967 (renderer xv-blit is not supported w/decoder ffmpeg (supported: null,opengl,opengl-lite,vdpau,nullvdpau,nullvaapi,openglvaapi))
2017-04-12 19:46:47.582193 N VDP: Ignoring profile item 968 (renderer quartz-blit is not supported w/decoder ffmpeg (supported: null,opengl,opengl-lite,vdpau,nullvdpau,nullvaapi,openglvaapi))
2017-04-12 19:46:47.582232 N VDP: Ignoring profile item 969 (renderer quartz-blit is not supported w/decoder ffmpeg (supported: null,opengl,opengl-lite,vdpau,nullvdpau,nullvaapi,openglvaapi))
2017-04-12 19:46:47.582681 E Failed listening on TCP [::]:5020 - Error 10: Protocol type not supported
2017-04-12 19:46:47.582743 I Listening on TCP 0.0.0.0:5021
2017-04-12 19:46:47.582760 E Failed listening on TCP [::]:5115 - Error 10: Protocol type not supported
2017-04-12 19:46:47.582805 I Listening on TCP 0.0.0.0:5116
2017-04-12 19:46:47.583430 E Failed listening on TCP [::]:5021 - Error 10: Protocol type not supported
2017-04-12 19:46:47.583483 I Listening on TCP 0.0.0.0:5022
2017-04-12 19:46:47.583485 E Failed listening on TCP [::]:5116 - Error 10: Protocol type not supported
2017-04-12 19:46:47.583528 I Listening on TCP 0.0.0.0:5117
2017-04-12 19:46:47.584183 E Failed listening on TCP [::]:5022 - Error 10: Protocol type not supported
2017-04-12 19:46:47.584229 E Failed listening on TCP [::]:5117 - Error 10: Protocol type not supported
2017-04-12 19:46:47.584236 I Listening on TCP 0.0.0.0:5023
2017-04-12 19:46:47.584270 I Listening on TCP 0.0.0.0:5118
2017-04-12 19:46:47.584384 N VDP: Ignoring profile item 970 (renderer xv-blit is not supported w/decoder ffmpeg (supported: null,opengl,opengl-lite,vdpau,nullvdpau,nullvaapi,openglvaapi))
2017-04-12 19:46:47.584431 N VDP: Ignoring profile item 971 (renderer xv-blit is not supported w/decoder ffmpeg (supported: null,opengl,opengl-lite,vdpau,nullvdpau,nullvaapi,openglvaapi))
2017-04-12 19:46:47.584470 N VDP: Ignoring profile item 972 (renderer quartz-blit is not supported w/decoder ffmpeg (supported: null,opengl,opengl-lite,vdpau,nullvdpau,nullvaapi,openglvaapi))
2017-04-12 19:46:47.584508 N VDP: Ignoring profile item 973 (renderer quartz-blit is not supported w/decoder ffmpeg (supported: null,opengl,opengl-lite,vdpau,nullvdpau,nullvaapi,openglvaapi))
2017-04-12 19:46:47.584949 E Failed listening on TCP [::]:5023 - Error 10: Protocol type not supported
2017-04-12 19:46:47.584970 E Failed listening on TCP [::]:5118 - Error 10: Protocol type not supported
2017-04-12 19:46:47.584999 I Listening on TCP 0.0.0.0:5024
2017-04-12 19:46:47.585009 I Listening on TCP 0.0.0.0:5119
2017-04-12 19:46:47.585706 E Failed listening on TCP [::]:5024 - Error 10: Protocol type not supported
2017-04-12 19:46:47.585752 I Listening on TCP 0.0.0.0:5025
2017-04-12 19:46:47.585766 E Failed listening on TCP [::]:5119 - Error 10: Protocol type not supported
2017-04-12 19:46:47.585809 I Listening on TCP 0.0.0.0:5120
2017-04-12 19:46:47.586439 E Failed listening on TCP [::]:5025 - Error 10: Protocol type not supported
2017-04-12 19:46:47.586488 I Listening on TCP 0.0.0.0:5026
2017-04-12 19:46:47.586516 E Failed listening on TCP [::]:5120 - Error 10: Protocol type not supported
2017-04-12 19:46:47.586561 I Listening on TCP 0.0.0.0:5121
2017-04-12 19:46:47.587198 E Failed listening on TCP [::]:5026 - Error 10: Protocol type not supported
2017-04-12 19:46:47.587251 I Listening on TCP 0.0.0.0:5027
2017-04-12 19:46:47.587279 E Failed listening on TCP [::]:5121 - Error 10: Protocol type not supported
2017-04-12 19:46:47.587327 I Listening on TCP 0.0.0.0:5122
2017-04-12 19:46:47.587966 E Failed listening on TCP [::]:5027 - Error 10: Protocol type not supported
2017-04-12 19:46:47.588012 I Listening on TCP 0.0.0.0:5028
2017-04-12 19:46:47.588041 E Failed listening on TCP [::]:5122 - Error 10: Protocol type not supported
2017-04-12 19:46:47.588090 I Listening on TCP 0.0.0.0:5123
2017-04-12 19:46:47.588719 E Failed listening on TCP [::]:5028 - Error 10: Protocol type not supported
2017-04-12 19:46:47.588776 I Listening on TCP 0.0.0.0:5029
2017-04-12 19:46:47.588804 E Failed listening on TCP [::]:5123 - Error 10: Protocol type not supported
2017-04-12 19:46:47.588847 I Listening on TCP 0.0.0.0:5124
2017-04-12 19:46:47.589480 E Failed listening on TCP [::]:5029 - Error 10: Protocol type not supported
2017-04-12 19:46:47.589527 I Listening on TCP 0.0.0.0:5030
2017-04-12 19:46:47.589553 E Failed listening on TCP [::]:5124 - Error 10: Protocol type not supported
2017-04-12 19:46:47.589600 I Listening on TCP 0.0.0.0:5125
2017-04-12 19:46:47.590261 E Failed listening on TCP [::]:5030 - Error 10: Protocol type not supported
2017-04-12 19:46:47.590320 I Listening on TCP 0.0.0.0:5031
2017-04-12 19:46:47.590345 E Failed listening on TCP [::]:5125 - Error 10: Protocol type not supported
2017-04-12 19:46:47.590390 I Listening on TCP 0.0.0.0:5126
2017-04-12 19:46:47.591098 E Failed listening on TCP [::]:5031 - Error 10: Protocol type not supported
2017-04-12 19:46:47.591152 I Listening on TCP 0.0.0.0:5032
2017-04-12 19:46:47.591178 E Failed listening on TCP [::]:5126 - Error 10: Protocol type not supported
2017-04-12 19:46:47.591221 I Listening on TCP 0.0.0.0:5127
2017-04-12 19:46:47.591932 E Failed listening on TCP [::]:5032 - Error 10: Protocol type not supported
2017-04-12 19:46:47.591933 E Failed listening on TCP [::]:5127 - Error 10: Protocol type not supported
2017-04-12 19:46:47.592004 I Listening on TCP 0.0.0.0:5128
2017-04-12 19:46:47.592007 I Listening on TCP 0.0.0.0:5033
2017-04-12 19:46:47.592750 E Failed listening on TCP [::]:5128 - Error 10: Protocol type not supported
2017-04-12 19:46:47.592751 E Failed listening on TCP [::]:5033 - Error 10: Protocol type not supported
2017-04-12 19:46:47.592819 I Listening on TCP 0.0.0.0:5034
2017-04-12 19:46:47.592822 I Listening on TCP 0.0.0.0:5129
2017-04-12 19:46:47.593575 E Failed listening on TCP [::]:5129 - Error 10: Protocol type not supported
2017-04-12 19:46:47.593650 I Listening on TCP 0.0.0.0:5130
2017-04-12 19:46:47.593901 E Failed listening on TCP [::]:5034 - Error 10: Protocol type not supported
2017-04-12 19:46:47.593960 I Listening on TCP 0.0.0.0:5035
2017-04-12 19:46:47.594778 E Failed listening on TCP [::]:5035 - Error 10: Protocol type not supported
2017-04-12 19:46:47.594857 I Listening on TCP 0.0.0.0:5036
2017-04-12 19:46:47.595295 E Failed listening on TCP [::]:5130 - Error 10: Protocol type not supported
2017-04-12 19:46:47.595359 I Listening on TCP 0.0.0.0:5131
2017-04-12 19:46:47.595577 E Failed listening on TCP [::]:5036 - Error 10: Protocol type not supported
2017-04-12 19:46:47.595630 I Listening on TCP 0.0.0.0:5037
2017-04-12 19:46:47.596088 E Failed listening on TCP [::]:5131 - Error 10: Protocol type not supported
2017-04-12 19:46:47.596146 I Listening on TCP 0.0.0.0:5132
2017-04-12 19:46:47.596300 E Failed listening on TCP [::]:5037 - Error 10: Protocol type not supported
2017-04-12 19:46:47.596355 I Listening on TCP 0.0.0.0:5038
2017-04-12 19:46:47.596857 E Failed listening on TCP [::]:5132 - Error 10: Protocol type not supported
2017-04-12 19:46:47.596912 I Listening on TCP 0.0.0.0:5133
2017-04-12 19:46:47.597033 E Failed listening on TCP [::]:5038 - Error 10: Protocol type not supported
2017-04-12 19:46:47.597089 I Listening on TCP 0.0.0.0:5039
2017-04-12 19:46:47.597685 E Failed listening on TCP [::]:5133 - Error 10: Protocol type not supported
2017-04-12 19:46:47.597747 I Listening on TCP 0.0.0.0:5134
2017-04-12 19:46:47.597787 E Failed listening on TCP [::]:5039 - Error 10: Protocol type not supported
2017-04-12 19:46:47.597839 I Listening on TCP 0.0.0.0:5040
2017-04-12 19:46:47.598485 E Failed listening on TCP [::]:5134 - Error 10: Protocol type not supported
2017-04-12 19:46:47.598509 E Failed listening on TCP [::]:5040 - Error 10: Protocol type not supported
2017-04-12 19:46:47.598548 I Listening on TCP 0.0.0.0:5135
2017-04-12 19:46:47.598551 I Listening on TCP 0.0.0.0:5041
2017-04-12 19:46:47.599269 E Failed listening on TCP [::]:5041 - Error 10: Protocol type not supported
2017-04-12 19:46:47.599273 E Failed listening on TCP [::]:5135 - Error 10: Protocol type not supported
2017-04-12 19:46:47.599346 I Listening on TCP 0.0.0.0:5042
2017-04-12 19:46:47.599346 I Listening on TCP 0.0.0.0:5136
2017-04-12 19:46:47.600087 E Failed listening on TCP [::]:5136 - Error 10: Protocol type not supported
2017-04-12 19:46:47.600145 I Listening on TCP 0.0.0.0:5137
2017-04-12 19:46:47.600172 E Failed listening on TCP [::]:5042 - Error 10: Protocol type not supported
2017-04-12 19:46:47.600217 I Listening on TCP 0.0.0.0:5043
2017-04-12 19:46:47.600958 E Failed listening on TCP [::]:5137 - Error 10: Protocol type not supported
2017-04-12 19:46:47.601029 I Listening on TCP 0.0.0.0:5138
2017-04-12 19:46:47.601062 E Failed listening on TCP [::]:5043 - Error 10: Protocol type not supported
2017-04-12 19:46:47.601105 I Listening on TCP 0.0.0.0:5044
2017-04-12 19:46:47.601873 E Failed listening on TCP [::]:5138 - Error 10: Protocol type not supported
2017-04-12 19:46:47.601944 I Listening on TCP 0.0.0.0:5139
2017-04-12 19:46:47.601970 E Failed listening on TCP [::]:5044 - Error 10: Protocol type not supported
2017-04-12 19:46:47.602016 I Listening on TCP 0.0.0.0:5045
2017-04-12 19:46:47.602780 E Failed listening on TCP [::]:5139 - Error 10: Protocol type not supported
2017-04-12 19:46:47.602847 I Listening on TCP 0.0.0.0:5140
2017-04-12 19:46:47.602880 E Failed listening on TCP [::]:5045 - Error 10: Protocol type not supported
2017-04-12 19:46:47.602927 I Listening on TCP 0.0.0.0:5046
2017-04-12 19:46:47.603703 E Failed listening on TCP [::]:5140 - Error 10: Protocol type not supported
2017-04-12 19:46:47.603798 E Failed listening on TCP [::]:5046 - Error 10: Protocol type not supported
2017-04-12 19:46:47.603851 I Listening on TCP 0.0.0.0:5141
2017-04-12 19:46:47.603882 I Listening on TCP 0.0.0.0:5047
2017-04-12 19:46:47.604680 E Failed listening on TCP [::]:5047 - Error 10: Protocol type not supported
2017-04-12 19:46:47.604752 I Listening on TCP 0.0.0.0:5048
2017-04-12 19:46:47.604769 E Failed listening on TCP [::]:5141 - Error 10: Protocol type not supported
2017-04-12 19:46:47.604845 I Listening on TCP 0.0.0.0:5142
2017-04-12 19:46:47.605424 E Failed listening on TCP [::]:5142 - Error 10: Protocol type not supported
2017-04-12 19:46:47.605465 I Listening on TCP 0.0.0.0:5143
2017-04-12 19:46:47.605524 E Failed listening on TCP [::]:5048 - Error 10: Protocol type not supported
2017-04-12 19:46:47.605576 I Listening on TCP 0.0.0.0:5049
2017-04-12 19:46:47.606063 E Failed listening on TCP [::]:5143 - Error 10: Protocol type not supported
2017-04-12 19:46:47.606101 I Listening on TCP 0.0.0.0:5144
2017-04-12 19:46:47.606300 E Failed listening on TCP [::]:5049 - Error 10: Protocol type not supported
2017-04-12 19:46:47.606337 I Listening on TCP 0.0.0.0:5050
2017-04-12 19:46:47.606886 E Failed listening on TCP [::]:5144 - Error 10: Protocol type not supported
2017-04-12 19:46:47.606945 I Listening on TCP 0.0.0.0:5145
2017-04-12 19:46:47.607045 E Failed listening on TCP [::]:5050 - Error 10: Protocol type not supported
2017-04-12 19:46:47.607080 I Listening on TCP 0.0.0.0:5051
2017-04-12 19:46:47.607675 E Failed listening on TCP [::]:5145 - Error 10: Protocol type not supported
2017-04-12 19:46:47.607733 I Listening on TCP 0.0.0.0:5146
2017-04-12 19:46:47.608540 E Failed listening on TCP [::]:5146 - Error 10: Protocol type not supported
2017-04-12 19:46:47.608598 I Listening on TCP 0.0.0.0:5147
2017-04-12 19:46:47.609347 E Failed listening on TCP [::]:5147 - Error 10: Protocol type not supported
2017-04-12 19:46:47.609408 I Listening on TCP 0.0.0.0:5148
2017-04-12 19:46:47.610120 E Failed listening on TCP [::]:5148 - Error 10: Protocol type not supported
2017-04-12 19:46:47.610182 I Listening on TCP 0.0.0.0:5149
2017-04-12 19:46:47.610785 E Failed listening on TCP [::]:5051 - Error 10: Protocol type not supported
2017-04-12 19:46:47.610848 I Listening on TCP 0.0.0.0:5052
2017-04-12 19:46:47.611274 E Failed listening on TCP [::]:5149 - Error 10: Protocol type not supported
2017-04-12 19:46:47.611330 I Listening on TCP 0.0.0.0:5150
2017-04-12 19:46:47.611559 E Failed listening on TCP [::]:5052 - Error 10: Protocol type not supported
2017-04-12 19:46:47.611611 I Listening on TCP 0.0.0.0:5053
2017-04-12 19:46:47.612240 E Failed listening on TCP [::]:5150 - Error 10: Protocol type not supported
2017-04-12 19:46:47.612296 I Listening on TCP 0.0.0.0:5151
2017-04-12 19:46:47.612298 E Failed listening on TCP [::]:5053 - Error 10: Protocol type not supported
2017-04-12 19:46:47.612351 I Listening on TCP 0.0.0.0:5054
2017-04-12 19:46:47.613052 E Failed listening on TCP [::]:5151 - Error 10: Protocol type not supported
2017-04-12 19:46:47.613110 I Listening on TCP 0.0.0.0:5152
2017-04-12 19:46:47.613408 E Failed listening on TCP [::]:5054 - Error 10: Protocol type not supported
2017-04-12 19:46:47.613459 I Listening on TCP 0.0.0.0:5055
2017-04-12 19:46:47.613905 E Failed listening on TCP [::]:5152 - Error 10: Protocol type not supported
2017-04-12 19:46:47.613961 I Listening on TCP 0.0.0.0:5153
2017-04-12 19:46:47.614487 E Failed listening on TCP [::]:5055 - Error 10: Protocol type not supported
2017-04-12 19:46:47.614553 I Listening on TCP 0.0.0.0:5056
2017-04-12 19:46:47.614775 E Failed listening on TCP [::]:5153 - Error 10: Protocol type not supported
2017-04-12 19:46:47.614827 I Listening on TCP 0.0.0.0:5154
2017-04-12 19:46:47.615564 E Failed listening on TCP [::]:5154 - Error 10: Protocol type not supported
2017-04-12 19:46:47.615636 I Listening on TCP 0.0.0.0:5155
2017-04-12 19:46:47.616752 E Failed listening on TCP [::]:5155 - Error 10: Protocol type not supported
2017-04-12 19:46:47.616821 I Listening on TCP 0.0.0.0:5156
2017-04-12 19:46:47.617882 E Failed listening on TCP [::]:5156 - Error 10: Protocol type not supported
2017-04-12 19:46:47.617964 I Listening on TCP 0.0.0.0:5157
2017-04-12 19:46:47.618935 E Failed listening on TCP [::]:5157 - Error 10: Protocol type not supported
2017-04-12 19:46:47.618998 I Listening on TCP 0.0.0.0:5158
2017-04-12 19:46:47.619874 E Failed listening on TCP [::]:5158 - Error 10: Protocol type not supported
2017-04-12 19:46:47.619931 I Listening on TCP 0.0.0.0:5159
2017-04-12 19:46:47.620803 E Failed listening on TCP [::]:5159 - Error 10: Protocol type not supported
2017-04-12 19:46:47.620859 I Listening on TCP 0.0.0.0:5160
2017-04-12 19:46:47.621752 E Failed listening on TCP [::]:5160 - Error 10: Protocol type not supported
2017-04-12 19:46:47.621807 I Listening on TCP 0.0.0.0:5161
2017-04-12 19:46:47.622678 E Failed listening on TCP [::]:5161 - Error 10: Protocol type not supported
2017-04-12 19:46:47.622735 I Listening on TCP 0.0.0.0:5162
2017-04-12 19:46:47.623711 E Failed listening on TCP [::]:5162 - Error 10: Protocol type not supported
2017-04-12 19:46:47.623783 I Listening on TCP 0.0.0.0:5163
2017-04-12 19:46:47.624622 E Failed listening on TCP [::]:5163 - Error 10: Protocol type not supported
2017-04-12 19:46:47.624684 I Listening on TCP 0.0.0.0:5164
2017-04-12 19:46:47.625541 E Failed listening on TCP [::]:5164 - Error 10: Protocol type not supported
2017-04-12 19:46:47.625595 I Listening on TCP 0.0.0.0:5165
2017-04-12 19:46:47.626582 E Failed listening on TCP [::]:5165 - Error 10: Protocol type not supported
2017-04-12 19:46:47.626646 I Listening on TCP 0.0.0.0:5166
2017-04-12 19:46:47.627597 E Failed listening on TCP [::]:5166 - Error 10: Protocol type not supported
2017-04-12 19:46:47.627655 I Listening on TCP 0.0.0.0:5167
2017-04-12 19:46:47.628270 E Failed listening on TCP [::]:5056 - Error 10: Protocol type not supported
2017-04-12 19:46:47.628326 I Listening on TCP 0.0.0.0:5057
2017-04-12 19:46:47.628937 E Failed listening on TCP [::]:5057 - Error 10: Protocol type not supported
2017-04-12 19:46:47.628983 I Listening on TCP 0.0.0.0:5058
2017-04-12 19:46:47.629536 E Failed listening on TCP [::]:5058 - Error 10: Protocol type not supported
2017-04-12 19:46:47.629591 I Listening on TCP 0.0.0.0:5059
2017-04-12 19:46:47.630153 E Failed listening on TCP [::]:5059 - Error 10: Protocol type not supported
2017-04-12 19:46:47.630199 I Listening on TCP 0.0.0.0:5060
2017-04-12 19:46:47.631106 E Failed listening on TCP [::]:5060 - Error 10: Protocol type not supported
2017-04-12 19:46:47.631162 I Listening on TCP 0.0.0.0:5061
2017-04-12 19:46:47.631381 E Failed listening on TCP [::]:5167 - Error 10: Protocol type not supported
2017-04-12 19:46:47.631438 I Listening on TCP 0.0.0.0:5168
2017-04-12 19:46:47.631838 E Failed listening on TCP [::]:5061 - Error 10: Protocol type not supported
2017-04-12 19:46:47.631898 I Listening on TCP 0.0.0.0:5062
2017-04-12 19:46:47.632125 E Failed listening on TCP [::]:5168 - Error 10: Protocol type not supported
2017-04-12 19:46:47.632163 I Listening on TCP 0.0.0.0:5169
2017-04-12 19:46:47.632677 E Failed listening on TCP [::]:5169 - Error 10: Protocol type not supported
2017-04-12 19:46:47.632719 I Listening on TCP 0.0.0.0:5170
2017-04-12 19:46:47.633229 E Failed listening on TCP [::]:5170 - Error 10: Protocol type not supported
2017-04-12 19:46:47.633268 I Listening on TCP 0.0.0.0:5171
2017-04-12 19:46:47.633771 E Failed listening on TCP [::]:5171 - Error 10: Protocol type not supported
2017-04-12 19:46:47.633808 I Listening on TCP 0.0.0.0:5172
2017-04-12 19:46:47.634315 E Failed listening on TCP [::]:5172 - Error 10: Protocol type not supported
2017-04-12 19:46:47.634355 I Listening on TCP 0.0.0.0:5173
2017-04-12 19:46:47.634855 E Failed listening on TCP [::]:5173 - Error 10: Protocol type not supported
2017-04-12 19:46:47.634893 I Listening on TCP 0.0.0.0:5174
2017-04-12 19:46:47.640123 E Failed listening on TCP [::]:5174 - Error 10: Protocol type not supported
2017-04-12 19:46:47.640214 I Listening on TCP 0.0.0.0:5175
2017-04-12 19:46:47.640603 E Failed listening on TCP [::]:5062 - Error 10: Protocol type not supported
2017-04-12 19:46:47.640669 I Listening on TCP 0.0.0.0:5063
2017-04-12 19:46:47.641147 E Failed listening on TCP [::]:5175 - Error 10: Protocol type not supported
2017-04-12 19:46:47.641201 I Listening on TCP 0.0.0.0:5176
2017-04-12 19:46:47.641435 E Failed listening on TCP [::]:5063 - Error 10: Protocol type not supported
2017-04-12 19:46:47.641492 I Listening on TCP 0.0.0.0:5064
2017-04-12 19:46:47.642058 E Failed listening on TCP [::]:5176 - Error 10: Protocol type not supported
2017-04-12 19:46:47.642116 I Listening on TCP 0.0.0.0:5177
2017-04-12 19:46:47.642238 E Failed listening on TCP [::]:5064 - Error 10: Protocol type not supported
2017-04-12 19:46:47.642292 I Listening on TCP 0.0.0.0:5065
2017-04-12 19:46:47.642964 E Failed listening on TCP [::]:5177 - Error 10: Protocol type not supported
2017-04-12 19:46:47.643023 I Listening on TCP 0.0.0.0:5178
2017-04-12 19:46:47.643054 E Failed listening on TCP [::]:5065 - Error 10: Protocol type not supported
2017-04-12 19:46:47.643100 I Listening on TCP 0.0.0.0:5066
2017-04-12 19:46:47.643856 E Failed listening on TCP [::]:5178 - Error 10: Protocol type not supported
2017-04-12 19:46:47.643929 I Listening on TCP 0.0.0.0:5179
2017-04-12 19:46:47.644662 E Failed listening on TCP [::]:5066 - Error 10: Protocol type not supported
2017-04-12 19:46:47.644728 I Listening on TCP 0.0.0.0:5067
2017-04-12 19:46:47.644770 E Failed listening on TCP [::]:5179 - Error 10: Protocol type not supported
2017-04-12 19:46:47.644816 I Listening on TCP 0.0.0.0:5180
2017-04-12 19:46:47.645568 E Failed listening on TCP [::]:5180 - Error 10: Protocol type not supported
2017-04-12 19:46:47.645627 I Listening on TCP 0.0.0.0:5181
2017-04-12 19:46:47.646343 E Failed listening on TCP [::]:5181 - Error 10: Protocol type not supported
2017-04-12 19:46:47.646399 I Listening on TCP 0.0.0.0:5182
2017-04-12 19:46:47.647121 E Failed listening on TCP [::]:5182 - Error 10: Protocol type not supported
2017-04-12 19:46:47.647180 I Listening on TCP 0.0.0.0:5183
2017-04-12 19:46:47.648000 E Failed listening on TCP [::]:5183 - Error 10: Protocol type not supported
2017-04-12 19:46:47.648070 I Listening on TCP 0.0.0.0:5184
2017-04-12 19:46:47.648415 E Failed listening on TCP [::]:5067 - Error 10: Protocol type not supported
2017-04-12 19:46:47.648472 I Listening on TCP 0.0.0.0:5068
2017-04-12 19:46:47.648791 E Failed listening on TCP [::]:5184 - Error 10: Protocol type not supported
2017-04-12 19:46:47.648841 I Listening on TCP 0.0.0.0:5185
2017-04-12 19:46:47.649699 E Failed listening on TCP [::]:5185 - Error 10: Protocol type not supported
2017-04-12 19:46:47.649757 I Listening on TCP 0.0.0.0:5186
2017-04-12 19:46:47.654186 E Failed listening on TCP [::]:5068 - Error 10: Protocol type not supported
2017-04-12 19:46:47.654266 I Listening on TCP 0.0.0.0:5069
2017-04-12 19:46:47.654295 E Failed listening on TCP [::]:5186 - Error 10: Protocol type not supported
2017-04-12 19:46:47.654343 I Listening on TCP 0.0.0.0:5187
2017-04-12 19:46:47.655136 E Failed listening on TCP [::]:5069 - Error 10: Protocol type not supported
2017-04-12 19:46:47.655194 I Listening on TCP 0.0.0.0:5070
2017-04-12 19:46:47.661567 E Failed listening on TCP [::]:5070 - Error 10: Protocol type not supported
2017-04-12 19:46:47.661643 I Listening on TCP 0.0.0.0:5071
2017-04-12 19:46:47.669570 E Failed listening on TCP [::]:5187 - Error 10: Protocol type not supported
2017-04-12 19:46:47.669650 I Listening on TCP 0.0.0.0:5188
2017-04-12 19:46:47.671578 E Failed listening on TCP [::]:5071 - Error 10: Protocol type not supported
2017-04-12 19:46:47.671657 I Listening on TCP 0.0.0.0:5072
2017-04-12 19:46:47.671951 E Failed listening on TCP [::]:5188 - Error 10: Protocol type not supported
2017-04-12 19:46:47.671989 I Listening on TCP 0.0.0.0:5189
2017-04-12 19:46:47.672702 E Failed listening on TCP [::]:5189 - Error 10: Protocol type not supported
2017-04-12 19:46:47.672742 I Listening on TCP 0.0.0.0:5190
2017-04-12 19:46:47.673444 E Failed listening on TCP [::]:5190 - Error 10: Protocol type not supported
2017-04-12 19:46:47.673484 I Listening on TCP 0.0.0.0:5191
2017-04-12 19:46:47.674191 E Failed listening on TCP [::]:5191 - Error 10: Protocol type not supported
2017-04-12 19:46:47.674232 I Listening on TCP 0.0.0.0:5192
2017-04-12 19:46:47.675181 E Failed listening on TCP [::]:5192 - Error 10: Protocol type not supported
2017-04-12 19:46:47.675242 I Listening on TCP 0.0.0.0:5193
2017-04-12 19:46:47.678198 E Failed listening on TCP [::]:5072 - Error 10: Protocol type not supported
2017-04-12 19:46:47.678271 I Listening on TCP 0.0.0.0:5073
2017-04-12 19:46:47.679460 E Failed listening on TCP [::]:5193 - Error 10: Protocol type not supported
2017-04-12 19:46:47.679525 I Listening on TCP 0.0.0.0:5194
2017-04-12 19:46:47.685535 E Failed listening on TCP [::]:5194 - Error 10: Protocol type not supported
2017-04-12 19:46:47.685616 I Listening on TCP 0.0.0.0:5195
2017-04-12 19:46:47.688412 E Failed listening on TCP [::]:5195 - Error 10: Protocol type not supported
2017-04-12 19:46:47.688482 I Listening on TCP 0.0.0.0:5196
2017-04-12 19:46:47.691569 E Failed listening on TCP [::]:5196 - Error 10: Protocol type not supported
2017-04-12 19:46:47.691648 I Listening on TCP 0.0.0.0:5197
2017-04-12 19:46:47.701663 E Failed listening on TCP [::]:5073 - Error 10: Protocol type not supported
2017-04-12 19:46:47.701741 I Listening on TCP 0.0.0.0:5074
2017-04-12 19:46:47.702472 E Failed listening on TCP [::]:5197 - Error 10: Protocol type not supported
2017-04-12 19:46:47.702541 I Listening on TCP 0.0.0.0:5198
2017-04-12 19:46:47.716396 E Failed listening on TCP [::]:5074 - Error 10: Protocol type not supported
2017-04-12 19:46:47.716474 I Listening on TCP 0.0.0.0:5075
2017-04-12 19:46:47.717216 E Failed listening on TCP [::]:5198 - Error 10: Protocol type not supported
2017-04-12 19:46:47.717285 I Listening on TCP 0.0.0.0:5199
2017-04-12 19:46:47.725547 E Failed listening on TCP [::]:5199 - Error 10: Protocol type not supported
2017-04-12 19:46:47.725583 E AirPlay: Failed to find a port for incoming connections.
2017-04-12 19:46:47.728322 E Failed listening on TCP [::]:5075 - Error 10: Protocol type not supported
2017-04-12 19:46:47.728398 I Listening on TCP 0.0.0.0:5076
2017-04-12 19:46:47.729000 E Failed listening on TCP [::]:5076 - Error 10: Protocol type not supported
2017-04-12 19:46:47.729050 I Listening on TCP 0.0.0.0:5077
2017-04-12 19:46:47.729668 E Failed listening on TCP [::]:5077 - Error 10: Protocol type not supported
2017-04-12 19:46:47.729713 I Listening on TCP 0.0.0.0:5078
2017-04-12 19:46:47.730361 E Failed listening on TCP [::]:5078 - Error 10: Protocol type not supported
2017-04-12 19:46:47.730403 I Listening on TCP 0.0.0.0:5079
2017-04-12 19:46:47.730987 E Failed listening on TCP [::]:5079 - Error 10: Protocol type not supported
2017-04-12 19:46:47.731031 I Listening on TCP 0.0.0.0:5080
2017-04-12 19:46:47.731569 E Failed listening on TCP [::]:5080 - Error 10: Protocol type not supported
2017-04-12 19:46:47.731608 I Listening on TCP 0.0.0.0:5081
2017-04-12 19:46:47.732149 E Failed listening on TCP [::]:5081 - Error 10: Protocol type not supported
2017-04-12 19:46:47.732188 I Listening on TCP 0.0.0.0:5082
2017-04-12 19:46:47.732969 E Failed listening on TCP [::]:5082 - Error 10: Protocol type not supported
2017-04-12 19:46:47.733015 I Listening on TCP 0.0.0.0:5083
2017-04-12 19:46:47.733593 E Failed listening on TCP [::]:5083 - Error 10: Protocol type not supported
2017-04-12 19:46:47.733634 I Listening on TCP 0.0.0.0:5084
2017-04-12 19:46:47.734199 E Failed listening on TCP [::]:5084 - Error 10: Protocol type not supported
2017-04-12 19:46:47.734239 I Listening on TCP 0.0.0.0:5085
2017-04-12 19:46:47.734765 E Failed listening on TCP [::]:5085 - Error 10: Protocol type not supported
2017-04-12 19:46:47.734805 I Listening on TCP 0.0.0.0:5086
2017-04-12 19:46:47.735344 E Failed listening on TCP [::]:5086 - Error 10: Protocol type not supported
2017-04-12 19:46:47.735383 I Listening on TCP 0.0.0.0:5087
2017-04-12 19:46:47.735955 E Failed listening on TCP [::]:5087 - Error 10: Protocol type not supported
2017-04-12 19:46:47.735996 I Listening on TCP 0.0.0.0:5088
2017-04-12 19:46:47.736574 E Failed listening on TCP [::]:5088 - Error 10: Protocol type not supported
2017-04-12 19:46:47.736614 I Listening on TCP 0.0.0.0:5089
2017-04-12 19:46:47.737168 E Failed listening on TCP [::]:5089 - Error 10: Protocol type not supported
2017-04-12 19:46:47.737206 I Listening on TCP 0.0.0.0:5090
2017-04-12 19:46:47.737751 E Failed listening on TCP [::]:5090 - Error 10: Protocol type not supported
2017-04-12 19:46:47.737807 I Listening on TCP 0.0.0.0:5091
2017-04-12 19:46:47.738397 E Failed listening on TCP [::]:5091 - Error 10: Protocol type not supported
2017-04-12 19:46:47.738438 I Listening on TCP 0.0.0.0:5092
2017-04-12 19:46:47.739009 E Failed listening on TCP [::]:5092 - Error 10: Protocol type not supported
2017-04-12 19:46:47.739056 I Listening on TCP 0.0.0.0:5093
2017-04-12 19:46:47.739649 E Failed listening on TCP [::]:5093 - Error 10: Protocol type not supported
2017-04-12 19:46:47.739690 I Listening on TCP 0.0.0.0:5094
2017-04-12 19:46:47.740246 E Failed listening on TCP [::]:5094 - Error 10: Protocol type not supported
2017-04-12 19:46:47.740288 I Listening on TCP 0.0.0.0:5095
2017-04-12 19:46:47.740879 E Failed listening on TCP [::]:5095 - Error 10: Protocol type not supported
2017-04-12 19:46:47.740933 I Listening on TCP 0.0.0.0:5096
2017-04-12 19:46:47.741522 E Failed listening on TCP [::]:5096 - Error 10: Protocol type not supported
2017-04-12 19:46:47.741566 I Listening on TCP 0.0.0.0:5097
2017-04-12 19:46:47.742239 E Failed listening on TCP [::]:5097 - Error 10: Protocol type not supported
2017-04-12 19:46:47.742286 I Listening on TCP 0.0.0.0:5098
2017-04-12 19:46:47.743608 E Failed listening on TCP [::]:5098 - Error 10: Protocol type not supported
2017-04-12 19:46:47.743664 I Listening on TCP 0.0.0.0:5099
2017-04-12 19:46:47.744271 E Failed listening on TCP [::]:5099 - Error 10: Protocol type not supported
2017-04-12 19:46:47.744298 E RAOP Device: Failed to find a port for incoming connections.
2017-04-12 19:46:47.769251 W Key Alt+r is already bound to a jump point.
2017-04-12 19:46:47.770534 W Key Ctrl+W is bound to multiple actions in context TV Playback.
2017-04-12 19:46:47.771323 N Registering Internal as a media playback plugin.
2017-04-12 19:46:47.780479 N Registering WebBrowser as a media playback plugin.
2017-04-12 19:46:47.780567 E Error Loading en_us translation for module mythbrowser
2017-04-12 19:46:47.785439 E Error Loading en_us translation for module mythgame
2017-04-12 19:46:47.796863 I Current MythMusic Schema Version (MusicDBSchemaVer): 1024
2017-04-12 19:46:47.807684 I Loading en_us translation for module mythmusic
2017-04-12 19:46:47.808864 I Loading en_us translation for module mythnetvision
2017-04-12 19:46:47.811357 E Error Loading en_us translation for module mythnews
2017-04-12 19:46:47.815413 E Error Loading en_us translation for module mythweather
2017-04-12 19:46:47.818934 I Connecting to zm server: 192.168.1.254:6548 (try 1 of 2)
2017-04-12 19:46:48.820300 I Using protocol version 11
2017-04-12 19:46:48.863858 N Monitor: Salon (5) is using 3 bytes per pixel
2017-04-12 19:46:48.877556 E Error Loading en_us translation for module mythzoneminder
2017-04-12 19:46:48.880197 I Listening on TCP 0.0.0.0:6546
2017-04-12 19:46:48.880858 E Failed listening on TCP [::]:6546 - Error 10: Protocol type not supported
2017-04-12 19:46:48.880880 E NetworkControl failed to bind to port 6546.
2017-04-12 19:46:48.945421 N Found mainmenu.xml for theme 'MythMediaStream-v28.1'
2017-04-12 19:46:48.956333 I Registering HouseKeeperTask 'HardwareProfiler'.
2017-04-12 19:46:48.959908 I Starting HouseKeeper.
2017-04-12 19:46:49.087455 I Bonjour: Service registration complete: name 'Mythfrontend on FE-IntelNUC' type '_mythfrontend._tcp.' domain: 'local.'
_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-dev
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Q about networking after recent networking improvements in master [ In reply to ]
On 04/12/2017 01:52 PM, Piotr Oniszczuk wrote:
> Peter,
>
> After upgrade mythtv-master from r380 to r385 I started to have many following entries in FE log:
>
> ……………
> 2017-04-12 19:46:47.563426 E Failed listening on TCP [::]:5000 - Error 10: Protocol type not supported
> ……………
>
> see below full fe log
>
> My FE is minimyth2. It has no IPv6 compiled within kernel.
> Is it possible that this is cause?
>
> Or maybe new code needs to change something in BE config?
>
> Anyway - pls be aware that some users may have similar problem.
>
> If it is result of not adequate BE config - then I believe it is good practice to set new defaults in a way guarantying myth behavior exactly like before Your’s networking improvements.
> This may help to avoid storm of user complains about issue like this…

I assumed that everybody has IPV6.

From the QT5 page (http://blog.qt.io/blog/2011/07/05/ipv6-changes-in-qt5/)

/To further express that we take IPv6 seriously, I also have removed the
support to compile with QT_NO_IPV6. I think that every platform that Qt5
will run on also has support for IPv6.//
/
I have created a patch to disable IPv6 if it is not supported. Please
test with the attached patch.
It will turn on the flag to disable IPv6 if it gets a "not supported"
error when listening. So you will get only 1 such error message.

Peter
Re: Q about networking after recent networking improvements in master [ In reply to ]
On 04/12/2017 02:09 PM, Peter Bennett wrote:
...
> I assumed that everybody has IPV6...

Peter,

Probably true, but:

I recall a number of folks on IRC and the users list have disabled
IPv6 in order to get their backends running. Unfortunately, it was
probably the wrong solution, and now it's out there in the ether.

I just searched for: mythtv net.ipv6.conf.all.disable_ipv6 and got
a bunch of (old) matches. The ..._disable_ipv6.patch will help those
that never undid the disable. Maybe we need a new loglevel:
VB_JOIN_THE_CURRENT_CENTURY.

(I'm running IPv6 using ULAs with your 'Networking improvements'
commit and without this patch A-OK. Nice work.)

--
Bill
_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-dev
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Q about networking after recent networking improvements in master [ In reply to ]
> Wiadomo?? napisana przez Peter Bennett <pgbennett@comcast.net> w dniu 12.04.2017, o godz. 21:09:
>
>
>>
>
> I assumed that everybody has IPV6.
>
> From the QT5 page (http://blog.qt.io/blog/2011/07/05/ipv6-changes-in-qt5/)
>
> To further express that we take IPv6 seriously, I also have removed the support to compile with QT_NO_IPV6. I think that every platform that Qt5 will run on also has support for IPv6.
>
> I have created a patch to disable IPv6 if it is not supported. Please test with the attached patch.
> It will turn on the flag to disable IPv6 if it gets a "not supported" error when listening. So you will get only 1 such error message.
>
> Peter

Peter,
Thx. Patch helps!
So far - so good.
I’ll put r385 into production to make more tests of new networking code.
BTW: great work with #12229!
br

_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-dev
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Q about networking after recent networking improvements in master [ In reply to ]
On 04/12/2017 03:58 PM, Bill Meek wrote:
> (I'm running IPv6 using ULAs with your 'Networking improvements'
> commit and without this patch A-OK. Nice work.)

Hi Bill

How do you add the Unique local address to your systems?

I am thinking about updating the wiki IPV6 article and wondering about
the best way of doing it.

I have it working by creating a script and linking it to
/etc/network/if-up.d/010addipaddress. In that script I run a command ip
-6 address add $ipadd dev "$ifacename" with appropriate parameters. I
created a table of ULAs and MAC addresses. This works well, I get the
automatic Global IPv6 address from Comcast plus the ULA that I set up.

I could not find a more user-friendly way to do it with NetworkManager.
It allows automatic or manual configuration. I have to leave automatic
configuration in place to get a valid Global IPv6 address. It would be
nice if NetworkManager allowed you to use automatic plus add additional
IP addresses to the list at the same time.

Peter
_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-dev
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Q about networking after recent networking improvements in master [ In reply to ]
On Sat, Apr 15, 2017 at 3:42 PM, Peter Bennett <pgbennett@comcast.net> wrote:

> How do you add the Unique local address to your systems?

I would think that in most cases you should
likely be using router advertisements and
SLAAC(*), in which case the IPv6 "auto-config"
should just work and provide both ULA and
GUA addresses to your systems.

(*) There are some who prefer DHCPv6.
_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-dev
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Q about networking after recent networking improvements in master [ In reply to ]
On 04/15/2017 12:14 PM, Gary Buhrmaster wrote:
> On Sat, Apr 15, 2017 at 3:42 PM, Peter Bennett <pgbennett@comcast.net> wrote:
>
>> How do you add the Unique local address to your systems?
> I would think that in most cases you should
> likely be using router advertisements and
> SLAAC(*), in which case the IPv6 "auto-config"
> should just work and provide both ULA and
> GUA addresses to your systems.
>
> (*) There are some who prefer DHCPv6.
> _______________________________________________
>
With SLAAC I am getting GUA addresses and link-local but no ULA
addresses. With DHCPv6 the router fails to work properly, it randomly
hangs and stops supplying either IPV4 or IPV6 addresses. (and also does
not supply ULAs).

If the router is to supply _ULA_ addresses, I assume you would have to
tell it the prefix. There is no place in my router config to do that.

Do most routers have that ability? I would like to control my ULA
addresses, or at least be sure they will not change if the router is
recycled or for any other reason.

Peter
Re: Q about networking after recent networking improvements in master [ In reply to ]
Hey Peter,

On 04/15/2017 10:42 AM, Peter Bennett wrote:
...
> How do you add the Unique local address to your systems?

I used http://www.sixxs.net/tools/grh/ula/ to get a proper ULA.
But I lied about my actual MAC. I haven't researched it much,
these:

net.ipv6.conf.all.use_tempaddr = 2
net.ipv6.conf.default.use_tempaddr = 2

exist and when set to 2 (in 15.10), a ULA is generated automatically.
Likely where distros may set things differently. I haven't retried
it with your new work, but I'm not clear if using temporary addresses
would work for the backend if it has remote FEs.

Originally, I added it with the Network Manager GUI. When systemd
(and networkd) arrived, I disabled NetworkManager and added them
manually like this:

/etc/systemd/network$ cat eth0.network
[Match]
Name=eth0

[Network]
Description=Primary NIC
Address=192.168.1.200/24
Address=fdf9:a66:2cd8:1::200/64
DHCP=no
DNS=8.8.8.8
DNS=8.8.4.4

[Route]
Gateway=192.168.1.128
Metric=11

[Route]
Gateway=fe80::b8b8:b8ff:fe6e:6e6e
Metric=12

> I am thinking about updating the wiki IPV6 article and wondering about the best way of doing it.

In here: https://www.mythtv.org/wiki/Enable_IPv6#Which_IPv6_address_should_be_used.3F I did
the complete cop-out of: "If the desired address doesn't exist, use the configuration tool
provided with the host's distribution to add it." I was trying to write the page mostly from
a MythTV perspective and tried to be light on IPv6 details. Had 2nd thought of even adding
the "Tools and sample output" section.

> I have it working by creating a script and linking it to /etc/network/if-up.d/010addipaddress. In that script I run a command ip -6 address add
> $ipadd dev "$ifacename" with appropriate parameters. I created a table of ULAs and MAC addresses. This works well, I get the automatic Global
> IPv6 address from Comcast plus the ULA that I set up.

Unfortunately, I mostly run *buntu boxes and can't comment on
the others. Here's some notes from what I tried:

Sample IP configurations. Pick one.
-----------------------------------

/etc/network/interfaces: [on *buntu]
auto eth0
iface eth0 inet static
address 192.168.1.222
netmask 255.255.255.0
gateway 192.168.1.128
iface eth0 inet6 static
address fdf9:a66:2cd8:1::222
netmask 64
gateway fe80::b8b8:b8ff:fe6e:fc90

/etc/NetworkManager/system-connections/Wired (or any name): [*buntu]
[ipv4]
address1=192.168.1.227/24,192.168.1.128
dns=192.168.1.128;
dns-search=
method=manual
[ipv6]
addr-gen-mode=stable-privacy
address1=fdf9:a66:2cd8:1::227/64,fe80::7262:b8ff:fe6e:fc90
dns=fe80::b8b8:b8ff:fe6e:fc90;
dns-search=
ip6-privacy=0
method=manual

/etc/sysconfig/network-scripts/ifcfg-enp0s10 [Fedora]
HWADDR=00:01:2E:24:58:0D
TYPE=Ethernet
BOOTPROTO=none
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
NAME=enp0s10
UUID=fce81113-3fef-39aa-b0f7-57f40cfc08de
ONBOOT=yes
AUTOCONNECT_PRIORITY=-999
IPADDR=192.168.1.226
PREFIX=24
GATEWAY=192.168.1.128
DNS1=192.168.1.128
IPV6INIT=yes
IPV6ADDR=fdf9:a66:2cd8:1::226/64
IPV6_FAILURE_FATAL=no
IPV6_DEFAULTGW=fe80::b8b8:b8ff:fe6e:fc90%enp0s10

I'm not sure the Wiki is going to care for all cases. Maybe those that
choose other than NetworkManager would be on there own.

> I could not find a more user-friendly way to do it with NetworkManager. It allows automatic or manual configuration. I have to leave automatic
> configuration in place to get a valid Global IPv6 address. It would be nice if NetworkManager allowed you to use automatic plus add additional
> IP addresses to the list at the same time.

Same here, I've been doing things with an editor mostly.

--
Bill
_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-dev
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Q about networking after recent networking improvements in master [ In reply to ]
On 04/15/2017 03:17 PM, Peter Bennett wrote:
>>
> With SLAAC I am getting GUA addresses and link-local but no ULA addresses. With DHCPv6 the router fails to work properly, it randomly hangs and
> stops supplying either IPV4 or IPV6 addresses. (and also does not supply ULAs).
>
> If the router is to supply _ULA_ addresses, I assume you would have to tell it the prefix. There is no place in my router config to do that.
>
> Do most routers have that ability? I would like to control my ULA addresses, or at least be sure they will not change if the router is
> recycled or for any other reason.

I did setup bind on one box. Mostly to test IPv6 on a tablet.

Don't use it for my entire LAN. I think it's setup would be
more than we'd expect of a user - especially with all the
work that's been done to simplify things.


--
Bill
_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-dev
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Q about networking after recent networking improvements in master [ In reply to ]
On Sat, Apr 15, 2017 at 8:17 PM, Peter Bennett <pgbennett@comcast.net> wrote:
....
> Do most routers have that ability? I would like to control my ULA addresses,
> or at least be sure they will not change if the router is recycled or for
> any other reason.

I can't say much about devices which like to
claim to be a router in the consumer space,
but I believe most real routers do. I can offer
both my dhcpv6-pd provided GUA addresses
and my ULA addresses to my systems via
router advertisements from my router (an
edgerouter)

For those that have chosen solutions that
are not compliant with the RFC 7084 (basic
router requirements for IPv6) SHOULD
regarding IPv6 ULA generation, I suppose one
could consider running a few radvd instances
on a few (minimal) systems to advertise the
local ULA prefix (a few instances to provide a
bit of redundancy) if your consumer gateway
does not give you the ability to configure your
RAs.

In any case ULAs are certainly not a common
configuration in the current consumer space,
even though ULA was expected to exist in
Homenet (ietf ipv6 home networking principals)
implementations, so should that effort move
forward, I would expect more implementations
to become compliant.
_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-dev
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Q about networking after recent networking improvements in master [ In reply to ]
On Sat, Apr 15, 2017 at 9:24 PM, Bill Meek <keemllib@gmail.com> wrote:

> I used http://www.sixxs.net/tools/grh/ula/ to get a proper ULA.

ULAs were never gauranteed to be unique,
or registered, but SIXXS encouraged
users to use their site to generate a (more
likely) unique ULA and to list them to
reduce the probability of a collision even
further.

It should be noted that SIXXS is closing
their doors later this year, and has stated
that their web site with move to read-only
archive mode. At the time of their notice,
it was unclear if their ULA listing service
will continue after that point, but given how
easy it is to get IPv6 GUA from most RIRs
these days, it likely has limited value.
_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-dev
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Q about networking after recent networking improvements in master [ In reply to ]
On 04/15/2017 04:24 PM, Bill Meek wrote:
>
> net.ipv6.conf.all.use_tempaddr = 2
> net.ipv6.conf.default.use_tempaddr = 2

Replying to myself (or correcting)

# Acceptable values:
# 0 - don?t use privacy extensions.
# 1 - generate privacy addresses
# 2 - prefer privacy addresses and use them over the normal addresses.

On my test box where I changed 2 to 0, I switched it back to 2.

The problem had nothing to do with MythTV, as expected. Rather,
when I powered on a remote host (FE), routing wasn't created
for the ULA I installed *manually* (on the BE), it was for the one created
by the kernel of the backend under test.

I could add the route for the manually created ULA, but that's
extra work users shouldn't need to worry about.

When I look at my 14.04 production BE, it has tempaddr = 2
but works fine. It's on the 15.10 box where I see the issue.

For 14.04 (kernel 3.13) no ULAs are created automatically.
For 15.10 (kernel 4.8.0) they are. Can't remember 15.04
and 17.04 (kernel 4.10) they aren't. But I just loaded
that yesterday afternoon on my laptop.

The ideal case seems to let the kernel develop/announce
the ULAs, assuming folks choose to mimic IPv4 Private
Network addresses.

I haven't figured out why 3.13 and 4.10 aren't creating
ULAs. Been looking at sysctl output, but no success.

--
Bill
_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-dev
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Q about networking after recent networking improvements in master [ In reply to ]
On Sun, Apr 16, 2017 at 3:25 PM, Bill Meek <keemllib@gmail.com> wrote:

> The ideal case seems to let the kernel develop/announce
> the ULAs, assuming folks choose to mimic IPv4 Private
> Network addresses.

I think you may be confusing link local addresses
(which the kernel does do for both IPv4 and IPv6),
and locally administered addresses, which is
typically provided by your gateway/router (often
RFC1918 for IPv4, and can be ULA for IPv6)
since it needs to be coordinated across all your
residential networks.
_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-dev
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Q about networking after recent networking improvements in master [ In reply to ]
On 04/16/2017 11:53 AM, Gary Buhrmaster wrote:
> On Sun, Apr 16, 2017 at 3:25 PM, Bill Meek <keemllib@gmail.com> wrote:
>
>> The ideal case seems to let the kernel develop/announce
>> the ULAs, assuming folks choose to mimic IPv4 Private
>> Network addresses.
>
> I think you may be confusing link local addresses
> (which the kernel does do for both IPv4 and IPv6),
> and locally administered addresses, which is
> typically provided by your gateway/router (often
> RFC1918 for IPv4, and can be ULA for IPv6)
> since it needs to be coordinated across all your
> residential networks.

Looks like ULAs to me:

$ ifconfig
enp4s0 Link encap:Ethernet HWaddr 1c:6f:65:4a:85:15
inet addr:192.168.1.221 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fd14:4bf7:d5bf:0:1e6f:65ff:fe4a:8515/64 Scope:Global
inet6 addr: fd14:4bf7:d5bf:0:4c4c:afde:fb87:7981/64 Scope:Global
inet6 addr: fdf9:a66:2cd8:1::221/64 Scope:Global
inet6 addr: fd14:4bf7:d5bf:0:b52e:f578:ce6b:8ceb/64 Scope:Global
inet6 addr: fe80::1e6f:65ff:fe4a:8515/64 Scope:Link
inet6 addr: fd14:4bf7:d5bf:0:d3bd:3a12:6018:90cb/64 Scope:Global


fd14... = magic to me, fdf9... = the ULA I made up and configured. Yesterday,
the fd14:4bf7:d5bf:0/64 prefix was fdec:somethingElseIdon'tRemember. Perhaps
they're some kind of stale temporary address. Just don't know. But if it's
not a reliable kernel feature, it's of no value to Peter's question.

[.my ISP only provides GUAs to their business customers and based on my last
conversation with them, they have no plans to start]

--
Bill
_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-dev
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Q about networking after recent networking improvements in master [ In reply to ]
On Sun, Apr 16, 2017 at 5:16 PM, Bill Meek <keemllib@gmail.com> wrote:

> Looks like ULAs to me:
....
> inet6 addr: fe80::1e6f:65ff:fe4a:8515/64 Scope:Link

That is a link local address. And your kernel auto-generated it.
For IPv4, the link local address (169.254.x.x, which is also
auto-generated) is replaced when you get a "better" address,
but IPv6 very specifically requires support for multiple addresses
so the link local stays "forever" (and may/will be used for certain
communications).

For those without multiple networks, or the need to get
outside the local lan, link local addresses have always been
viable.
_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-dev
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Q about networking after recent networking improvements in master [ In reply to ]
On 04/16/2017 12:26 PM, Gary Buhrmaster wrote:
> On Sun, Apr 16, 2017 at 5:16 PM, Bill Meek <keemllib@gmail.com> wrote:
>
>> Looks like ULAs to me:
> ....
>> inet6 addr: fe80::1e6f:65ff:fe4a:8515/64 Scope:Link
> That is a link local address...

I know, it's the fd14:4bf7:d5bf:0/64 ULAs (the ones that I didn't
create manually) that I'm was addressing. Just kept the LL for
completeness. Plus the EUI.64 part is visible in one ULA.

Since I can't figure out why the extra ULAs are there and since tempaddr
prefixes change (makes sense) there's not much hope for its use as a
MythTV solution.

--
Bill
_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-dev
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Q about networking after recent networking improvements in master [ In reply to ]
On 04/16/2017 01:16 PM, Bill Meek wrote:
> $ ifconfig
> enp4s0 Link encap:Ethernet HWaddr 1c:6f:65:4a:85:15
> inet addr:192.168.1.221 Bcast:192.168.1.255 Mask:255.255.255.0
> inet6 addr: fd14:4bf7:d5bf:0:1e6f:65ff:fe4a:8515/64
> Scope:Global
> inet6 addr: fd14:4bf7:d5bf:0:4c4c:afde:fb87:7981/64
> Scope:Global
> inet6 addr: fdf9:a66:2cd8:1::221/64 Scope:Global
> inet6 addr: fd14:4bf7:d5bf:0:b52e:f578:ce6b:8ceb/64
> Scope:Global
> inet6 addr: fe80::1e6f:65ff:fe4a:8515/64 Scope:Link
> inet6 addr: fd14:4bf7:d5bf:0:d3bd:3a12:6018:90cb/64
> Scope:Global
>
>
> fd14... = magic to me, fdf9... = the ULA I made up and configured.
> Yesterday,
> the fd14:4bf7:d5bf:0/64 prefix was fdec:somethingElseIdon'tRemember.
> Perhaps
> they're some kind of stale temporary address. Just don't know. But if
> it's
> not a reliable kernel feature, it's of no value to Peter's question.
>
> [.my ISP only provides GUAs to their business customers and based on my
> last
> conversation with them, they have no plans to start]

It seems like you have an over-enthusiastic router, which created 4 ULA
addresses for 1 server.
Mine, on the other hand, generates none, but I do get a GUA from Comcast:

enp0s25 Link encap:Ethernet HWaddr bc:5f:f4:f8:a8:a2
inet addr:192.168.0.188 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: 2601:183:101:18dc:5e04:34b5:7af4:6714/64 Scope:Global
inet6 addr: fe80::1c98:f936:7f9e:3afb/64 Scope:Link
inet6 addr: fd3d:63f5:6a89:1::10/64 Scope:Global

The fd3d is the one I create and assign in the script I mentioned before.

If your ISP does not give you Global addresses then you cannot access
IPV6 web sites. They seem to think only businesses need that??? That's
crazy.

Comcast seems to be on the ball in that respect. They give an IPv6 range
to users, and their websites and their email servers all are IPv6
accessible.

Peter
_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-dev
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Q about networking after recent networking improvements in master [ In reply to ]
On Sun, 16 Apr 2017 12:16:29 -0500, you wrote:

>[.my ISP only provides GUAs to their business customers and based on my last
> conversation with them, they have no plans to start]

If your ISP is not assigning any GUAs to you, then you can not use
IPv6 to connect to the outside world. Which means that enabling IPv6
ULAs may well cause problems as your devices will prefer to connect
via the IPv6 addresses and will take a long time to try using an IPv4
address when that fails. If there is no real IPv6 connectivity with
the outside world, but a device can see an IPv6 address it thinks it
can use for that, then even if there are no IPv6 DNS settings in
place, it will use IPv4 DNS to get IPv6 addresses and try to connect
to them.

Not providing GUAs means not providing IPv6 support at all, so there
must be something wrong with your understanding of what your ISP is
saying. Most likely, they are only providing dynamic GUA address
blocks, that will potentially change every time your router reconnects
to them. That is not how IPv6 is supposed to work, but does seem to
be how stupid ISPs are doing it. My ISP does that, but for those
people who pay for a static IPv4 address, they also provide static
IPv6 addresses, and as I have always had a static IPv4 I have never
had to cope with dynamic IPv6 assignments. The way to cope with
dynamic IPv6 addresses seems to be what you are doing - use ULA
addresses for all the devices on your network, and allow automatic
assignment of dynamic GUA addresses by the router when it receives an
assignment of its GUA address block.

When the dynamic GUA assignment changes, if any of your devices are
using the GUA addresses to talk to each other, those connections will
be disrupted. I am not sure if IPv6 will prefer to use ULA addresses
if they are present and a GUA address is also present - I hope it
works like that. Within one subnet, IPv6 devices seem to prefer use
the link-local addresses to talk to each other, even if they have GUA
addresses assigned. So if you only have one subnet, then IPv6 will
likely keep working right when the GUA changes.

Since you are not seeing any GUA addresses on your devices, there must
be some misconfiguration somewhere that needs fixing, most likely in
your Internet router.
_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-dev
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Q about networking after recent networking improvements in master [ In reply to ]
On Mon, Apr 17, 2017 at 12:21 AM, Stephen Worthington
<stephen_agent@jsw.gen.nz> wrote:
...
> If your ISP is not assigning any GUAs to you, then you can not use
> IPv6 to connect to the outside world. Which means that enabling IPv6
> ULAs may well cause problems as your devices will prefer to connect
> via the IPv6 addresses and will take a long time to try using an IPv4
> address when that fails.

Only if your clients are not compliant with RFC 6555 ("Happy eyeballs").
That there are borked applications is without doubt, but that means
the application should be terminated, not your IPv6 addresses.
_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-dev
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org