Dino, I get ping: recvfrom: Unknown error -89 constantly
My Humax Forum » Freesat HD » FOXSAT HDR
opkg update failure after v4.1.2 firmware install
(33 posts)-
| Tue 8 Oct 2013 16:23:44 #11 |
-
I was about to add, I had problems with my DNS this morning, BT servers, and I needed to change the DNS on my router to get certain addresses resolved properly. I could get some sites, but I didn't check to see whether they were cached locally or not it seemed easier to change the DNS entry, happens once in a blue mooon.
If you have a pc/laptop ping hummypkg.org.uk from a dos/command window
and then do the same from the Humax from the telnet promptboth should resolve to 89.248.55.76
you should also be able to ping the above ip address as Dino asked from the Humax. If you can then you need to look at the DNS on the router, reboot it or add different DNS servers would be the easiest and quickest option. If you can't ping the ip address from the Humax then there are other problems.
Edit:
just seen your latest reply, have you tried physically rebooting both the router and Humax. The DNS problems I saw this morning could have mucked up the router.
It'd also be interesting to know whether you can ping hummypkg.org.uk from the pc/laptop and not from the Humax after the reboots.| Tue 8 Oct 2013 16:36:06 #12 | -
Thanks Damian ( just curious - assume you're not the same damian from a Dune / zappiti forum I once used? ), anyway can ping 89.248.55.76 sucessfully from an dos/command session on my networked pc, still unknown error -89 from telnet session.
switching off modem router and humax still shows same results as above
can ping hummypkg.org.uk sucessfully from a dos/command session on my networked pc, still get "bad address" from telnet session.
| Tue 8 Oct 2013 16:52:19 #13 | -
If you can't ping by number, it can't be a DNS issue as there's no DNS required. Can the HDR ping the router ?
ping 192.168.1.1
Then enter
arp -a
You should see at least two entries, one being your PC and the other being the router.
If your router is in the arp cache try a traceroute to the repository.
traceroute 89.248.55.76
Let us know the results.
| Tue 8 Oct 2013 17:22:35 #14 | -
One more request. On the HDR enter
netstat -r
on the HDR and post up the results.
Dino
| Tue 8 Oct 2013 17:25:25 #15 | -
Dino,
ping router from HDR shows unknown error -89
arp -a= from telnet HDR
Foxsat-Box~# arp -a
agreed see pc ip and router iptracert 89.248.55.76 from HDR = not found
| Tue 8 Oct 2013 17:55:27 #16 | -
Dino,
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 eth0fyi 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?
| Tue 8 Oct 2013 18:00:56 #17 | -
Mark,
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
| Tue 8 Oct 2013 19:17:04 #18 | -
Ok 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
| Tue 8 Oct 2013 20:06:09 #19 |
Reply »
You must log in to post.
