[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <200903010134.54405.mail@saschahlusiak.de>
Date: Sun, 1 Mar 2009 01:34:48 +0100
From: Sascha Hlusiak <mail@...chahlusiak.de>
To: netdev@...r.kernel.org
Subject: [PATCH] Assign linklocal addresses to isatap from link dev
Hello,
To use isatap on a client, I use the following command:
# ip tunnel add isatap0 mode isatap remote $REMOTE_V4 dev eth0
(without the attached iproute2-patch that command would fail because of the
remote option; patch is sent to maintainer).
Old implemention would then add a linklocal address based on the unset 'local'
option, which is obviously wrong: fe80::5efe:0:0/64
With my patch applied and the tunnel created like above, if a link is attached
to the tunnel, all it's ipv4 addresses are added as isatap compatible
linklocal addresses to the tunnel device. The wrong isatap ll-address above
will not be added anymore, if the 'local' option is unset.
# ip addr
2: eth0: UNKNOWN qlen 1000
[...]
inet 192.168.6.5/24 brd 192.168.6.255 scope global eth0
inet 192.168.6.9/32 scope global eth0
[...]
7: is0@...0: <POINTOPOINT,NOARP,UP,LOWER_UP>
link/sit 0.0.0.0 peer x.x.x.x
inet6 fe80::5efe:c0a8:609/64 scope link
valid_lft forever preferred_lft forever
inet6 fe80::5efe:c0a8:605/64 scope link
valid_lft forever preferred_lft forever
That way stateless autoconf works with isatap tunnels and without knowledge of
the local v4 address.
Signed-off-by: Sascha Hlusiak <mail@...chahlusiak.de>
Thanks,
Sascha Hlusiak
View attachment "iproute2_isatap_remote.patch" of type "text/x-patch" (650 bytes)
View attachment "kernel_addrconf_isatap_ll.patch" of type "text/x-patch" (2336 bytes)
Download attachment "signature.asc " of type "application/pgp-signature" (199 bytes)
Powered by blists - more mailing lists