From: Roland Dreier <rdreier@cisco.com>
To: John Dykstra <john.dykstra1@gmail.com>
Cc: Roland Dreier <roland@digitalvampire.org>, netdev@vger.kernel.org
Subject: Re: IPv6 default routes timing out?
Date: Thu, 30 Jul 2009 11:34:21 -0700 [thread overview]
Message-ID: <aday6q6qatu.fsf@cisco.com> (raw)
In-Reply-To: <1248975058.7167.28.camel@Maple> (John Dykstra's message of "Thu, 30 Jul 2009 12:30:58 -0500")
> > Thanks, I did some more debugging it seems the issue is in the
> > router's (openbsd) wireless driver -- it thinks it is broadcasting
> > router advertisements but they aren't making it to the laptop.
> Could it be that there's something buggy in the laptop wireless driver
> or hardware re filtering of multicast packets at the L2 level?
Well, I see router advertisements (and pings to ff02::1) from the router
on both of the two laptops I have handy, and then after a while the
openbsd system seems to stop broadcasting -- I no longer see the
broadcast ipv6 packets on either laptop, but if I just do "ifconfig ral0
down; ifconfig ral0 up" on the openbsd system then everything seems to
come back. So it seems unlikely that the problem is anywhere except on
the openbsd system sending.
It's interesting to note that the only broadcasts that the openbsd
router is going to send that matter in my setup are ipv6 router
advertisements -- before I started using ipv4, all the broadcasts would
have been arps from the laptops to the router, so I would have never
noticed that the router stopped being able to broadcast.
- R.
next prev parent reply other threads:[~2009-07-30 18:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-29 17:42 IPv6 default routes timing out? Roland Dreier
2009-07-30 0:33 ` John Dykstra
2009-07-30 16:58 ` Roland Dreier
2009-07-30 17:30 ` John Dykstra
2009-07-30 18:34 ` Roland Dreier [this message]
2009-07-30 20:09 ` John Dykstra
2009-07-30 20:58 ` Roland Dreier
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=aday6q6qatu.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=john.dykstra1@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=roland@digitalvampire.org \
/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).