Hi Sashank999
I don't know what is going on, but I do not think it is a misconfiguration issue with Tinycore. I want to do a brief recap of observations
and follow up with a couple of questions/causes.
This command:
wget --debug --output-file=icu.txt http://repo.tinycorelinux.net/11.x/x86_64/tcz/icu65-dev.tcz
Appears to show wget trying to use IPv6 addressing, possibly because it's being offered an IPv6 address to use:
Reading HSTS entries from /home/tc/.wget-hsts
--2020-08-04 13:43:51-- http://repo.tinycorelinux.net/11.x/x86_64/tcz/bash.tcz
Resolving repo.tinycorelinux.net... 89.22.99.37, 64:ff9b::5916:6325
Caching repo.tinycorelinux.net => 89.22.99.37 64:ff9b::5916:6325
Connecting to repo.tinycorelinux.net|89.22.99.37|:80... connected.
The download used only 6% of your connections bandwidth which is unacceptable.
This command:
wget --debug --output-file=icu.txt --inet4-only http://repo.tinycorelinux.net/11.x/x86_64/tcz/bash.tcz
This forces wget to use only IPv4 addresses, which it does:
Reading HSTS entries from /home/tc/.wget-hsts
--2020-08-06 04:34:34-- http://repo.tinycorelinux.net/11.x/x86_64/tcz/bash.tcz
Resolving repo.tinycorelinux.net... 89.22.99.37
Caching repo.tinycorelinux.net => 89.22.99.37
Connecting to repo.tinycorelinux.net|89.22.99.37|:80... connected.
The download used 30% of your connections bandwidth which sounds reasonable.
The busybox version, which is used by tce-load and Apps:
time busybox wget -S http://repo.tinycorelinux.net/11.x/x86_64/tcz/bash.tcz > icu.txt 2>&1
Does not provide the debug information that the wget.tcz version does.
It does appear to be more severely effected by what's going on since it used only 1% of your networks bandwidth.
I suspect this is an IPv6 issue, yet there are no instances of ipv6 mentioned in the sysctl.txt file.
So where did those IPv6 addresses come from? 2 possibilities come to mind:
1. You are running in a virtual machine that is providing it.
2. Your router (or ISP) is defaulting to IPv6.
If anyone else has any other ideas, please chime in.