From: Denis Vlasenko <vda@ilport.com.ua>
To: linux-os@analogic.com, Michael Tokarev <mjt@tls.msk.ru>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: sent an invalid ICMP type 11, code 0 error to a broadcast: 0.0.0.0 on lo?
Date: Thu, 7 Jul 2005 11:25:39 +0300 [thread overview]
Message-ID: <200507071125.39046.vda@ilport.com.ua> (raw)
In-Reply-To: <Pine.LNX.4.61.0507061319440.5241@chaos.analogic.com>
On Wednesday 06 July 2005 20:27, Richard B. Johnson wrote:
> Only the 127.0.0.0 network should be routed through the loop-back
> device.
This is the normal dose of disinformation embedded into
otherwise useful reply from Richard. Sometimes I wonder
whether he does this for fun for for some other dark
and obscure reason.
Anyway, lo is perfetly happy with packets other than 127.x.x.x
going thru it.
# ip a
1: if: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:04:23:15:ba:76 brd ff:ff:ff:ff:ff:ff
inet 172.17.13.22/16 brd 172.17.255.255 scope global if
2: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
# ip r
172.17.0.0/16 dev if proto kernel scope link src 172.17.13.22
default via 172.17.0.1 dev if
# ping -c4 172.17.13.22
PING 172.17.13.22 (172.17.13.22) 56(84) bytes of data.
64 bytes from 172.17.13.22: icmp_seq=1 ttl=64 time=0.155 ms
64 bytes from 172.17.13.22: icmp_seq=2 ttl=64 time=0.113 ms
64 bytes from 172.17.13.22: icmp_seq=3 ttl=64 time=0.122 ms
64 bytes from 172.17.13.22: icmp_seq=4 ttl=64 time=0.121 ms
--- 172.17.13.22 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3011ms
rtt min/avg/max/mdev = 0.113/0.127/0.155/0.021 ms
On the other console:
# tcpdump -nlilo
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on lo, link-type EN10MB (Ethernet), capture size 68 bytes
11:20:37.669996 IP 172.17.13.22 > 172.17.13.22: icmp 64: echo request seq 1
11:20:37.670093 IP 172.17.13.22 > 172.17.13.22: icmp 64: echo reply seq 1
11:20:38.671066 IP 172.17.13.22 > 172.17.13.22: icmp 64: echo request seq 2
11:20:38.671125 IP 172.17.13.22 > 172.17.13.22: icmp 64: echo reply seq 2
11:20:39.672327 IP 172.17.13.22 > 172.17.13.22: icmp 64: echo request seq 3
11:20:39.672389 IP 172.17.13.22 > 172.17.13.22: icmp 64: echo reply seq 3
11:20:40.681857 IP 172.17.13.22 > 172.17.13.22: icmp 64: echo request seq 4
11:20:40.681922 IP 172.17.13.22 > 172.17.13.22: icmp 64: echo reply seq 4
--
vda
next prev parent reply other threads:[~2005-07-07 8:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-06 12:30 Michael Tokarev
2005-07-06 17:27 ` Richard B. Johnson
2005-07-07 8:25 ` Denis Vlasenko [this message]
2005-07-07 11:56 ` Michael Tokarev
2005-07-07 12:34 ` Richard B. Johnson
2005-07-07 13:05 ` Michael Tokarev
2005-07-08 11:18 ` Denis Vlasenko
2005-07-08 11:34 ` Richard B. Johnson
2005-07-08 11:13 ` Denis Vlasenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200507071125.39046.vda@ilport.com.ua \
--to=vda@ilport.com.ua \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.com \
--cc=mjt@tls.msk.ru \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®