From: Mike Kazantsev <mk.fraggod@gmail.com>
To: netfilter@vger.kernel.org
Subject: [SOLVED] Re: IPv6 forwarding to TAP-interface fails
Date: Mon, 21 Dec 2009 14:09:52 +0500 [thread overview]
Message-ID: <20091221140952.63c607f5@malediction> (raw)
In-Reply-To: <20091221114648.08eede72@malediction>
[-- Attachment #1: Type: text/plain, Size: 2286 bytes --]
On Mon, 21 Dec 2009 11:46:48 +0500
Mike Kazantsev <mk.fraggod@gmail.com> wrote:
> Then I start the simple ping6 from lan network to vde (VM):
...
>
> IP6 2001:470:1f0b:11de::22 > ff02::1:ff00:21: ICMP6, neighbor
> solicitation, who has 2001:470:1f0b:11de::21, length 32
> IN=vde OUT= MAC=33:33:ff:00:00:21:00:16:3e:16:38:41:86:dd
> SRC=2001:0470:1f0b:11de:0000:0000:0000:0022
> DST=ff02:0000:0000:0000:0000:0001:ff00:0021
> LEN=72 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=ICMPv6 TYPE=135 CODE=0
>
> IP6 2001:470:1f0b:11de::21 > 2001:470:1f0b:11de::22: ICMP6,
> neighbor advertisement, tgt is 2001:470:1f0b:11de::21, length 32
> IN= OUT=vde
> SRC=2001:0470:1f0b:11de:0000:0000:0000:0021
> DST=2001:0470:1f0b:11de:0000:0000:0000:0022
> LEN=72 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=ICMPv6 TYPE=136 CODE=0
>
Just looking at these lines as I pasted them actually helped: ICMP6
neighbor solicitation request was sent from 22 to 21, while the packets
were originated from 21.
Made me wondering about what kind of backwards magic is at work here...
> ip addr:
...
> 7: vde: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 500
> link/ether b2:f5:e7:68:fd:9e brd ff:ff:ff:ff:ff:ff
> inet 192.168.0.20/28 scope global vde
> inet6 2001:470:1f0b:11de::20/125 scope global
> valid_lft forever preferred_lft forever
And here's the problem: no link-local address on the interface.
"ip addr flush dev vde" in init.d script setting up interface did that,
that was the mistake.
With this address added (or rather preserved), router is able to send
neighbor solicitation requests from it and everything works fine.
Anyway, strange thing is that, apparently, VM on the other side is able
to send these requests without link-local address, using global one
instead:
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qlen 1000
inet6 2001:470:1f0b:11de::22/125 scope global
valid_lft forever preferred_lft forever
Guess older kernel (2.6.30.4) there is the cause of it, and that's also
why it worked before with pretty much the same setup.
Thanks again to Pascal for pointing me in the right direction.
--
Mike Kazantsev // fraggod.net
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2009-12-21 9:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-19 11:20 IPv6 forwarding to TAP-interface with ip6tables fails Mike Kazantsev
2009-12-19 14:09 ` Pascal Hambourg
2009-12-21 6:46 ` IPv6 forwarding to TAP-interface fails Mike Kazantsev
2009-12-21 9:09 ` Mike Kazantsev [this message]
2009-12-23 13:03 ` [SOLVED] " Pascal Hambourg
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=20091221140952.63c607f5@malediction \
--to=mk.fraggod@gmail.com \
--cc=netfilter@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).