From: Julian Anastasov <ja@ssi.bg>
To: Tom London <selinux@gmail.com>
Cc: Dave Jones <davej@redhat.com>, netdev@vger.kernel.org
Subject: Re: return of ip_rt_bug()
Date: Fri, 5 Aug 2011 19:36:41 +0300 (EEST) [thread overview]
Message-ID: <alpine.LFD.2.00.1108051931250.29588@ja.ssi.bg> (raw)
In-Reply-To: <CAFiZG+Wmv_FEx2ZX3qZt0tAr-QVQD_javX1gbRWujr9xyf7nbQ@mail.gmail.com>
Hello,
On Fri, 5 Aug 2011, Tom London wrote:
> I'd like to conclude that this is due to UDP casting on the wlan.
> I'll reboot with the radio on and in debug mode to see what happens.
Sending to 255.255.255.255 without binding to source address
or output device will succeed only if there is a route that matches
the 255.255.255.255 address (default route as last option).
If no route matches, the result is ENETUNREACH and packet
should be dropped. But how input route is attached, I still don't know.
Your ip monitor does not show fatal event that can
invalidate the source address or the default route (that
will match for 255.255.255.255) while sending packet.
It is almost impossible such problem to occur, i.e. between routing
and following re-routing the address/route to disappear.
Such events:
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP>
link/ether
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP>
link/ether
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP>
link/ether
are may be for link, not sure. Events for addresses/routes
would show addresses and routes in a way similar to
ip addr and ip route list.
Not sure where your logs go, may be you can add
"kern.* /var/log/kernel.log" in your /etc/rsyslog.conf. But if
you don't see the WARNING then the problem does not happen.
You can also see the ip_rt_bug line with 'dmesg'. So, can
you confirm the problem occurs only when default route
points to wlan? Even if so, I still don't see good explanation
for the error message.
Regards
--
Julian Anastasov <ja@ssi.bg>
prev parent reply other threads:[~2011-08-05 16:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-02 17:09 return of ip_rt_bug() Dave Jones
2011-08-04 7:23 ` David Miller
2011-08-04 12:20 ` Julian Anastasov
2011-08-04 13:14 ` Tom London
2011-08-04 17:37 ` Julian Anastasov
2011-08-04 17:48 ` Tom London
2011-08-05 2:45 ` Tom London
2011-08-05 7:56 ` Julian Anastasov
2011-08-05 13:18 ` Tom London
2011-08-05 13:30 ` Tom London
2011-08-05 13:37 ` Tom London
2011-08-06 22:14 ` Julian Anastasov
2011-08-08 5:20 ` David Miller
2011-08-09 13:51 ` Julian Anastasov
2011-08-11 13:00 ` David Miller
2011-08-11 16:36 ` rt_iif conversions (was Re: return of ip_rt_bug()) Julian Anastasov
2011-08-12 1:01 ` rt_iif conversions David Miller
2011-08-05 16:36 ` Julian Anastasov [this message]
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=alpine.LFD.2.00.1108051931250.29588@ja.ssi.bg \
--to=ja@ssi.bg \
--cc=davej@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=selinux@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).