Jump to content


Photo

OSCAM Bind request failed (Address family not supported by protocol)

oscam ipv6

  • Please log in to reply
13 replies to this topic

#1 twinkie

  • Member
  • 6 posts

0
Neutral

Posted 2 April 2016 - 08:21

Hello, after recent update to nightly build this week i occured problem with OSCAM start.

 

It takes 6 minutes when oscam trying bind to ipv6 to give up.

 

What can I do to disable this ? I could not find any parameter to disable ipv6 in oscam.

The problem is i guess in ipv6 configuration in newest openpli linux kernel or module.

 

How is possible to disable this IPV6 to get back to IPV4 ?

 

Thank you for support

 

 
-------------------------------------------------------------------------------
>> OSCam <<  cardserver log switched at Sat Apr  2 08:52:24 2016
-------------------------------------------------------------------------------
2016/04/02 08:52:24 00000000 s >> OSCam <<  cardserver log switched, version 1.20-unstable_svn, build r11213 (mipsel-oe-linux)
2016/04/02 08:52:24 00000000 s     (main) System name    = Linux
2016/04/02 08:52:24 00000000 s     (main) Host name      = magic-box
2016/04/02 08:52:24 00000000 s     (main) Release        = 3.12.1
2016/04/02 08:52:24 00000000 s     (main) Version        = #1 Wed Jan 21 01:10:28 CET 2015
2016/04/02 08:52:24 00000000 s     (main) Machine        = mips
2016/04/02 08:52:24 00000000 s     (main) Stb model      = dm800se
2016/04/02 08:52:24 00000000 s     (main) Stb vumodel    = vuuno
2016/04/02 08:52:24 00000000 s     (main) Stb boxtype    = vuuno
2016/04/02 08:52:24 00000000 s     (main) creating pidfile /tmp/oscam.pid with pid 674
2016/04/02 08:52:24 00000000 s   (config) userdb reloaded: 4 accounts loaded, 0 expired, 0 disabled
2016/04/02 08:52:24 00000000 s     (main) signal handling initialized
2016/04/02 08:52:24 00000000 s   (config) 391 provid's loaded
2016/04/02 08:52:24 00000000 s   (config) 926 service-id's loaded in 17 ms
2016/04/02 08:52:24 00000000 s      (net) monitor: Cannot create socket (errno=124: Address family not supported by protocol)
2016/04/02 08:52:24 00000000 s      (net) monitor: Trying fallback to IPv4
2016/04/02 08:52:24 00000000 s      (net) monitor: setsockopt(IPV6_V6ONLY) failed (errno=99: Protocol not available)
2016/04/02 08:52:24 00000000 s      (net) monitor: Bind request failed (Address family not supported by protocol), waiting another 119 seconds
2016/04/02 08:52:25 00000000 s      (net) monitor: Bind request failed (Address family not supported by protocol), waiting another 118 seconds
2016/04/02 08:52:26 00000000 s      (net) monitor: Bind request failed (Address family not supported by protocol), waiting another 117 seconds
2016/04/02 08:52:31 00000000 s      (net) monitor: Bind request failed (Address family not supported by protocol), waiting another 112 seconds
2016/04/02 08:54:16 00000000 s      (net) monitor: Bind request failed (Address family not supported by protocol), waiting another 7 seconds
2016/04/02 08:54:19 00000000 s      (net) monitor: Bind request failed (Address family not supported by protocol), waiting another 4 seconds
2016/04/02 08:54:20 00000000 s      (net) monitor: Bind request failed (Address family not supported by protocol), waiting another 3 seconds
2016/04/02 08:54:21 00000000 s      (net) monitor: Bind request failed (Address family not supported by protocol), waiting another 2 seconds
2016/04/02 08:54:22 00000000 s      (net) monitor: Bind request failed (Address family not supported by protocol), waiting another 1 seconds
2016/04/02 08:54:23 00000000 s      (net) monitor: Bind request failed (Address family not supported by protocol), giving up
2016/04/02 08:54:23 00000000 s      (net) cs357x: Cannot create socket (errno=124: Address family not supported by protocol)
2016/04/02 08:54:23 00000000 s      (net) cs357x: Trying fallback to IPv4
2016/04/02 08:54:23 00000000 s      (net) cs357x: setsockopt(IPV6_V6ONLY) failed (errno=99: Protocol not available)
2016/04/02 08:54:23 00000000 s      (net) cs357x: Bind request failed (Address family not supported by protocol), waiting another 119 seconds
2016/04/02 08:54:24 00000000 s      (net) cs357x: Bind request failed (Address family not supported by protocol), waiting another 118 seconds
2016/04/02 08:54:25 00000000 s      (net) cs357x: Bind request failed (Address family not supported by protocol), waiting another 117 seconds
2016/04/02 08:54:26 00000000 s      (net) cs357x: Bind request failed (Address family not supported by protocol), waiting another 116 seconds
2016/04/02 08:54:27 00000000 s      (net) cs357x: Bind request failed (Address family not supported by protocol), waiting another 115 seconds
2016/04/02 08:54:28 00000000 s      (net) cs357x: Bind request failed (Address family not supported by protocol), waiting another 114 seconds
2016/04/02 08:56:16 00000000 s      (net) cs357x: Bind request failed (Address family not supported by protocol), waiting another 6 seconds
2016/04/02 08:56:17 00000000 s      (net) cs357x: Bind request failed (Address family not supported by protocol), waiting another 5 seconds
2016/04/02 08:56:18 00000000 s      (net) cs357x: Bind request failed (Address family not supported by protocol), waiting another 4 seconds
2016/04/02 08:56:19 00000000 s      (net) cs357x: Bind request failed (Address family not supported by protocol), waiting another 3 seconds
2016/04/02 08:56:20 00000000 s      (net) cs357x: Bind request failed (Address family not supported by protocol), waiting another 2 seconds
2016/04/02 08:56:21 00000000 s      (net) cs357x: Bind request failed (Address family not supported by protocol), waiting another 1 seconds
2016/04/02 08:56:22 00000000 s      (net) cs357x: Bind request failed (Address family not supported by protocol), giving up
2016/04/02 08:56:22 00000000 s      (net) cccam: Cannot create socket (errno=124: Address family not supported by protocol)
2016/04/02 08:56:22 00000000 s      (net) cccam: Trying fallback to IPv4
2016/04/02 08:56:22 00000000 s      (net) cccam: setsockopt(IPV6_V6ONLY) failed (errno=99: Protocol not available)
2016/04/02 08:56:22 00000000 s      (net) cccam: Bind request failed (Address family not supported by protocol), waiting another 119 seconds
2016/04/02 08:56:23 00000000 s      (net) cccam: Bind request failed (Address family not supported by protocol), waiting another 118 seconds
2016/04/02 08:56:24 00000000 s      (net) cccam: Bind request failed (Address family not supported by protocol), waiting another 117 seconds
2016/04/02 08:56:25 00000000 s      (net) cccam: Bind request failed (Address family not supported by protocol), waiting another 116 seconds
2016/04/02 08:56:26 00000000 s      (net) cccam: Bind request failed (Address family not supported by protocol), waiting another 115 seconds
2016/04/02 08:58:17 00000000 s      (net) cccam: Bind request failed (Address family not supported by protocol), waiting another 4 seconds
2016/04/02 08:58:18 00000000 s      (net) cccam: Bind request failed (Address family not supported by protocol), waiting another 3 seconds
2016/04/02 08:58:19 00000000 s      (net) cccam: Bind request failed (Address family not supported by protocol), waiting another 2 seconds
2016/04/02 08:58:20 00000000 s      (net) cccam: Bind request failed (Address family not supported by protocol), waiting another 1 seconds
2016/04/02 08:58:21 00000000 s      (net) cccam: Bind request failed (Address family not supported by protocol), giving up
2016/04/02 08:58:21 00000000 s   (reader) Synology [cs357x] creating thread for device 192.168.0.200
2016/04/02 08:58:21 00000000 s     (stat) loadbalancer: could not open /tmp/.oscam/stat for reading (errno=2 No such file or directory)
2016/04/02 08:58:21 00000000 s (emmcache) loaded 372 emmcache records from /tmp/.oscam/oscam.emmcache in 18 ms
2016/04/02 08:58:21 19AC53B8 p   (reader) Synology [cs357x] proxy 192.168.0.200:15991
2016/04/02 08:58:21 19AC53B8 p   (reader) Synology [cs357x] proxy initialized, server 192.168.0.200:15991
2016/04/02 08:58:21 00000000 s (emmcache) loaded 88 emmstat records from /tmp/.oscam/oscam.emmstat in 11 ms
2016/04/02 08:58:21 00000000 s (anticasc) anti cascading disabled
2016/04/02 08:58:21 0EB5B91F c   (client) plain dvbapi-client granted (dvbapiau, au=auto (10 reader))
2016/04/02 08:58:21 0EB5B91F c   (dvbapi) dvbapi channelcache loaded from /etc/tuxbox/config/oscam/oscam.ccache
2016/04/02 08:58:21 0EB5B91F c   (dvbapi) Detected /dev/dvb/adapter0/demux0 Api: 0, userconfig boxtype: 1 maximum amount of possible filters is 32 (oscam limit is 32)
2016/04/02 08:58:21 0EB5B91F c   (dvbapi) PMT6: Trying connect to enigma CA PMT listen socket...
2016/04/02 08:58:21 0EB5B91F c   (dvbapi) PMT6 CA PMT Server connected on fd 7!
2016/04/02 08:58:21 641C7470 h    (webif) webif: decompressed 165887 bytes back into 395176 bytes
2016/04/02 08:58:21 0EB5B91F c   (dvbapi) Demuxer 0 ecmpid 0 CAID: 0D96 ECM_PID: 1B9F PROVID: 000000 
2016/04/02 08:58:21 0EB5B91F c   (dvbapi) Demuxer 0 ecmpid 1 CAID: 0624 ECM_PID: 1B9E PROVID: 000000 
2016/04/02 08:58:21 0EB5B91F c   (dvbapi) Demuxer 0 ecmpid 2 CAID: 0500 ECM_PID: 1BA0 PROVID: 051910 
2016/04/02 08:58:21 0EB5B91F c   (dvbapi) Demuxer 0 stream Videostream (MPEG-4)(type: 1b pid: 1b95 length: 0)
2016/04/02 08:58:21 0EB5B91F c   (dvbapi) Demuxer 0 stream Audiostream (MPEG-1)(type: 03 pid: 1b96 length: 0)
 


Re: OSCAM Bind request failed (Address family not supported by protocol) #2 WanWizard

  • PLi® Core member
  • 68,309 posts

+1,719
Excellent

Posted 2 April 2016 - 11:11

What image are you using? On what box?

 

Every OpenPLi image has IPv6 enabled, I don't see any issues here (with oscam-1.20-unstable_svn-r11213).


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: OSCAM Bind request failed (Address family not supported by protocol) #3 twinkie

  • Member
  • 6 posts

0
Neutral

Posted 3 April 2016 - 20:46

I use box Magicbox MG4 satellite box
 
which info from which file I should provide ? Upgraded to latest nightly build via internal update.
 
 
Linux version 3.12.1 (oe1@build4) (gcc version 4.9.1 (GCC) ) #1 Wed Jan 21 01:10:28 CET 2015
 
Jan  1 01:00:24 magic-box syslog.info syslogd started: BusyBox v1.22.1
Jan  1 01:00:24 magic-box user.notice kernel: klogd started: BusyBox v1.22.1 (2015-02-15 15:38:27 CET)
Jan  1 01:00:24 magic-box user.info kernel: Initializing cgroup subsys cpuset
Jan  1 01:00:24 magic-box user.notice kernel: Linux version 3.12.1 (oe1@build4) (gcc version 4.9.1 (GCC) ) #1 Wed Jan 21 01:10:28 CET 2015
 


Re: OSCAM Bind request failed (Address family not supported by protocol) #4 theparasol

  • Senior Member
  • 4,157 posts

+198
Excellent

Posted 3 April 2016 - 21:08

I use box Magicbox MG4 satellite box

 
which info from which file I should provide ? Upgraded to latest nightly build via internal update.

 

No support for magicboxes here. Such shit can happen if you use a based on openpli image that is relaying on the official openpli feeds.

Try to get support on the site where you got the unofficial openpli image too.


@Camping: ZGemma H.2S, Technisat Multytenne 4-in-1 @Home: Edision Mini 4K, Wave Frontier T55, EMP Centauri EMP DiSEqC 8/1 switch, 4x Inverto Ultra Black single LNB


Re: OSCAM Bind request failed (Address family not supported by protocol) #5 malakudi

  • Senior Member
  • 1,449 posts

+69
Good

Posted 4 April 2016 - 06:25

In oscam.conf , set bindwait=5 in global section. Then you would have a 15 seconds delay (5 seconds for every port, and you have 3 used ports)

 

I would say this is a bug in oscam-net.c code, bindwait has a different purpose, it should not wait for "Address family not supported by protocol" errors. If address family is not supported, it will not magically get supported after bindwait seconds.


Edited by malakudi, 4 April 2016 - 06:27.


Re: OSCAM Bind request failed (Address family not supported by protocol) #6 mrvica

  • Senior Member
  • 1,218 posts

+80
Good

Posted 4 April 2016 - 14:54

I use box Magicbox MG4 satellite box
Upgraded to latest nightly build via internal update.

off topic, I have in the neiberhood Magicbox MG4, I am just intereseting which software did you flash, this one:
http://magicbox-tv.c...IMEDIA_MG4_bei/
or from somwhere else, I was told that MG4 = Cloud_Ibox3_SE, is that true?

Re: OSCAM Bind request failed (Address family not supported by protocol) #7 twinkie

  • Member
  • 6 posts

0
Neutral

Posted 4 April 2016 - 19:32

Hello I tried bindwait = 5 but same result with 2 minutes wait in delay as in log below.

 

I flashed image from www.magicbox-tv.com: magibox-OpenPli4.0-beta-20150825.rar when I received this box from china, but after that I performed regular update from receiver menu to latest nightly build with no problems, but after update last week this started to happen. I know I could get back to this image or even the newer one which is magibox-openpli4-20151119.rar but as this could happen on my box it can cause issue on others too as this issue came with regular update. So I think other people could experience this problem too. Also I got lot of configuration done on my box so get back to original image will result in many hours of configuration and for now I could live with it is just anoying to wait 6 minutes for oscam to start responding.

 

 

2016/04/04 20:21:23 00000000 s      (net) monitor: Bind request failed (Address family not supported by protocol), waiting another 119 seconds
2016/04/04 20:21:24 00000000 s      (net) monitor: Bind request failed (Address family not supported by protocol), waiting another 118 seconds
2016/04/04 20:21:25 00000000 s      (net) monitor: Bind request failed (Address family not supported by protocol), waiting another 117 seconds
2016/04/04 20:21:26 00000000 s      (net) monitor: Bind request failed (Address family not supported by protocol), waiting another 116 seconds
2016/04/04 20:21:27 00000000 s      (net) monitor: Bind request failed (Address family not supported by protocol), waiting another 115 seconds
2016/04/04 20:21:28 00000000 s      (net) monitor: Bind request failed (Address family not supported by protocol), waiting another 114 seconds
2016/04/04 20:21:29 00000000 s      (net) monitor: Bind request failed (Address family not supported by protocol), waiting another 113 seconds
2016/04/04 20:21:30 00000000 s      (net) monitor: Bind request failed (Address family not supported by protocol), waiting another 112 seconds
2016/04/04 20:21:31 00000000 s      (net) monitor: Bind request failed (Address family not supported by protocol), waiting another 111 seconds
2016/04/04 20:21:32 00000000 s      (net) monitor: Bind request failed (Address family not supported by protocol), waiting another 110 seconds
2016/04/04 20:21:33 00000000 s      (net) monitor: Bind request failed (Address family not supported by protocol), waiting another 109 seconds
2016/04/04 20:21:34 00000000 s      (net) monitor: Bind request failed (Address family not supported by protocol), waiting another 108 seconds
2016/04/04 20:21:35 00000000 s      (net) monitor: Bind request failed (Address family not supported by protocol), waiting another 107 seconds
2016/04/04 20:21:36 00000000 s      (net) monitor: Bind request failed (Address family not supported by protocol), waiting another 106 seconds
2016/04/04 20:21:37 00000000 s      (net) monitor: Bind request failed (Address family not supported by protocol), waiting another 105 seconds
2016/04/04 20:21:38 00000000 s      (net) monitor: Bind request failed (Address family not supported by protocol), waiting another 104 seconds
2016/04/04 20:21:39 00000000 s      (net) monitor: Bind request failed (Address family not supported by protocol), waiting another 103 seconds
2016/04/04 20:21:40 00000000 s      (net) monitor: Bind request failed (Address family not supported by protocol), waiting another 102 seconds


Re: OSCAM Bind request failed (Address family not supported by protocol) #8 malakudi

  • Senior Member
  • 1,449 posts

+69
Good

Posted 4 April 2016 - 19:35

Show oscam.conf , it seems bindwait=5 didn't apply.



Re: OSCAM Bind request failed (Address family not supported by protocol) #9 twinkie

  • Member
  • 6 posts

0
Neutral

Posted 8 April 2016 - 18:25

Yes!! the parameter bindwait=5 resolved my issue, thans a lot for your advice. I had bindwait twice in [global] section of oscam.conf first i add bindwait=5 but later in section was still bindwait=120 and that applied.



Re: OSCAM Bind request failed (Address family not supported by protocol) #10 Dimmie

  • Senior Member
  • 2,338 posts

+33
Good

Posted 3 June 2016 - 17:16

So people that use pirated copies of OPenPLI will get support here after all ?

 

mmm



Re: OSCAM Bind request failed (Address family not supported by protocol) #11 goldeneye

  • Senior Member
  • 1,030 posts

+14
Neutral

Posted 3 June 2016 - 17:25

Sometimes people answer before actually reading the content... The TS gets lucky....

Re: OSCAM Bind request failed (Address family not supported by protocol) #12 theparasol

  • Senior Member
  • 4,157 posts

+198
Excellent

Posted 3 June 2016 - 17:42

I did read it in whole, but point is: this is not streamboard the support home for oscam and the image in use isn't openpli.

Therefor my blunt answer instead of the simple real solution.

Its certainly kind that Malakudi did present the solution but next time this user will go to here again since he was served with a solution before and probably some friends of him too ;)

And others will read this topic too while googleing for a solution and ask their openpli unrelated questions too since this user was kindly helped.

 

So, it might look like a nice guy action but its plain stupid if you ask me ;)


@Camping: ZGemma H.2S, Technisat Multytenne 4-in-1 @Home: Edision Mini 4K, Wave Frontier T55, EMP Centauri EMP DiSEqC 8/1 switch, 4x Inverto Ultra Black single LNB


Re: OSCAM Bind request failed (Address family not supported by protocol) #13 malakudi

  • Senior Member
  • 1,449 posts

+69
Good

Posted 3 June 2016 - 17:54

@theparasol: It was a question about oscam, and I answered about oscam. Since you have done commits in oscam, much more than I have done, I would expect from you to give a technical answer like I did. It was completely unrelated that the box had a not genuine openpli image. It was an oscam problem, any box that uses oscam would have the same issue if ipv6 was disabled.

 

Stupid was to give a reason about unsupported box on a techincal issue about oscam handling ipv6. An oscam developer would respond by creating a fix in oscam source code.

 

Unfortunately, the quality of oscam code has dropped considerably in the last years.


Edited by malakudi, 3 June 2016 - 17:55.


Re: OSCAM Bind request failed (Address family not supported by protocol) #14 malakudi

  • Senior Member
  • 1,449 posts

+69
Good

Posted 3 June 2016 - 17:58

So people that use pirated copies of OPenPLI will get support here after all ?

 

mmm

 

No, they will not. The question was unrelated to openpli, same problem would happen to openpli if someone would disable ipv6 - and I know people do that for various reasons. So it was a technical reply about an oscam issue, not openpli issue.





Also tagged with one or more of these keywords: oscam, ipv6

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users