MVP cannot get IP with 4.1.6

[ke6guj]

I'm on a 192.168.0.x subnet also, no problems here.

I have my router set to give out static IP addresses via MAC address.

[MrApollinax]

that is what I'm doing in my setup as well.

[Narflex]

Originally Posted by MurrayGill

Excellent thread! Was tearing my hair out over this problem, and had resorted to going back to 4.1.4.

Just one note however...this also seems to be a problem if your DHCP server is serving out 192.168.0.X addresses.

At least, when I upgraded (again) last night, my MVP would get stuck on "Contacting Bootserver" while my router was serving out 192.168.0.X addresses but resolved immediately when I switched it to 192.168.1.X addresses.

Didn't have a chance to play much with 4.1.6, but the remote does seem much more responsive. Color me happy!

I've seen this before when the router runs out of addresses for DHCP. (it really shouldn't) Changing the address range fixed it when I had that issue (which is basically what you did). So it might have been the same sort of thing...

[walts81]

Can anyone help with this? I turned on debugging and found this in the log. But I don't know what it means or how to fix it.

Wed 2/1 17:29:52.595 Added MVP client to our bootp list 00:0d:fe:00:13:40
Wed 2/1 17:29:52.595 servername 192.168.1.3
Wed 2/1 17:29:52.595 Sending bootp reply
Wed 2/1 17:29:52.735 Received tftp packet
Wed 2/1 17:29:52.737 Reading mvp.bin in mode octet
Wed 2/1 17:29:52.737 Opening file
Wed 2/1 17:29:53.431 PM currState=0 wakeupTime=Wed 2/1/2006 18:56:00.000
Wed 2/1 17:29:55.066 TFTP timeout
Wed 2/1 17:29:56.056 TFTP timeout
Wed 2/1 17:29:57.051 TFTP timeout
Wed 2/1 17:29:58.044 TFTP timeout
Wed 2/1 17:29:59.035 TFTP timeout
Wed 2/1 17:30:00.032 TFTP timeout
Wed 2/1 17:30:01.024 TFTP timeout
Wed 2/1 17:30:02.125 TFTP timeout
Wed 2/1 17:30:03.117 TFTP timeout
Wed 2/1 17:30:04.110 TFTP timeout
Wed 2/1 17:30:05.105 TFTP timeout
Wed 2/1 17:30:05.105 Retry count exceeded

Thanks,
Josh

[spence]

Originally Posted by MrApollinax

Did you read the fix provided for the user earlier in this thread? Is your issue related to DHCP IP addressing as it was for the previous user? I just finished watching an episode of American Chopper using my MVP and have no issues with 4.1.6. A little more info would help us tell you if your problem is related to this or something else entirely.

Yes I've done that... Address and mask is normal. I added a network based scope to see if server would hickup and - no installed without a hitch... Address was assigned via DHCP, and tapped by its operating software on the PC.

I'm still open for ideas as to why it starts loading the application software to the MVP and then times out?

[MrApollinax]

@walts81 and spence

Any firewalls enabled that may prevent file tftp to the MVP?

[walts81]

Originally Posted by MrApollinax

@walts81 and spence

Any firewalls enabled that may prevent file tftp to the MVP?

Nope, and I had the MVP working great before upgrading. I tried uninstalling 4.1.6 and going back to 4.1.3 but the problem persisted.

- Josh

[MrApollinax]

Do you ever get the "Starting Application" screen? Have you done an ethernet capture of the communications between your server and the MVP to see where your communications breaks down? That information would be helpful for support as well as us here to help pinpoint where your break down occurs.

[walts81]

Originally Posted by MrApollinax

Do you ever get the "Starting Application" screen? Have you done an ethernet capture of the communications between your server and the MVP to see where your communications breaks down? That information would be helpful for support as well as us here to help pinpoint where your break down occurs.

It usually hangs on "Loading Application" but I got it to say "Starting Application" twice last night. But it just hung there, never went any farther. Don't know how to make an ethernet capture. ??

Thanks,
Josh

[MrApollinax]

Follow the instructions found in this post:

http://forums.sagetv.com/forums/show...4&postcount=45

[kminder]

Add me to the list of unfortunates. I have my network setup with my router as DHCP server giving out 192.168.0.0/24 addresses and the MVP has a static address of 192.168.0.22 assigned to its MAC. No workey.

I have a mix of static and dynamic IP and switching everthing over to 192.168.1.x even for a test will probably be several hours of work. (I may be exagerating but it feels that way.)

My problem is that I can't tell if the MVP really got an address or not. I guess I'm going to have to break down and install Ethereal on my server. Having to install WinPcap just makes my skin crawl for some reason. On the other hand I don't really want to go out an buy a hub just to be able to snoop from my dev box. I guess it all boils down to how much time, money and energy you have compared to how badly you want it. Tonight I'm falling short in the enery category.

Why can Hauppauge just put their software on firmware like everyone else? DHCP, BOOTP, TFTP and a bottle of rum. I don't want to have to work this hard on my home network. Grrr...

BTW. What are these entries in sage.properties I made based on the 4.1.4 announcment supposed to accomplish?
miniserver/automvp=true
miniserver/clients=MVP/00\:0D\:FE\:00\:8F\:FA/192.168.0.22
miniserver/gateway=192.168.0.1

If anyone has made it this far, below is a dump of of debug log from when the MVP is trying to boot.

Wed 2/1 22:58:16.931 Received bootp request
Wed 2/1 22:58:16.932 Op:1 hwtype:1 hwaddrlen:6hopcount:0
transaction:1325283027 nSeconds:100 flags:0
MAC: 00:0d:fe:00:8f:fa
Wed 2/1 22:58:16.933 Matched request to client 0
Wed 2/1 22:58:16.934 Warning, request from 00:0d:fe:00:8f:fa doesn't have IP.
Wed 2/1 22:58:24.095 PM currState=1 wakeupTime=Wed 12/31/1969 19:00:00.000

[MrApollinax]

Here is what my boot sequence for the MVP shows in the log:

Originally Posted by MVP boot

Tue 1/31 15:57:18.879 Received bootp request
Tue 1/31 15:57:18.879 Op:1 hwtype:1 hwaddrlen:6hopcount:0
transaction:-997606415 nSeconds:100 flags:0
MAC: 00:0d:fe:00:33:6e
Tue 1/31 15:57:18.880 Added MVP client to our bootp list 00:0d:fe:00:33:6e
Tue 1/31 15:57:18.880 Warning, request from 00:0d:fe:00:33:6e doesn't have IP.
Tue 1/31 15:57:27.899 Received bootp request
Tue 1/31 15:57:27.899 Op:1 hwtype:1 hwaddrlen:6hopcount:0
transaction:-997606415 nSeconds:100 flags:0
MAC: 00:0d:fe:00:33:6e
Tue 1/31 15:57:27.899 Matched request to client 0
Tue 1/31 15:57:27.900 Warning, request from 00:0d:fe:00:33:6e doesn't have IP.
Tue 1/31 15:57:36.951 Received bootp request
Tue 1/31 15:57:36.952 Op:1 hwtype:1 hwaddrlen:6hopcount:0
transaction:-509632359 nSeconds:100 flags:0
MAC: 00:0d:fe:00:33:6e
Tue 1/31 15:57:36.952 Matched request to client 0
Tue 1/31 15:57:36.952 servername 192.168.0.129
Tue 1/31 15:57:36.953 Sending bootp reply
Tue 1/31 15:57:37.084 Received tftp packet

Tue 1/31 15:57:37.086 Reading mvp.bin in mode octet (<--"Loading Applicaiton")
Tue 1/31 15:57:37.086 Opening file(<--"Starting Application")
Tue 1/31 15:57:44.412 PM currState=1 wakeupTime=Wed 12/31/1969 18:00:00.000
Tue 1/31 15:57:51.469 At last block
Tue 1/31 15:58:10.898 Server got broadcast packet: java.net.DatagramPacket@bed4e9
Tue 1/31 15:58:10.898 Server sent back mini discovery data:java.net.DatagramPacket@bed4e9to /192.168.0.149 3072 (<--"SageTV Loading Screen")
Tue 1/31 15:58:10.907 MiniUI got connection from Socket[addr=/192.168.0.149,port=3676,localport=31099]
Tue 1/31 15:58:10.909 MiniUI is adding to its map:000dfe00336e
Tue 1/31 15:58:10.910 Creating new UI for client:000dfe00336e
Tue 1/31 15:58:11.040 ImageUtils loading URL jar:file:/C:/Program%20Files/SageTV/SageTV/Sage.jar!/images/tvicon.gif
Tue 1/31 15:58:11.121 ImageUtils creating BI copy sun.awt.windows.WImage@b9c215
Tue 1/31 15:58:11.164 MiniUI established for 000dfe00336e(<--"SageTV UI")

As far as your sage properties go:

miniserver/automvp=true --> Server is enabled (not too sure about this one)
miniserver/clients=MVP/00\:0D\:FE\:00\:8F\:FA/192.168.0.22 -->(specify what IP address the MVP should request during bootp process. See my comments on this below)
miniserver/gateway=192.168.0.1 (Default Gateway of the MVP, needed to direct bootp broadcast packets)

I think you have the miniserver/clients property entered incorrectly. It should look like this:
miniserver/clients=MVP/00:0D:FE:00:8F:FA/192.168.0.22 (correct example)

not like this:
miniserver/clients=MVP/00\:0D\:FE\:00\:8F\:FA/192.168.0.22 (your example)

[kminder]

Thanks MrApollinax,
I'm fairly certian that I entered my MVP's MAC address correctly as you suggest because when I went back and checked the file I was surpised to see the backslashes. I just assumed that this was some annoying Java properties file escaping that occured when Sage rewrote the file.

So to be clear here your file does not contain the backslashes even after the sage server exits. Correct?

Thanks again.
Kevin.

[MrApollinax]

That is correct. However I have taken this out of my properties file now that the MVP is handling my router's DHCP reply correctly. I'm now statically assigning a DHCP addresss to the MVP via my router. There is no need to put that IP address in the file any longer. Just to clarify, by you putting in that IP address in your properties file you aren't configuring an IP for the MVP. All you are doing is telling the MVP to ask for the same address every session.

[walts81]

Well I checked the sage.properties file and it looked like this...

miniserver/automvp=true
miniserver/clients=
miniserver/gateway=192.168.0.1

So I added MVP/00:0D:FE:00:13:40 to the miniserver/clients. And BTW Sage does automatically put the backslashes in. I also switched my network over to 192.168.1.x addresses yesterday after seeing that others were having problems with the 192.168.0.x addresses. But I guess this didn't get updated in the sage.properties file so I changed that value as well. I haven't been able to test these changes since I'm at work so I'll let you guys know when I get home this evening.

Thanks,
Josh

[MurrayGill]

Originally posted by Narflex
I've seen this before when the router runs out of addresses for DHCP. (it really shouldn't) Changing the address range fixed it when I had that issue (which is basically what you did). So it might have been the same sort of thing...

Hmmm...I don't think it ran out of addresses. It was working with 4.1.3, then immediately stopped working after the upgrade to 4.1.6, and wouldn't work even after a hard reboot of the router (a D-Link DI-624). The change from 192.168.0.* to 192.168.1.* was the only other change.

If I can keep the WAF factor down, I may play around with it tonight.

2.5 days on 4.1.6 without needing to kill the sage service though. Response seems much improved as well...very happy

[kminder]

Interesting. I'm running a D-Link DI-624s. I wonder if there is anyone out there with working setup that includes a 624 series router. I've checked for firmware updates and there are none at least for the 624s.

[walts81]

Originally Posted by kminder

Interesting. I'm running a D-Link DI-624s. I wonder if there is anyone out there with working setup that includes a 624 series router. I've checked for firmware updates and there are none at least for the 624s.

Well I did have it working with a 624 (before I upgraded to 4.1.6). And it worked great. But it's not working after the upgrade (but I'm still working on the cause, might not have anything to do with the router).

- Josh

[ke6guj]

Well, I have a 624 in the mix with no problems. I have all my Sage stuff directly connected to a gigabit switch and then the switch is connected to the router. So, the only time that the MVP talks to the router is when it does DHCP. The router is set to assign "static" ip addresses (via MAC address) to everything on my network.

I don't do anything fancy with MAC addresses in sage.properties.

miniserver/automvp=true
miniserver/clients=
miniserver/gateway=192.168.0.1

Is it possible that your IP addresses don't match, between what you told Sage to use for the MVP, and what the MVP got from the router?

[walts81]

Well 2 full days at this and still no working MVP. I can't run ethereal because the MVP is connected via a wireless bridge and according to ethereal's website a capture over 802.11 is very limited. I have no firewalls setup. My network is 192.168.1.x. The MVP gets an IP (I can see it on my router's clients table). Sage can see it because it shows up in the log but for some reason times out on the tftp. And like I said before... the MVP was working perfectly before upgrading to 4.1.6. This is driving me nuts!

- Josh