From: "Bjørn Mork" <bjorn@mork.no>
To: netdev@vger.kernel.org
Subject: Re: [RFC] ipv6: always join solicited-node address
Date: Mon, 14 Oct 2013 09:09:59 +0200 [thread overview]
Message-ID: <87fvs4s4zc.fsf@nemi.mork.no> (raw)
In-Reply-To: <20131014005508.GE14021@order.stressinduktion.org> (Hannes Frederic Sowa's message of "Mon, 14 Oct 2013 02:55:08 +0200")
Hannes Frederic Sowa <hannes@stressinduktion.org> writes:
> IFF_NOARP seems to be a bit messed up in ipv6. Your patch seems fine to
> me but I would add protection to the ndisc_rcv and sending routines to
> do nothing if IFF_NOARP is set for that interface.
That's what I thought. So for my problem, this will not really change
much.
> So it would be possible that you could resolve this issue by just issuing
> an "ip link set arp on dev <interface>" and won't have hassle with racing
> interface initialization.
Yes, but that would also make the IP layer try to resolve IP to link
layer addressess both for IPv4 and IPv6, which just won't work. At least
not for IPv4, where there just is no way to transport an ARP to the
modem. And I assume it may fail for IPv6 too on any sane device.
> Is this a specific bug of the modem you are using or are all devices
> powered by this driver like this?
Unfortunately I have no IPv6 enabled SIM myself, so I have no
information about other devices. This report was based on user
feedback.
I assume the bug is specific to this firmware implementation, probably
extending to all similar devices from the same vendor. But it could be
more common than that. The fact that the bug is there indicates that
this works just fine in Windows.
Yes, I realize that I am in ugly-hack-to-workaround-firmware-issues land
again... But it sure would be nice to have some way for a driver to
indicate that L2 neighbour tables are meaningless, but that any incoming
requests should still be answered.
Bjørn
next prev parent reply other threads:[~2013-10-14 7:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-13 17:24 [RFC] ipv6: always join solicited-node address Bjørn Mork
2013-10-14 0:55 ` Hannes Frederic Sowa
2013-10-14 7:09 ` Bjørn Mork [this message]
2013-10-14 15:56 ` Hannes Frederic Sowa
2013-10-31 15:00 ` Bjørn Mork
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=87fvs4s4zc.fsf@nemi.mork.no \
--to=bjorn@mork.no \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).