From: Sascha Hlusiak <saschahlusiak@arcor.de>
To: linux-kernel@vger.kernel.org
Subject: Manually invoke IPv6 router solicitation messages
Date: Thu, 12 Jul 2007 16:51:09 +0200 [thread overview]
Message-ID: <46963FDD.9010900@arcor.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 966 bytes --]
Hi,
Is there a way to manually make the kernel send IPv6 router solicitation
messages? At the moment the kernel will send a few messages after the
interface is brought up and then never again, no matter if it succeeded
or failed to autoconf the device.
Background:
I use wpa_supplicant to connect to wireless and I use ifplugd/netplug to
manage my wired network.
Both tools bring the interface up and immediately the kernel tries to
autoconfigure them, even the cable is not plugged in or the wireless
connection is not yet established. When the connection is finally
brought up, the autoconfig already failed and I have to wait until the
router is so nice to send a router advertisement message by itself.
Does it make sense to have a syscall or /proc entry that makes the
kernel send such a message, or do you suggest having a userspace tool to
send those messages when needed?
Sascha Hlusiak
(Please CC me, since I'm off-list)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
reply other threads:[~2007-07-12 14:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=46963FDD.9010900@arcor.de \
--to=saschahlusiak@arcor.de \
--cc=linux-kernel@vger.kernel.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