NFPS / Private Fixing iVue Guide to work with IPTV Stalker ("failed authorization")

IPTV Private Server (NFPS)
Status
Not open for further replies.
#81
Didn't read through entire thread, so stop me if someone has done this... I'm creating a vbscript to automate the process of assigning a users MAC to the addons.ini file in iVue. It will have a popup box for the user to enter the raw encoded mac address string from their addons.ini file (following the original tutorial method for copying it from this thread) and a pop up to enter YOUR mac address. It will do the rest: convert the raw string, tack on the 6 digits from your mac address, re-encode, and replace all instances with it in your addons.ini file. About half way done..., but I have a question...

Should this tack on the first 6 or last 6 from a users MAC?
So if my raw decoded string looks like this: mac": "00:1A:79:BB:BB:BB", "
and cleaned up string looks like this: 00:1A:79:BB:BB:BB
...and MY mac address looks like this: AB:CD:EF:00:01:02
Should the final MAC look like this? 00:1A:79:00:01:02
or this? 00:1A:79:AB:CD:EF

Also, I've read about some users using 00:1A:78 (not always 79). Not clear if this is determined in original iVue addons.ini file or not. If it's something the user needs to specify, I could just make another pop box for the user to enter 78 or 79. I welcome any other ideas...

Also, would be a windows only tool... :(

thx
 
Last edited:
#82
Drivium said:
Didn't read through entire thread, so stop me if someone has done this... I'm creating a vbscript to automate the process of assigning a users MAC to the addons.ini file in iVue. It will have a popup box for the user to enter the raw encoded mac address string from their addons.ini file (following the original tutorial method for copying it from this thread) and a pop up to enter YOUR mac address. It will do the rest: convert the raw string, tack on the 6 digits from your mac address, re-encode, and replace all instances with it in your addons.ini file. About half way done..., but I have a question...

Should this tack on the first 6 or last 6 from a users MAC?
So if my raw decoded string looks like this: mac": "00:1A:79:BB:BB:BB", "
and cleaned up string looks like this: 00:1A:79:BB:BB:BB
...and MY mac address looks like this: AB:CD:EF:00:01:02
Should the final MAC look like this? 00:1A:79:00:01:02
or this? 00:1A:79:AB:CD:EF

Also, I've read about some users using 00:1A:78 (not always 79). Not clear if this is determined in original iVue addons.ini file or not. If it's something the user needs to specify, I could just make another pop box for the user to enter 78 or 79. I welcome any other ideas...

Also, would be a windows only tool... :(

thx
Click to expand...


The on-going requirement for non-stb users will be to use the "00:1A:78" prefix. However, some are still reporting that the 79 is still working for them. If I were coding this thing, I'd just have the user enter the entire MAC that they have linked to their donation. If you'd like, you probably could warn the user that the mac entered is not valid with the server. I'd also have the ability to just enter the 12 numbers, without having to worry about the colons.
 
#84
Drivium said:
Yea, my plan was to have them enter their whole mac and have the script cut half of it to add it to the prefix, but which half of the users MAC is needed? 1st half or 2nd half?
Click to expand...

I think that's where you may confuse people. The first six digits designate the maker of the device/nic, the last six are supposed to be unique to that maker. For the purposes of the iptv server and the Stalker middleware, the last six doesn't really matter to it as long as it matches to a linked MAC to a valid donation. That linked MAC has to be able to work with the server with IPTV Stalker. If they can't make IPTV Stalker work as a standalone add-on, they either don't have a valid linked mac, or they aren't actually connecting with the server, probably due to a wrong url. So if you are coding this, just let the user enter his MAC that has already been lined to a donation. You don't have to pick digits, but if you want, just pick the last six that the user entered and make sure the first six are "00:1A:78".
 
#85
dara said:
You don't have to pick digits, but if you want, just pick the last six that the user entered and make sure the first six are "00:1A:78".
Click to expand...

The first 6 (00:1A:78) are what I was referring to as the prefix. I get that this piece is mandatory and unchanging. So, I'll have it grab the last 6 of the users MAC. So, if the users MAC is 11:22:33:44:55:66, the result will be 00:1A:78:44:55:66.

Also - so far, in iVue on both my FireTV & PC, the default MAC in the addons.ini file is 00:1A:79:BB:BB:BB. Is this the case for everyone? If so, the encrypted string would be the same within the .ini file also. I could save the user the step of having to copy that string into the popup if it's always the same.
 
Last edited:
#86
Drivium said:
The first 6 (00:1A:78) are what I was referring to as the prefix. I get that this piece is mandatory and unchanging. So, I'll have it grab the last 6 of the users MAC. So, if the users MAC is 11:22:33:44:55:66, the result will be 00:1A:78:44:55:66. Thanks.
Click to expand...

That's fine, but for the purpose of the service, their linked MAC should always start with 00:1A:78, even if their real actual MAC starts with 11:22:33 ... the server doesn't care. If you allow someone to enter 11:22:33:44:55:66 into your script, they will link that same number into their donation or at least attempt it, and then complain that iVue doesn't work after they entered their MAC. Yes, users will do that... :)
 
#87
I think we're miscommunicating. I understand that the 00:1A:78 should ALWAYS go at the beginning of the MAC. I've already coded for that. No matter which MAC the user enters, the front half will be stripped away and replaced with 00:1A:78. I'll have a msgbox popup that allows the user to view the MAC they're about to write to the ini so they can confirm it's correct. They can proceed or abort.
 
#88
Hi all I'm new to all of this, I have installed Ivie guides etc and I have IPTV stalker add on but when I click to open the list of all channels I get authorisation failed, I'm on kodi 14.2 on an android box? Can you help me please? Thanks, Shane.
 
#89
Ok, need someone to test!

Code: 
Here's a pastebin of my code: http://pastebin.com/xqdAPT8g

Link to app: https://drive.google.com/file/d/0B7UqN53jp_4camkwOUZvWUFBMkE/view?usp=sharing
How to use:

Make sure a COPY of your addons.ini file and iVue_MAC_Swap.vbs are in the same folder:
View attachment 899

Execute the VBS file.

Follow the prompts:
View attachment 900
View attachment 901
View attachment 902
View attachment 903

Won't be able to test until I get home, but it writes to the ini successfully. My only concern is that basic text editing may somehow corrupt the file as opposed to modifying it within Notepad++. Guess we'll see... But, that's why we use COPIES right? lol
 
Last edited by a moderator:
#91
Improved script to automatically find the encoded MAC within their addons.ini file. User no longer needs to manually copy and paste the encoded mac string from the ini file. The only user interaction now is to provide their MAC address...wait a few seconds....and confirm the write.

Code: 
Pastebin:    http://pastebin.com/XdfYP6dF

Link to file: https://drive.google.com/file/d/0B7UqN53jp_4cSmNrSEdJTm5GakU/view?usp=sharing
 
Last edited by a moderator:
#92
Works great Drivium!

I have to code your links to conform to the site rules.

I'll copy your posts over to the Kodi EPG section so it can be found easier.
 
Last edited:
#94
Maybe spoke too soon... getting authorization errors and couldn't get into PVR Stalker or STB Emu.

Yep, and can't log into my other apps as well with my mac. I changed it to another so I can log in. It looks like the ini maybe sending the serial number so it may screw up other addons.
 
Last edited:
#96
The v2 script makes no mods to any serials. It strictly mods the MACs that follow the word "mac" and the only "mac" I have in mine is related to iptvstalker. Was the final MAC the script displayed not the right MAC? I'm trying to understand what might be going on. Are you able to send me a copy of your addon.ini file so I can see how it plays with the script? If possible, let me know what the script should avoid modifying in the ini file. Not sure why your tecbox addons.ini would impact other addons...
 
Last edited:
#97
The MAC was correct, and it did work initially, but after exiting out of Kodi, the other addons and emulators stopped working. If a "serial number" is sent by IPTV Stalker, it will screw up access for other addons as it is stored on the middleware. All the iVue is doing is passing what ever is in that line, and there is some junk that is sent across with that line for the serial number. I believe can be prevented with a minor hard code change in IPTV Stalker.

I do think the script will work for most that only use the iVue though.
 
#98
Ok. I think I'm seeing what you are describing. The live tv channels are no longer working. If I access iptv stalker manually (via video addons), I can get in just fine and iVue also works. TV/EPG seem to be the only thing affected for me. So, anything I can do on my end? Maybe clear the references to "serial" in the ini? Or are you saying that there can't be a universal solution to this issue? I'm asking sincerely, because I'm VERY new to KODI and it's addons and my OCD will flare up if I keep chasing this thing with no possible solution...lol.

Are you a programmer? Getting the impression you are.
 
Last edited:
#99
Drivium said:
Ok. I think I'm seeing what you are describing. The live tv channels are no longer working. If I access iptv stalker manually (via video addons), I can get in just fine and iVue also works. TV/EPG seem to be the only thing affected for me. So, anything I can do on my end? Maybe clear the references to "serial" in the ini?

Are you a programmer?
Click to expand...

That's what I was thinking... if the serial references are removed from the ini, or if it sends it over as null, the IPTV Stalker should still work, and not affect PVR Stalker or the STB Emu.

I'm not a programmer, or at least current, but I can read code. The call to the server is made in 'addon.py' in the plugin.video.stalker in the playLevel() def. I'll see if it still will work by removing the portal ['serial'] argument.
 
#100
dara said:
That's what I was thinking... if the serial references are removed from the ini, or if it sends it over as null, the IPTV Stalker should still work, and not affect PVR Stalker or the STB Emu. I'll see if it still will work by removing the portal ['serial'] argument
Click to expand...

Cool. Let me know. If that does the trick, we're lookin' at v3.

dara said:
I'm not a programmer, or at least current, but I can read code.
Click to expand...

Gotcha. I'm not really either, more of a hacker. I just like to automate stuff. Push a button and watch the pretty lights. When you said "middleware", I was instantly impressed...lol. No idea what that is. I'm not current either. Most familiar with vbs, which is about 9999 years old, but still supported in windows by default! lol I've written some python scripts at work and have been able to do what I needed to, but I wouldn't say I'm fluent.

I still don't get how an iVue ini can affect other addons...
 
Last edited:
Status
Not open for further replies.
Top Bottom
Back
Menu