Wired MVP Client not working with Sage but does with MediaMVP version 3.2

[hankjones]

Hello, I'm hoping someone can help out, or has seen this before...

I have 2 MVP's one is from Hauppauge and another Helius MediaStream, which is just an OEM'd MVP.

Hauppauge : Model 86001 Rev D3A
MediaStream: Model 86001 Rev E1M

The Hauppauge one works fine booting up with sage. The MedaiStream boots up okay with Hauppauge's MediaMVP version 3.2, but it doesn't work Sage.

When turning on logging with sage I get the following:
Sat 9/22 8:22:40.358 Received bootp request
Sat 9/22 8:22:40.359 Op:1 hwtype:1 hwaddrlen:6hopcount:0
transaction:804247121 nSeconds:100 flags:0
MAC: 00:0f:22:00:05:2d
Sat 9/22 8:22:40.359 Couldn't match client 00:0f:22:00:05:2d
Sat 9/22 8:22:48.366 Enabled SS
Sat 9/22 8:23:05.929 Received bootp request
Sat 9/22 8:23:05.929 Op:1 hwtype:1 hwaddrlen:6hopcount:0
transaction:1943395687 nSeconds:100 flags:0
MAC: 00:0f:22:00:05:2d
Sat 9/22 8:23:05.929 Couldn't match client 00:0f:22:00:05:2d

From the sniifer traces I get the following:
the MediaStream boots, gets an ip address
does a DHCP broadcast to 255.255.255.255
sends a bunch of UDP/16868's
and then cycles over and over again.

I've tried reinstalling sage, but am still getting the errors in the logging. With the working MVP, i get MiniUI got connected from etc....

[gplasky]

Originally Posted by hankjones

Hello, I'm hoping someone can help out, or has seen this before...

I have 2 MVP's one is from Hauppauge and another Helius MediaStream, which is just an OEM'd MVP.

Are you sure it's JUST a rebadged MVP? According to their website this only works with their MediaGate Router product.


Gerry

[hankjones]

It really looks just like a rebranded device. The bootup screen looks just like a regular MVP. It seems to work the the Hauppauge software just fine. The only difference I can tell is that Hauppauge installed a Coax output with this model.

[CollinR]

Does it say Hauppauge when it boots?

If it doesn't it's probably not going to be easy to get it working. Sounds to me like someone OEMed the same/similar device with different firmware. If it boots after power loss and says something other then Hauppauge you'll know for sure. The two boxes would act identically, which they aren't.

[hankjones]

The device says Hauppauge when it boots. The Hauppauge one that works boots up with "Checking Ethernet Status". The Mediastream that that doesn't work has the exact same screen, but at the bottom it has rectangles that looks like it’s showing the boot process.

Are there multiple MVP software builds to try? It seems like the Sage software is responding to the broadcast, but errors out.

I've attached a shot of the unit. And shot of the screen during boot up, where it gets stuck.

[gplasky]

Originally Posted by hankjones

The device says Hauppauge when it boots. The Hauppauge one that works boots up with "Checking Ethernet Status". The Mediastream that that doesn't work has the exact same screen, but at the bottom it has rectangles that looks like it’s showing the boot process.

Are there multiple MVP software builds to try? It seems like the Sage software is responding to the broadcast, but errors out.

I've attached a shot of the unit. And shot of the screen during boot up, where it gets stuck.

There seems to be some inconsistencies. Sage uses the following ports for the MVP:
16867 (UDP)
16869 (UDP)
16881 (UDP)
31100 (UDP)
31099 (TCP)

The fact that your logs show it trying to connect over 16868 leads me to believe it is trying to connect with something else.
Your jpg for the model number looks like a sticker stuck over the original production sticker.
The Hauppagues with the coax connection (SPDIF) are usually a model 86019, Rev H2 with a firmware Rev of 2.04. It is the 2.04 firmware that has your same startup screen and then has the "loading application" and little flashing boxes. The older firmware Rev. 1.0 never has the boxes in your screenshot. It has the "Checking Ethernet status" then "Contacting DHCP server" if it can't load the SageTV software then it says "Locating MVP server' or something similar.

I could be wrong but to me it sounds like you have some kind of hybrid model looking for something different on the network. Just my 2 cents.

Gerry

[hankjones]

I did another sniffer trace and found that I must have looked at the wrong collumn, the Source port of the MVP is udp/16868, and the destination is udp/16867

I've attached a screenshot of a working and non working sniffer traces.

BTW! Thanks for all the feedback.

[gplasky]

Originally Posted by hankjones

I did another sniffer trace and found that I must have looked at the wrong collumn, the Source port of the MVP is udp/16868, and the destination is udp/16867

I've attached a screenshot of a working and non working sniffer traces.

BTW! Thanks for all the feedback.

So for whatever reason it looks like the Mediastream never loads the sage software so it never responds? As your test indicated it has no problem using the original Hauppague software. My guess is something is different enough to not allow the Sage software to load. Maybe file a bug report and ship them some debug logs. But if it is fixable they may not be able to without an actual device.

Gerry

[hankjones]

SOLUTION!

Thanks to Sage TV Support! This worked!

*****************************************
The server doesn't recognize it by default. He could try adding the below line to your Sage.properties file.

miniserver/clients=MVP/00:0f:22:00:05:2d/192.168.0.150

Replace the IP with the IP of your MVP.

Just make sure to close Sage and the service prior to making this change in the properties file.

Let me know if that works.

George
***************************

[gplasky]

That's great you got it working.


Gerry

[CollinR]

So how do you insure the MVP gets that IP address?

This is very intersting to me, does it seem to make the normal MVP connect faster or more reliably if you set it up this way too?

[LSHorwitz]

I too am very interested, since I have 3 older MVPs (and 3 PC clients) and have found that the newer MVP firmware will not work with last year's (version 4) Sage software. I would gladly buy more MVPs if I could find a software method to patch the properties file to allow me to use the newer MVPs with the version 4 SageTV server.

I appears this solution has worked for hankjones but I am now wondering if it also would work for the latest MVPs which are now being shipped by Sage and Hauppauge.

Any opinions would be most appreciated. Thanks,

Larry

[gplasky]

Originally Posted by CollinR

So how do you insure the MVP gets that IP address?

This is very intersting to me, does it seem to make the normal MVP connect faster or more reliably if you set it up this way too?

In some routers you can assign a specific IP address to be associated with a specific MAC address. That the device will always get the same IP address.


Gerry

[tipstir]

Correct! Media MVP will work better if you set up static IP address for the MVP MAC address. Dlink and Dynex Routers work the best there. Buffalo and the rest should support these features.

[bmclean]

I tried to change the settings using notepad on a Vista Business system and could not get it to save. Any suggestions?

[tipstir]

Originally Posted by bmclean

I tried to change the settings using notepad on a Vista Business system and could not get it to save. Any suggestions?

You need to do this in your router? Which brand and model router do you have?

Originally Posted by bmclean

I have 2 MVP's one is from Hauppauge and another Helius MediaStream, which is just an OEM'd MVP.

Oh you have the same one I have from helius (got two of these D3A and E1M) I guess you jump on the Ebay deal for $41 bucks or $43 bucks. I had bid $41 for two of them the vendor accepted my bid. Now I have 7 of these MVP.

[LSHorwitz]

tipster,

Can you tell me whether the MVPs being sold as Helios on eBay will work with the vewrsion 4 SageTv software. I am quite certain that the newer MVPs will NOT work (unless there is some, yet to be published, patch or other preference file edit to fix them). I would like to add a couple more MVPs to my version 4 Sage system but can't determine whether these Helios MVPs will work or not.

Thanks for any advice,

Larry

[tipstir]

Originally Posted by LSHorwitz

tipster,

Can you tell me whether the MVPs being sold as Helios on eBay will work with the vewrsion 4 SageTv software. I am quite certain that the newer MVPs will NOT work (unless there is some, yet to be published, patch or other preference file edit to fix them). I would like to add a couple more MVPs to my version 4 Sage system but can't determine whether these Helios MVPs will work or not.

Thanks for any advice,

Larry

I can't find anything wrong with the helius versions on ebay they work great! They sent me E1M and D3A. I already had D3A 2 and D1 and E1. You shouldn't have a problem. New MVPs are H1 and up.. You won't be getting those.

[LSHorwitz]

Thanks so very much for your reply tipster!

I am specifically concerned about compatibility with version 4 Sage, since I recently had to return a newer MVP to Sage since it will not work with version 4. Sage / Frey acknowledges that this is an incompatibility.

Therefore I wanted to order the Helios but wonder if it truly runs with the older version 4 Sage or only with the newer verrions 5 and 6?

Thanks again,

Larry

[tipstir]

Originally Posted by LSHorwitz

Thanks so very much for your reply tipster!

I am specifically concerned about compatibility with version 4 Sage, since I recently had to return a newer MVP to Sage since it will not work with version 4. Sage / Frey acknowledges that this is an incompatibility.

Therefore I wanted to order the Helios but wonder if it truly runs with the older version 4 Sage or only with the newer verrions 5 and 6?

Thanks again,

Larry

Do you remember what firmware version you had?