Forum › Forums › Freesat HD › FOXSAT HDR › hdr – pc connect without internet
Tagged: no internet hdr - pc network
- This topic has 29 replies, 6 voices, and was last updated 11 years, 11 months ago by
Anonymous.
-
AuthorPosts
-
June 17, 2013 at 2:49 pm #14684
Anonymous
InactiveHi , and many thanks for your updates and work on the HDR etc.
I have an old HDR and have installed the upgrades you have provided.
the screen shows the update is installed.
I still cannot access the hdr from windows, running XP64
I have no internet connection which seems to be a problem. I can ping the HDR but cannot get a network connection, either with the browser or the network tools.
Is there a way of doing so without an internet connection, and if so how do I do it, or if yo know of a resource with instructions would you be so kind as to guide me to it.
Many thanks Bill Hooks.
June 17, 2013 at 5:11 pm #45305Anonymous
InactiveBill,
Not having the Internet won’t stop you accessing the HDR on your own LAN.
From the information, it sounds like the custom software *isn’t* actually installed.
When you say ‘the screen shows the update is installed’, what do you mean by this ?
When you boot it up from cold, do you get the custom firmware message on the HDR’s own display panel ?
After you ping the HDR, type ‘arp -a’ in the command line and let us know what physical address is reported.
Dino
June 17, 2013 at 7:15 pm #45306grahamlthompson
ParticipantAfaik without internet access the OP will find it hard to install and update the various packages. After the basic re-flash the PC downloads and installs the full version from the internet repository. Updates are internet delivered.
June 21, 2013 at 11:41 am #45307Anonymous
InactiveOK Thanks gents.
The Firmware update message shows in the HDR window on boot up.
FW4.8 etc.
Pinging the set IP gives a return contact of about 0.2ms.
I will try the hardware ping later and report back on Monday
or sooner if I can get online somewhere.
June 21, 2013 at 1:17 pm #45308Anonymous
InactiveIt is possible to download the packages from http://hummypkg.org.uk/foxsat/ to USB from a location which does have access and then apply them. However I am not sure of the sequence required.
You should have access on your LAN via http://ipaddress.
The Foxsat will not appear in your network until after samba is installed.
Try the following on a USB stick. The packages (right click on the links and use ‘save as’)
busybox 1.18.4-1
epg 1.5
hmt 2.2
jim-tcl 0.7.1-1
samba 2.2.12-1
service-manager 2.0
sysclock 1.1
telnet 1.0
twonky4 4.4.18
webif 2.75
webif-docs 1.01
channel-icons 1.06
The dependencies are known in the package files – so I would try inserting a USB stick and waiting until activity is complete, remove the stick and reinsert after 10 secs or so. Applied packages are deleted from the stick.
raydon or Adrian could you comment on the sequence please.
June 24, 2013 at 11:20 am #45309Anonymous
InactivePacks have been loaded on stick and so I believe installed. No way to check as no pc connectivity.
Log from pings attached: No arp found.
Network info:
Physical Address: 30-85-A9-49-44-C5
IP Address: 169.254.60.57
Subnet Mask: 255.255.0.0
Default Gateway:
DNS Server:
WINS Server:
June 24, 2013 at 5:24 pm #45310Anonymous
InactiveBill,
Is 169.254.60.57 your PC ? If so it is pinging itself. You need to work out what the IP address is of the HDR from the menu.
Use ‘menu’, then down to ‘system’ and across to ‘network’
There should be an IP address. Note it and ping it from a device on the same network.
If the HDR is not on a LAN don’t bother with the custom firmware. It doesn’t have to be on the Internet, but it does have to be on a LAN in order to get any benefit from it.
Dino
June 24, 2013 at 7:05 pm #45311Anonymous
InactiveBill,
looking at your attachment your PC is 169.254.60.57
Your PC and HDR need to be network connected together; either via a network hub/switch or router or a cross-over cable.
If you don’t have a network hub or a cross-over cable then an old BT router or similar will do so long as it’s got power and network sockets. Once everything is connected, reboot the router if necessary, reboot the PC and HDR
If you’re using a router you may find that your PC ip address changes to something like 192.168.1.?
If this is the case then your HDR will also be assigned an ip address via DHCP automatically which you’ll need to check as per Dino’s instructions above.
If you’ve kept the original 169.254.60.57 on your PC then you probably need to manually assign an ip address to the HDR using the menu,system,network option on the HDR, add something like 169.254.60.59, netmask 255.255.255.0, Gateway/DNS 169.254.60.1
If this doesn’t work or isn’t making much sense, please get back to us with a description of the equipment you’ve got and what it is you’re trying to achieve. I’m assuming you don’t have internet and you either want to watch programmes from the HDR on your PC or you simply want to use the PC to administer the HDR and the custom firmware is excellent for this.
June 26, 2013 at 1:00 pm #45312Anonymous
InactiveThe IP address shown is for the Humax HDR not the PC. Runnig through a 100mp switch.
I have tried reinstalling the package as suggested and this has revealed a problem:
Install started
Collected errors:
* pkg_init_from_file: Malformed package file /opt/tmp/samba_2.2.12-1_mips.opk.
Install done
The remaining packages are not installed due to unfullfilled requirements, IE samba.
And on some incorrect architecture. Is this because another file is missing?
You are correct I want to watch programmes from the HDR on PC and use the PC to administer the HDR.
I will dig around and see if I can find an alternate version of the samba pack, and try reinstalling the apps.
Thanks again, hope we can get this working, I can’t wait till I can put the channels in the order I want.
Bill
June 26, 2013 at 2:53 pm #45313Anonymous
InactiveBill, I notice that both the gateway and DNS are not set.
Is there a fully configured DHCP server on that network?
June 26, 2013 at 3:45 pm #45314Anonymous
InactiveBill,
Did you manually set the HDR’s IP address ?
It looks like the IP/MAC in your attachment is that of an Asus machine – the screen shot looks like windows and I think the HDR would only have got that address if it had been manually set.
Can you confirm two things.
1) the IP address and mask of the HDR (from the on screen menu)
2) the IP address and mask used by your PC (from settings->control panel).
Thanks
Dino
June 26, 2013 at 6:36 pm #45315Anonymous
InactiveHi Bill,
I agree with Dino on this.
I was also wondering whether your pc is an Asus laptop which you connect to the internet via a dongle or similar and you also want to connect directly to the HDR via your hub with network cable. This would explain the unassigned/default physical ip address on your laptop? or pc.
If this is the case then there are ways of connecting the HDR to the internet via your laptop, but this is way beyond my realms of explaining exactly how step by step. Adding the packages manually should work, but as you’re finding out, it isn’t straight forward. Alternatively it’d be a lot easier to take the hdr to a friend’s house and setup using their internet router. Take a bottle of wine and enjoy.
It would however be very useful to physically check and confirm the two things Dino has asked for, plus any other information that maybe relevant
cheers
June 28, 2013 at 10:39 am #45316Anonymous
InactiveHi Gents,
Firstly dino: Yes, I manually set the IP’s on all computers and the HDR.
IP Address: 169.254.60.57 for HDR the PC’s :169.254.60.50/52/54/55
Subnet Mask: 255.255.0.0 is common to all.
Meanwhiles:
An interesting few days. I downloaded fresh, the bundle and the individual packages.
Copied one version onto each mem stick.
Plugged in and ran Samba initially, but both versions failed as before. Malformed package.
I found an earlier samba version, which failed on architecture. Thinking this may be due to the patch version
I upgraded the patch to 4.09.
Tried to install Samba2.73, but got the mal failure again, and got a webif requirment for the later version.
I then ran through the rest of the packages and the main problem seems to be the webif failure, which everything else seems to rely on.
There are som more package failures also. Logs listed below. Is there another location, other than the wikipage where I can find the downloads.
Manny thanks
Bill
Install started
Collected errors:
* pkg_hash_fetch_best_installation_candidate: Packages for webif found, but incompatible with the architectures configured
* opkg_install_cmd: Cannot install package webif.
Install done
Install started
Installing webif (2.75) to root…
Collected errors:
* satisfy_dependencies_for: Cannot satisfy the following dependencies for webif:
* webif-docs * channel-icons *
* opkg_install_cmd: Cannot install package webif.
Install done
Install started
Installing webif (2.75) to root…
Collected errors:
* satisfy_dependencies_for: Cannot satisfy the following dependencies for webif:
* webif-docs * channel-icons *
* opkg_install_cmd: Cannot install package webif.
Install done
Install started
Installing webif-docs (1.01) to root…
Collected errors:
* satisfy_dependencies_for: Cannot satisfy the following dependencies for webif-docs:
* webif (>= 2.74) *
* opkg_install_cmd: Cannot install package webif-docs.
Install done
Install started
Installing channel-icons (1.06) to root…
Collected errors:
* satisfy_dependencies_for: Cannot satisfy the following dependencies for channel-icons:
* webif (>= 2.74) *
* opkg_install_cmd: Cannot install package channel-icons.
Install done
Install started
Installing channel-icons (1.06) to root…
Collected errors:
* satisfy_dependencies_for: Cannot satisfy the following dependencies for channel-icons:
* webif (>= 2.74) *
* opkg_install_cmd: Cannot install package channel-icons.
Install done
Install started
Collected errors:
* deb_extract: /opt/tmp/busybox_1.20.2-1_mips.opk: invalid magic
* pkg_init_from_file: Failed to extract control file from /opt/tmp/busybox_1.20.2-1_mips.opk.
Install done
Install started
Installing inadyn (1.96.2-2) to root…
Collected errors:
* satisfy_dependencies_for: Cannot satisfy the following dependencies for inadyn:
* webif (>= 2.72) *
* opkg_install_cmd: Cannot install package inadyn.
Install done
Install started
Installing channel-editor (0.53-1) to root…
Collected errors:
* satisfy_dependencies_for: Cannot satisfy the following dependencies for channel-editor:
* webif (>= 2.72) *
* opkg_install_cmd: Cannot install package channel-editor.
Install done
Install started
Installing twonky5 (5.1.6) to root…
Collected errors:
* check_conflicts_for: The following packages conflict with twonky5:
* check_conflicts_for: twonky4 * check_conflicts_for:
* opkg_install_cmd: Cannot install package twonky5.
Install done
Install started
Installing ssmtpmail (1.0-1) to root…
Collected errors:
* satisfy_dependencies_for: Cannot satisfy the following dependencies for ssmtpmail:
* webif (>= 2.72) *
* opkg_install_cmd: Cannot install package ssmtpmail.
Install done
Install started
Installing fixfilenames (1.0-1) to root…
Collected errors:
* satisfy_dependencies_for: Cannot satisfy the following dependencies for fixfilenames:
* webif (>= 2.72) *
* opkg_install_cmd: Cannot install package fixfilenames.
Install done
Install started
Installing housekeeper (3.1-3) to root…
Collected errors:
* satisfy_dependencies_for: Cannot satisfy the following dependencies for housekeeper:
* webif (>= 2.72) *
* opkg_install_cmd: Cannot install package housekeeper.
Install done
Install started
Installing nasmount (2.0) to root…
Collected errors:
* satisfy_dependencies_for: Cannot satisfy the following dependencies for nasmount:
* webif (>= 2.73) *
* opkg_install_cmd: Cannot install package nasmount.
Install done
Install started
Installing mobile-remote-control (1.2) to root…
Collected errors:
* satisfy_dependencies_for: Cannot satisfy the following dependencies for mobile-remote-control:
* webif (>= 2.71) * remote-control (>= 1.2-1) *
* opkg_install_cmd: Cannot install package mobile-remote-control.
Install done
Install started
Installing remote-control (1.2-1) to root…
Collected errors:
* satisfy_dependencies_for: Cannot satisfy the following dependencies for remote-control:
* webif (>= 2.72) *
* opkg_install_cmd: Cannot install package remote-control.
Install done
Install started
Installing vlcplayer (1.0-3) to root…
Collected errors:
* satisfy_dependencies_for: Cannot satisfy the following dependencies for vlcplayer:
* webif (>= 2.72) *
* opkg_install_cmd: Cannot install package vlcplayer.
Install done
June 29, 2013 at 6:34 am #45317Anonymous
InactiveBill,
Still slightly confused, but it appears you are able to contact the HDR over your LAN, I’m guessing that you have at least telnet access to the HDR from a PC which is how you are getting the information that the package isn’t installing fully.
You say you are trying 4.0.8 and 4.0.9. I think this might not be a good idea. The latest version of the custom firmware is 4.1.1. The version of CF required can be related to the version of the humax software.
Do you know what version of standard humax software you have (or started with) ?
If you don’t know, I’d suggest getting the latest official software (1.00.21) from
http://beta.humaxonline.co.uk/downloads/foxsat-hdr
and installing that so you know your starting point.
Once you’ve got that working, get the 4.1.1 version of the CF and try installing that using the off line method. Otherwise, as has been suggested, get the updated box online temporarily and install the CF over the Internet.
Dino.
June 29, 2013 at 8:16 am #45318grahamlthompson
ParticipantInstalling the latest CF will also update the Humax firmware if the currently installed Humax software doesn’t match that required for the update.
-
AuthorPosts
- You must be logged in to reply to this topic.