| View previous topic :: View next topic |
| Author |
Message |
Leonardo.b
Guru
Joined: 10 Oct 2020
Posts: 308
|
 Posted: Tue Oct 20, 2020 7:10 pm Post subject: Ping doesn't come back. [SOLVED] |
 |
|
When I send ping to a domain, like:
the name is resolved, the IP assigned, and the ping starts his travel over the net.
But, as result, nothing comes back, and I have 100% packet loss.
This is an amd64 laptop with Intel wirless card; firmware patched in the kernel.
I am playing hardened profile (from hardened stage 3), iwd for wireless connection, and libressl. No dhpcdc or openresolv (but I tried both). Not a syslog yet.
resolv.conf contains OpenDNS nameserver and nothing more.
I can access to internet, download packets and perform upgrades.
From Windows or Debian ping works.
net-wireless/iwd stayalone on package.use
Even if when I perform
| Code: | | emerge -av net-wireless/iwd |
it does not displays "stayalone".
Last edited by Leonardo.b on Wed Oct 21, 2020 6:54 pm; edited 1 time in total |
|
| Back to top |
|
 |
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 55193
Location: 56N 3W
|
| Posted: Tue Oct 20, 2020 7:28 pm Post subject: |
|
|
Leonardo.b,
Do you mean USE=standalone ?
You put "stayalone" in your post.
If everything works except ping, I suspect that ping is blocked somewhere. Not at gentoo.org as I get
| Code: | roy@NeddySeagoon_Static ~ $ ping -c1 gentoo.org
PING gentoo.org(2001:41c8:0:936::139 (2001:41c8:0:936::139)) 56 data bytes
64 bytes from 2001:41c8:0:936::139 (2001:41c8:0:936::139): icmp_seq=1 ttl=54 time=25.1 ms
--- gentoo.org ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 25.082/25.082/25.082/0.000 ms
roy@NeddySeagoon_Static ~ $ ping6 -c1 gentoo.org
PING gentoo.org(2001:41c8:0:936::139 (2001:41c8:0:936::139)) 56 data bytes
64 bytes from 2001:41c8:0:936::139 (2001:41c8:0:936::139): icmp_seq=1 ttl=54 time=24.9 ms
--- gentoo.org ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 24.871/24.871/24.871/0.000 ms |
so both IPv4 and IPv6 work.
Try | Code: | | traceroute -U gentoo.org |
That uses a different port.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
Leonardo.b
Guru
Joined: 10 Oct 2020
Posts: 308
|
| Posted: Tue Oct 20, 2020 8:15 pm Post subject: |
|
|
I'm impressed, I did not imagined a so quick answer, thanks.
Well, traceroute works. I put gentoo.org just as an example.
Even without -U parameter, it works.
Pings to myselt work too.
And, yea, the spelling on the last post was wrong, but in any case this USE flag seems to not exist anymore. On the system I copied the correct one.
I don't know if this is related to my issue. I don't think, really. |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 55193
Location: 56N 3W
|
| Posted: Tue Oct 20, 2020 9:06 pm Post subject: |
|
|
Leonardo.b
| Code: | # eix iwd
* net-wireless/iwd
Available versions: 1.8-r3 (~)1.9-r1 **9999*l {+client +crda +monitor ofono standalone systemd wired CPU_FLAGS_X86="aes ssse3" KERNEL="linux"}
Homepage: https://git.kernel.org/pub/scm/network/wireless/iwd.git/
Description: Wireless daemon for linux
|
and | Code: | # grep standalone /usr/portage/net-wireless/iwd/*.ebuild
/usr/portage/net-wireless/iwd/iwd-1.9-r1.ebuild:standalone systemd"
/usr/portage/net-wireless/iwd/iwd-1.9-r1.ebuild: standalone? (
/usr/portage/net-wireless/iwd/iwd-1.9-r1.ebuild: if use standalone ; then
/usr/portage/net-wireless/iwd/iwd-9999.ebuild:standalone systemd"
/usr/portage/net-wireless/iwd/iwd-9999.ebuild: standalone? (
/usr/portage/net-wireless/iwd/iwd-9999.ebuild: if use standalone ; then |
So USE=standalone has just arrived. Its not in 1.8-r3 but its in both 1.9-r1, the testing version and the live version.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
Leonardo.b
Guru
Joined: 10 Oct 2020
Posts: 308
|
| Posted: Tue Oct 20, 2020 10:18 pm Post subject: |
|
|
Emerged ~amd64 version of iwd. This doesn't affected ping.
They still does not come back.
Last edited by Leonardo.b on Wed Oct 21, 2020 5:20 pm; edited 1 time in total |
|
| Back to top |
|
|
Hu
Administrator
Joined: 06 Mar 2007
Posts: 23361
|
| Posted: Wed Oct 21, 2020 2:41 am Post subject: |
|
|
| This may indicate that some system along the way is improperly dropping the ICMP echo request, or the ICMP echo reply. You could try to determine which system it is by using progressively higher TTL values for ping or traceroute. For ping, run ping -c 1 -t 1 www.gentoo.org. This will fail, when the first hop along the route returns a "Time to live exceeded" error. Now re-run with -t 2, then -t 3, and so on up until you get back to the behavior of getting no response at all. This will tell you how many hops out the offending host is. Alternatively, you could use traceroute --icmp to let traceroute adjust the TTL for you. This only finds the bad host. It does not help you to fix it. |
|
| Back to top |
|
|
Leonardo.b
Guru
Joined: 10 Oct 2020
Posts: 308
|
| Posted: Wed Oct 21, 2020 5:38 pm Post subject: |
|
|
Following your advices:
| Code: | | ping -t 1 anyname.com |
Stops.
| Code: | | traceroute --icmp anyname.com |
Returns the first step, called "dsldevice.lan".
Then only * * *
| Code: | | traceroute anyname.com |
Reachs every step, even the first, with no errors.
Could be my system be set to block ping's arrival?
Ping is the only function that seems to not work, and so I don't care too much, but would be intresting to understand why. |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 55193
Location: 56N 3W
|
| Posted: Wed Oct 21, 2020 5:59 pm Post subject: |
|
|
Leonardo.b,
It looks like dsldevice.lan is doing the blocking. That's your router.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
Leonardo.b
Guru
Joined: 10 Oct 2020
Posts: 308
|
| Posted: Wed Oct 21, 2020 7:08 pm Post subject: |
|
|
Ok, it makes sense. Thanks.
I tried Ubuntu LIVE, and noticed that pings don't work here neither.
It confirms that the problem isn't inside the OS, but in the net.
The last time I tried pings with Windows was a while ago.
Something must be changed.
So long,
Leonardo |
|
| Back to top |
|
|
|
Networking & Security
