From: Simon Wunderlich <simon.wunderlich@s2003.tu-chemnitz.de>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] alfred: Allow listening interface to appear/disappear
Date: Thu, 3 Oct 2013 16:18:54 +0200 [thread overview]
Message-ID: <20131003141852.GA3588@pandem0nium> (raw)
In-Reply-To: <1380628934-22220-1-git-send-email-sven@open-mesh.com>
[-- Attachment #1: Type: text/plain, Size: 1415 bytes --]
On Tue, Oct 01, 2013 at 02:02:08PM +0200, Sven Eckelmann wrote:
> Hi,
>
> a device running alfred maybe has to remove the underlying device (e.g. wlan
> device has to be reconfigured). This currently makes it necessary to restart
> alfred to get the device sending data again. An unwanted side effect of this
> procedure is the removal of all data currently stored in alfred.
>
> Instead alfred should detect such problems and try to recover by reopening the
> device after sleeping a while. The sleeping is automatically done by select.
>
> I've tested the changes only using macvtap:
>
> Terminal 1:
>
> $ ip link del dev macvlan0
> $ ip link add link eth0 name macvlan0 type macvlan
> $ ip link set macvlan0 address 1a:46:0b:ca:bc:7b up
> $ ./alfred -b none -i macvlan0
>
> Terminal 2 (after letting alfred run for a while)
>
> $ ip link del dev macvlan0
> $ ip link add link eth0 name macvlan0 type macvlan
> $ ip link set macvlan0 address 1a:46:0b:ca:bc:7b up
>
> Kind regards,
> Sven
Thanks, applied the whole series (785bc8b, 87c1916, 02997b2, 1b79312, 65d26ca, d6de864).
Your testsetup did not work for me (no IPv6 addresses where assigned to these macvlan0
interfaces), but I've tried on my WiFi network in alfred master mode and could confirm
that alfred continues to send announcements after tearing down the WiFi and setting it
up again.
Thanks,
Simon
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2013-10-03 14:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-01 12:02 [B.A.T.M.A.N.] alfred: Allow listening interface to appear/disappear Sven Eckelmann
2013-10-01 12:02 ` [B.A.T.M.A.N.] [PATCH 1/6] alfred: Close netsock when initialization failed Sven Eckelmann
2013-10-01 12:02 ` [B.A.T.M.A.N.] [PATCH 2/6] alfred: Don't access netsock when it is invalid Sven Eckelmann
2013-10-01 12:02 ` [B.A.T.M.A.N.] [PATCH 3/6] alfred: Try to detect error on socket Sven Eckelmann
2013-10-01 12:02 ` [B.A.T.M.A.N.] [PATCH 4/6] alfred: Handle failed announcement as netsock error Sven Eckelmann
2013-10-01 12:02 ` [B.A.T.M.A.N.] [PATCH 5/6] alfred: Try to reinitialize invalid netsock Sven Eckelmann
2013-10-01 12:02 ` [B.A.T.M.A.N.] [PATCH 6/6] alfred: Remove unused check for device MTU Sven Eckelmann
2013-10-03 14:18 ` Simon Wunderlich [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=20131003141852.GA3588@pandem0nium \
--to=simon.wunderlich@s2003.tu-chemnitz.de \
--cc=b.a.t.m.a.n@lists.open-mesh.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