FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Ubuntu > Ubuntu Kernel Team

 
 
LinkBack Thread Tools
 
Old 02-28-2011, 03:03 PM
Ruben Laban
 
Default Odd issue with 6in4 (sit) tunnels

Hi,

I'm seeing something very odd with 6in4/sit tunnels: when I specify the local IPv4 address, the link local address of the tunnel gets a /128 mask assigned instead
of the usual /64:

$ sudo ip tunnel add sit-ok mode sit remote 10.10.10.10
$ sudo ip tunnel add sit-not-ok mode sit local 192.168.178.30 remote 10.10.10.10
$ sudo ip link set sit-ok up
$ sudo ip link set sit-not-ok up
$ ip -6 address show sit-ok
21: sit-ok: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1480
inet6 fe80::c0a8:b21e/64 scope link
valid_lft forever preferred_lft forever
$ ip -6 address show sit-not-ok
22: sit-not-ok: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1480
inet6 fe80::c0a8:b21e/128 scope link
valid_lft forever preferred_lft forever
$

I can't think of any reason why this would be intended behaviour. Both cases do get a fe80::/64 route:

$ ip -6 route show | grep sit
fe80::/64 via :: dev sit-ok proto kernel metric 256 mtu 1480 advmss 1420 hoplimit 0
fe80::/64 via :: dev sit-not-ok proto kernel metric 256 mtu 1480 advmss 1420 hoplimit 0

Am I missing something here, or is it just some oversight somewhere in the IPv6 handling?

Regards,
Ruben Laban

--
kernel-team mailing list
kernel-team@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kernel-team
 
Old 03-01-2011, 11:43 AM
Ruben Laban
 
Default Odd issue with 6in4 (sit) tunnels

Replying to myself here.

On Monday 28 February 2011 at 17:03 (CET), Ruben Laban wrote:
> I'm seeing something very odd with 6in4/sit tunnels: when I specify the
> local IPv4 address, the link local address of the tunnel gets a /128 mask
> assigned instead of the usual /64:

I noticed that the sixxs interface created by aiccu didn't show the same
symptoms. After digging around its source I found out why:

Instead of doing:
ip tunnel create sitX mode sit local A.B.C.D remote E.F.G.H ttl 64
ip link set sitX up

it does:
ip tunnel create sitX mode sit remote E.F.G.H ttl 64
ip link set sitX up
ip tunnel change sitX local A.B.C.D

It's nasty, really nasty, but it does get the job done.

Regards,
Ruben Laban

--
kernel-team mailing list
kernel-team@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kernel-team
 

Thread Tools




All times are GMT. The time now is 12:17 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org