Forum › Forums › Freesat HD › FOXSAT HDR › opkg update failure after v4.1.2 firmware install
- This topic has 32 replies, 6 voices, and was last updated 12 years, 1 month ago by
Anonymous.
-
AuthorPosts
-
October 8, 2013 at 5:55 pm #47273
Anonymous
InactiveDino,
ping router from HDR shows unknown error -89
arp -a= from telnet HDR
Foxsat-Box~# arp -a
agreed see pc ip and router ip
tracert 89.248.55.76 from HDR = not found
October 8, 2013 at 6:00 pm #47274Anonymous
InactiveDino,
on HDR box in a telnet session
Foxsat-Box~# netstat -r
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
192.168.1.0 * 255.255.255.0 U 0 0 0 eth0
default 192.168.1.1 0.0.0.0 UG 0 0 0 eth0
fyi my pc ( upstairs 192.168.1.2 ) is connected to the modem router ( downstairs 192.168.1.1 ) via a router ( which acts as a switch upstairs 192.168.1.0 ) does this affect things?
October 8, 2013 at 7:17 pm #47275Anonymous
InactiveMark,
When you ping the router from the HDR, ignore the line saying “ping: recvfrom: Unknown error -89” in the results, just look for lines that include ‘time’ – something like
“64 bytes from 192.168.1.1: seq=1 ttl=64 time=2.249 ms”
Then when you press ctrl c to end, you should get something like
“— 192.168.1.1 ping statistics —
50 packets transmitted, 50 packets received, 0% packet loss
round-trip min/avg/max = 1.022/1.637/2.619 ms”
This is the result we want. If you get a sequence of only
“ping: recvfrom: Unknown error -89” messages and at the end something like
“— 192.168.1.1 ping statistics —
6 packets transmitted, 0 packets received, 100% packet loss”
Then that means there’s a problem.
With that in mind, test in stages – each time look for the times and 0% packet loss at the end of the sequence.
1) Pinging the modem/router address from the HDR telnet session.
ping 192.168.1.1
If you get a positive result for this, then try
2) Pinging the repository by number.
ping 89.248.55.76
Again look for the line showing the time. If this works try
3) Ping something else by name to test DNS e.g.
ping bbc.co.uk
If that works ok try the final one
4) Ping the repository by name
ping hummypkg.org.uk
If all that works, then the HDR is accessing the Internet and using DNS ok. So it should be possible to update from the repository.
If not, let us know which bit doesn’t work.
Dino
October 8, 2013 at 8:06 pm #47276Anonymous
InactiveOk Dino, I see what you need now:
1) 0% packet loss
2) 0 packets, 100% packet loss!
3) bad address!
4) bad address!
The humax ( 192.168.1.4 ) is plugged via ethernet straight into the modem? Will disconnect and reconnect cable to see if that’s the problem
October 8, 2013 at 9:13 pm #47277Martin Liddle
Participantmamos22 – 1 hour ago »
The humax ( 192.168.1.4 ) is plugged via ethernet straight into the modem? Will disconnect and reconnect cable to see if that’s the problem
What make and model of modem? Is this cable or ADSL or FTTC?
October 8, 2013 at 9:13 pm #47278Anonymous
InactiveOK, if we failed at step one, that means the HDR & router/modem aren’t talking properly across your LAN using IP.
I thought earlier you said there was an arp entry for the router in the HDR cache and that you are using DHCP. These imply the physical connection is ok.
As the PC is talking to both the router/modem & the HDR using IP, this suggests that the router might be ignoring the HDR’s IP traffic somehow. Does the router/modem have any config which limits which addresses it lets onto the Internet ?
October 8, 2013 at 9:34 pm #47279Anonymous
InactiveHi mamos22,
no not that Damian, just had to google zappiti to double check that the wine hasn’t destroyed one too many brain cells.
Until Dino replies…
I’m guessing the HDR is trying to access the internet via the switch/router you have at 192.168.1.0
This may explain why you can ping 192.168.1.1 but not get any further.
I was in two minds whether to recommend re-installing firmware as I originally thought the opkg may have corrupted network on the HDR, but as you can ping to 192.168.1.1 it looks more like a routing issue.
I’m assuming pc upstairs, router acting as switch/hub at 192.168.1.0, router/modem downstairs 192.168.1.1 connected to adsl/cable/internet and HDR also downstairs connected to router/modem
If this is the case, then a quick test would be to switch off the switch/hub 192.168.1.0 upstairs or unplug network cable to it, reboot HDR and see if you can access iplayer on the HDR. What should happen is HDR on reboot should connect to dhcp on the 192.168.1.1 modem/router and magically work
You really need to make sure that the 192.168.1 0 and 1 address are connecting to the routers that you think they are, unless they are completely different from menu it may help to physically switch one off whilst configuring the other.
Moving forward, I would give the main router a 192.168.1.1 address, the switch/hub router (currently on 0) 192.168.1.8 or similar, make sure that switch/hub has dhcp switched off and any other settings that allow you to use it as a router, basically you just want it as a hub to connect upstairs to downstairs, I think.
If you want to stick with dhcp then by all means set up a pool on the 192.168.1.1 from 192.168.1.20 – 192.168.1.50
Personally I’d have a small pool for guests/testing, but always have manual entries for fixed/static devices which aids testing/diagnosis
In this case assign something like 192.168.1.60 to the pc and 192.168.1.80 to the HDR, netmask 255.255.255.0 gateway/dns 192.168.1.1
Edit.
just seen dino’s reply, and it’s not sensible for both of us to be asking/suggesting at the same time, I’m more than happy to sit back, take a look at the above, try what I’ve suggested, if there’s anything you don’t understand report back and if there’s anything different in your setup let us know, the more relevant info you provide the easier it is for someone here to put their finger on it, I assume things have been setup as I would do it so may overlook a different way of connecting equipment and it’s obviously not always the case, particularly with wifi, dongles, homeplugs and some people who create dmz’s or block ports.
October 9, 2013 at 5:38 am #47280Anonymous
InactiveMark,
I’ve been assuming that 192.168.1.1 is the address of the router/modem that connects to the Internet as this is a commonly used convention. Let us know if this isn’t correct.
Can you confirm what the default gateway of the working PC is ?
I’ve also assumed that 192.168.1.0 for the second router you’ve referred to (for the PC upstairs ?) was a typo since all zeros in the host range is invalid for a host and I’ve assumed that this router was probably operating as a wireless bridge rather than a router.
Can you confirm this is your set up ?
As Damian says there’s several ways of doing things, but on a home LAN, having two routers both operating as routers might be tricky and could lead to some devices not being able to reach the Internet while working ok locally.
Dino
October 9, 2013 at 8:50 am #47281Anonymous
InactiveDino, re your earlier response yesterday, yes DHCP is definitely on, the modem router ( DLink DSL-2740B ) has several menu options and I can see it showing the HDR’s ip ( 192.168.1.4 ) is 1 of 2 connected LAN clients that are not being blocked, going through all the menus, I cannot see any obstruction to the HDR box, I don’t have any blocked IP addresses, it also states I have 4 dynamically connected DHCP clients but doesn’t show them.
Damian’s assumption from earlier is correct re setup:
“I’m assuming pc upstairs ( this is 192.168.1.5) , router acting as switch/hub at 192.168.1.0 ( this is upstairs next to pc ), router/modem ( model – Dlink DSl-2740b ) downstairs 192.168.1.1 connected to adsl internet and HDR ( 192.168.1.4 ) also downstairs connected to router/modem ( 192.168.1.1 )”
Default Gateway is the dLink @ 192.168.1.1
My PC upstairs is connected by ethernet cable to router upstairs ( 192.168.1.0 ), the router is connected to the DLink modem router downstairs ( 192.168.1.1 ) which the HDR downstairs is connected to. This was ideally to give me wireless upstairs due to wi-fi issues and assumed from what I could see that this was correct so that the router upstairs acted as a switch.
appreciate your help, will try switching off upstairs router per Damian’s reply
October 9, 2013 at 9:45 am #47282Anonymous
Inactiveswitching off the upstairs router meant that the iplayer on the HDR connected first time, before I switched of the router it showed that I wasn’t connected ( I am so used to seeing this that I don’t use iplayer on the HDR and haven’t for along time, it uses only connects 1 in 10 attempts even after rebooting downstairs modem router ). Sorry I should have mentioned this but as I never use it I just thought that it was a problem with the box re iplayer.
Switching back on the upstairs router 192.168.1.0 and rebooting the HDR surprisingly still shows iplayer on the HDR to be working!
Going back into the web interface, I successfully updated the packages and upgraded the webif with no problems!
Thanks very much Dino & Damian, that seems to have done the trick!
Appreciate all your help as would never have sorted this otherwise and would have given up!
Damian,
will re-read your post and proceed to use static ip addresses to see if that helps.
Many thanks again, will keep testing and upgrading / installing packages to see how long this lasts
will check and configure upstairs router as you suggest, no dmz on modem router or upstairs router set, will check all settings and let you know
October 9, 2013 at 2:16 pm #47283Anonymous
InactiveIf you only use the upstairs router as a switch you will save yourself a lot of complication (Don’t use the internet port – just the switch ports for the connection to the other router as well). You will need to check that it has DHCP turned off as well as the other router is doing that).
Your problem before is that you were using the same subnet for both units with an incorrect subnet mask – 255.255.255.0 won’t work as the last zero says all address in that subnet (192.168.1) are connected to the router – so both routers would not pass traffic to each other.
October 9, 2013 at 2:38 pm #47284Anonymous
InactiveGlad it’s sorted. Two routers on the same home LAN is generally a bad idea.
October 9, 2013 at 5:37 pm #47285Anonymous
InactiveOk Thanks Repassac, router is connected to modem router by the ports not the “internet” connection, however was unaware that the subnet mask couldn’t be the same as thought it was critical that they were the same?
Assume, just changing the last digit for the subnet mask on one of the routers will correct the issues I had – as this is the first network I have had to setup? Aside from this issue haven’t had any other issues re accessing connections on the network.
Am fairly sure the router has DHCP disabled but will chk again as not so easy getting into it’s settings.
Thanks again Dino, reason for two routers is rubbish wi-fi coverage due to solid wall blocking wi-fi signal to my bedroom.
October 9, 2013 at 6:06 pm #47286Anonymous
InactiveA switch upstairs might be an option. It can’t interfere with the main router’s role but you’d need a cable to it from the main router.
If you can’t run a cable, a wireless bridge would be a better bet than a router.
Other people opt for Home Plugs in this scenario.
Basically – try to avoid having two routers on the same home LAN.
October 9, 2013 at 6:24 pm #47287Anonymous
InactiveIf this is so then all should be well unless you have two DHCP servers (a mistake) – if nothing is connected to the internet port then all should be well if you have disabled the upstairs router DHCP server.
Sorry for imposing on the other contributor’s to the thread.
-
AuthorPosts
- You must be logged in to reply to this topic.