Tiny Core Linux
Tiny Core Base => TCB Bugs => Topic started by: kurch on March 07, 2011, 06:31:35 AM
-
What is the problem with appbrowser?When I pressed the connect button, I encountered a message "Connection error, check network or mirror."
Please help me!
-
Are you connected to the Internet?
What does this give: $ sudo ping -c4 www.google.com
-
Are you connected to the Internet?
What does this give: $ sudo ping -c4 www.google.com
4 packets transmitted, 4 packets received
-
I've had this problem for a while now too. I think that something may have been changed in how AppBrowser connects to the internet when it was updated, or something in TC when it was updated. It only seems to affect the connection I have at home. I can access the world wide web, but not the mirrors. From school, I can access the mirrors perfectly. Trying the ping, I too get a 0% packet loss.
-
By and large what 'appbrowser' does for downloading is actually handled by the 'tce-load' tool, which itself uses the Busybox 'wget' applet. IMHO doing a 'ping' test is a necessary but not a sufficient pre-condition for ensuring that 'wget' will work.
I'd therefore suggest to make sure that a simple test like wget -qO - http://example.com proves that HTTP transfers are OK, before moving on to a test with a specific file of the main repository (e.g. via wget -qO - http://distro.ibiblio.org/tinycorelinux/3.x/mirrors.lst)
-
in TC 3.5.1 it seems that appbrowser points to:
http://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/
instead of
http://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/3.x/tcz/
-
in TC 3.5.1 it seems that appbrowser points to:
http://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/
instead of
http://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/3.x/tcz/
Whilst it is correct that the default entry in '/opt/tcemirror' is 'http://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/' the 'getMirror()' function (in '/etc/init.d/tc-functions') "converts" this to 'http://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/3.x/tcz/' by taking the version information (from '/usr/share/doc/tc/release.txt') into account.
AFAIK this has been the case since quite a long time at least for all of the TC 3.x series. Due to some recent changes on the main repository (i.e. ibiblio.org) the default entry could now be shortened to http://distro.ibiblio.org/tinycorelinux/. But that is for Robert and the team to decide, e.g. how much they trust ibiblio.org to keep things set up into the future as they are currently working.
I'm just lazy and like to save myself (and possibly others) from non-required typing, hence I used the "non-default" URL in my reply #4. Nevertheless I try really hard to always check that the links I'm posting are actually working (at least at the time of posting).
-
this is indeed not a real 'bug', that's why I have hesitated to post, but simple use of appbrowser (yesterday evening)
was an issue. Pressing the connect button displays all extensions in the repository, while trying to download (download only option) an extension within appbrowser results in 'server not found' error. doing the same at the command line with the full url (wget) works.
-
definitely a problem with ibiblio, it works ok today
-
I cannot download anything please help me
-
Can not help anybody?
-
check the following
1. that you are connected: sudo ping www.google.com in aterm should retrieve lines with packets sent and received; to stop the output, press ctrl+c;
2. if you are connected, then load appbrowser, and connect to the main server; it should display all extensions entries; select one and download it.
if you are connected to the internet, and you can not see the extensions in appbrowser, or can not download one of these, you might have a problem with your proxy; in this case, you should ask your proxy to give you the gateway to connect to in order to be able to download things from the internet (issuing route -e in aterm should give you your current gateway). Note that this might not be possible tough, because proxies could block downloads for security reasons.
-
check the following
1. that you are connected: sudo ping www.google.com in aterm should retrieve lines with packets sent and received; to stop the output, press ctrl+c;
2. if you are connected, then load appbrowser, and connect to the main server; it should display all extensions entries; select one and download it.
if you are connected to the internet, and you can not see the extensions in appbrowser, or can not download one of these, you might have a problem with your proxy; in this case, you should ask your proxy to give you the gateway to connect to in order to be able to download things from the internet (issuing route -e in aterm should give you your current gateway). Note that this might not be possible tough, because proxies could block downloads for security reasons.
When I wrote route -e in the aterm, I encountered message:
(http://i1103.hizliresim.com/2011/3/21/7532.png) (http://goo.gl/mc9cY)
-
I have the impression that to help you further we need a "fuller picture" (and I don't mean a screenshot as IMHO this sort of information as straight text is much easier to digest without having to scroll around).
Would you please provide the output of ifconfig eth0 ; route ; cat /etc/resolv.conf What is the reason that you don't use DHCP (as I assume that you use some sort of router to connect to the internet)? Do you use a HTTP proxy?
Furthermore, I'd suggest to first test downloading from the main repository with a simple test like wget -qO - http://distro.ibiblio.org/tinycorelinux/3.x/mirrors.lst as in the failure case some useful information for further troubleshooting might come up.
-
from your screenshot, nameserver is most probably wrong, and default gateway should be smthg like 192.168.1.254, and not 'dsl'; as maro said, use dhcp, so try this:
1. open aterm, and type: sudo killall udhcpc
2. in aterm, type: sudo ifconfig eth0 up
3. in aterm, type: sudo ifconfig eth0 essid YOURESSID key YOURKEY
4. in aterm type: sudo udhcpc -H box -b -i eth0
5. control that you are connected in aterm, type: sudo ping www.google.de (stop the output with ctrl+c)
Note: YOURESSID is the name of your network; you must write something here;
Note: YOURKEY is the name of your encrypted key (wep or wap key); if you don't have one, replace YOURKEY with "off" (without quotes).
-
from your screenshot, nameserver is most probably wrong, and default gateway should be smthg like 192.168.1.254, and not 'dsl'
Some routers would indeed resolve like this.
route -nwould show the IP.
Either way, I could not see nameserver showing in screenshot.
.
3. in aterm, type: sudo ifconfig eth0 essid YOURESSID key YOURKEY
Those are rather options of iwconfig than of ifconfig.
kurch has not been clearly stating in what way they would connect, but given the ifname I'd reckon it's ethernet.
EDIT: Oops, now I can see what maro meant about "having to scroll around", hadn't occured to me... :P
Nevertheless, I think '192.168.1.1' would be most common if one uses nameserver on a router.