2006-07-16, 15:01
i was over at a friend's house trying to get Kai working for him. he has a pretty normal household LAN, with CAT5 cable connecting a couple PCs and his Xbox to a router, which handles DHCP and NAT for the broadband connection for the whole place.
installed the latest version of the engine onto a Windows XP Pro box, forwarded a single port as needed, entered the user info. bada-bing, the engine ran without a problem and appeared to be functioning normally from the Windows GUI.
his Xbox was running a CVS build of XBMC from i believe either yesterday or the day before, so no older than 72 hours. the Xbox was set to use DHCP, and this was working flawlessly prior to these adventures, with weather, RSS, scripts, and LAN media streaming all working fine.
so we enabled Xlink Kai in Settings > My Programs, and it auto-entered the stuff (just love that feature
), and then upon returning to the Home screen, the Kai button was visible. it was also showing the "connected" graphic in My Programs.
we could successfully go into the Kai/MyBuddies Window and browse for maybe 2 minutes, then we received a "disconnected" message.
this is where it gets weird.
upon resetting the Xbox to attempt to "make it work again", XBMC's internet access ceased to function. a quick look at the IP address and i found something very odd:
with the Kai engine running on a PC on the LAN, XBMC wasn't able to resolve an IP address correctly using DHCP. instead of the 192.168.0.1xx mask used by the LAN, it was receiving an IP address starting with 10. and containing a bunch of apparently random numbers. aren't 10.x.x.x addresses considered reserved/unroutable?
anyways, is there any good explanation for why DHCP for XBMC is completely disrupted while the Kai engine is running on this network? the best one i have so far is "the router is jocked up". it IS a quite old router (one of the port forwarding preconfigs was for Battle.net
), and from an off-brand, so i am thinking it's just crappy and needs a firmware update.
installed the latest version of the engine onto a Windows XP Pro box, forwarded a single port as needed, entered the user info. bada-bing, the engine ran without a problem and appeared to be functioning normally from the Windows GUI.
his Xbox was running a CVS build of XBMC from i believe either yesterday or the day before, so no older than 72 hours. the Xbox was set to use DHCP, and this was working flawlessly prior to these adventures, with weather, RSS, scripts, and LAN media streaming all working fine.
so we enabled Xlink Kai in Settings > My Programs, and it auto-entered the stuff (just love that feature
), and then upon returning to the Home screen, the Kai button was visible. it was also showing the "connected" graphic in My Programs.we could successfully go into the Kai/MyBuddies Window and browse for maybe 2 minutes, then we received a "disconnected" message.
this is where it gets weird.
upon resetting the Xbox to attempt to "make it work again", XBMC's internet access ceased to function. a quick look at the IP address and i found something very odd:
with the Kai engine running on a PC on the LAN, XBMC wasn't able to resolve an IP address correctly using DHCP. instead of the 192.168.0.1xx mask used by the LAN, it was receiving an IP address starting with 10. and containing a bunch of apparently random numbers. aren't 10.x.x.x addresses considered reserved/unroutable?
anyways, is there any good explanation for why DHCP for XBMC is completely disrupted while the Kai engine is running on this network? the best one i have so far is "the router is jocked up". it IS a quite old router (one of the port forwarding preconfigs was for Battle.net
), and from an off-brand, so i am thinking it's just crappy and needs a firmware update.
