[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

General questions setting up IPv6 on my playground (Linux Debian Woody)



[Sorry, I suppose this is not strictly on topic. I did not found a
better place to ask (so: if you have any better suggestions feel free
to redirect the question]


I am trying to play with IPv6 in my private playground. The does not
work as I expect (which oviousliy is a problem of me beeing quite
clueless in IPv6 concepts). I already read the Linux IPv6 howto but
some concepts are not very clear to me.

Maybe you can help me, RTFM is appreciated, too. 



My setup: Two machines running Linux (Debian Woody) connected by
ethernet.

Onne of them ('toxic') is connected to the internet by dial-up
connection.

I installed the client for Freenet6-tunneling on that maschine.

But first the basics: 

Let's habe a look at the network configuration of "toxic":


| eth0      Link encap:Ethernet  HWaddr 00:01:02:26:F7:A7  
|           inet addr:192.168.0.97  Bcast:192.168.0.255  Mask:255.255.255.0
|           inet6 addr: fe80::201:2ff:fe26:f7a7/10 Scope:Link
|           inet6 addr: 3ffe:bc0:10ab:1::1/64 Scope:Global
|           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
|           RX packets:54642931 errors:0 dropped:0 overruns:0 frame:0
|           TX packets:81591479 errors:0 dropped:0 overruns:0 carrier:0
|           collisions:0 txqueuelen:100 
|           RX bytes:129845406 (123.8 MiB)  TX bytes:2533045306 (2.3 GiB)
|           Interrupt:10 Base address:0x7c00 
| 
| lo        Link encap:Local Loopback  
|           inet addr:127.0.0.1  Mask:255.0.0.0
|           inet6 addr: ::1/128 Scope:Host
|           UP LOOPBACK RUNNING  MTU:16436  Metric:1
|           RX packets:19256596 errors:0 dropped:0 overruns:0 frame:0
|           TX packets:19256596 errors:0 dropped:0 overruns:0 carrier:0
|           collisions:0 txqueuelen:0 
|           RX bytes:2575921871 (2.3 GiB)  TX bytes:2575921871 (2.3 GiB)
| 
| sit1      Link encap:IPv6-in-IPv4  
|           inet6 addr: 3ffe:bc0:8000::3ebf/128 Scope:Global
|           inet6 addr: fe80::d9b8:846f/10 Scope:Link
|           inet6 addr: fe80::c0a8:61/10 Scope:Link
|           UP POINTOPOINT RUNNING NOARP  MTU:1494  Metric:1
|           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
|           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
|           collisions:0 txqueuelen:0 
|           RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

the ppp0 interface is down at te moment, dont't worry. If it is up, I
could ping6 3ffe:bc0:8000::3ebf, the address of the tunnel
endpoint. Fine :-)


What confuses me is the netmask of the link addres of eth0: 

|           inet6 addr: fe80::201:2ff:fe26:f7a7/10 Scope:Link

which I /thought/ to be at least uncommon. I double checked my
interfaces setup but there is no definition of any IPv6 adressing
around.


Okay, so we have a look at the other maschine: 


| niehaus@crystalline:~$ /sbin/ifconfig 
| eth0      Protokoll:Ethernet  Hardware Adresse 00:0D:60:8C:3B:BD  
|           inet Adresse:192.168.0.100  Bcast:192.168.0.255  Maske:255.255.255.0
|           inet6 Adresse: fe80::20d:60ff:fe8c:3bbd/64 Scope: Link
|           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
|           RX packets:1495842 errors:0 dropped:0 overruns:0 frame:0
|           TX packets:897901 errors:0 dropped:0 overruns:0 carrier:0
|           Kollisionen:0 Sendewarteschlangenlänge:1000 
|           RX bytes:1897606049 (1.7 GiB)  TX bytes:81001277 (77.2 MiB)
|           Basisadresse:0x8000 Speicher:c0220000-c0240000 
| 
| irda0     Protokoll:IrLAP  Hardware Adresse 75:ba:e2:44  
|           UP RUNNING NOARP  MTU:2048  Metric:1
|           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
|           TX packets:118867 errors:0 dropped:0 overruns:0 carrier:0
|           Kollisionen:0 Sendewarteschlangenlänge:8 
|           RX bytes:0 (0.0 b)  TX bytes:3786763 (3.6 MiB)
| 
| lo        Protokoll:Lokale Schleife  
|           inet Adresse:127.0.0.1  Maske:255.0.0.0
|           inet6 Adresse: ::1/128 Scope: Host
|           UP LOOPBACK RUNNING  MTU:16436  Metric:1
|           RX packets:29268 errors:0 dropped:0 overruns:0 frame:0
|           TX packets:29268 errors:0 dropped:0 overruns:0 carrier:0
|           Kollisionen:0 Sendewarteschlangenlänge:0 
|           RX bytes:16657568 (15.8 MiB)  TX bytes:16657568 (15.8 MiB)

For some reason I have a /64 netmask here (which I think makes much
more sense)[1].

I thought, auto configuration would get a step further and let me
ping6 between the maschines but it dind't - prabably because the IPv6
adresses ar misconfigured. Any idea , why this misconfiguration
happened? I tried to initialize the interfaces again, but that didn`t
change anything).


Du I need to run radvd? I already tried: again: No success au all
althoug radvddump shows, that advertisements are transmitted.


My configuration file (which has been generated by tspc[2])

| niehaus@toxic:~$ cat  /etc/radvd.conf 
| interface eth0
| {
|  AdvSendAdvert on;
|  prefix 3ffe:0bc0:10ab:0001::/64
|  {
|  AdvOnLink on;
|  AdvAutonomous on;
|  };
| };
|   
| niehaus@toxic:~$ 

running radvd on "toxic" (which has IPv6 connectivity) makes appear
announcments on crystalline:

| crystalline:/home/niehaus# radvdump 
| Router advertisement from fe80::201:2ff:fe26:f7a7 (hoplimit 255)
| Received by interface eth0
|         # Note: {Min,Max}RtrAdvInterval cannot be obtained with radvdump
|         AdvCurHopLimit: 64
|         AdvManagedFlag: off
|         AdvOtherConfigFlag: off
|         AdvHomeAgentFlag: off
|         AdvReachableTime: 0
|         AdvRetransTimer: 0
|         Prefix 3ffe:bc0:10ab:1::/64
|                 AdvValidLifetime: 2592000
|                 AdvPreferredLifetime: 604800
|                 AdvOnLink: on
|                 AdvAutonomous: on
|                 AdvRouterAddr: off
|         AdvSourceLLAddress: 00 01 02 26 F7 A7 


... but I don't observe any IPv6 reconfiguration. BTW:

| niehaus@crystalline:~$ cat /proc/sys/net/ipv6/conf/eth0/accept_ra 
| 1
| niehaus@crystalline:~$ cat /proc/sys/net/ipv6/conf/eth0/autoconf  
| 1

This stuff is turned on. 



Can vou give me any hints what I am missing?

Thanks in advance!



Sebastian


Footnotes:
____________________________


[1] I just set up another box fresh install Debian Woody) on the same
ethernet (connected by the same switch):



| niehaus@narcotic:~$ /sbin/ifconfig 
| eth0      Link encap:Ethernet  HWaddr 00:02:1C:F7:26:78  
|           inet addr:192.168.0.99  Bcast:192.168.0.255  Mask:255.255.255.0
|           inet6 addr: fe80::202:1cff:fef7:2678/10 Scope:Link
|           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
|           RX packets:110192 errors:0 dropped:0 overruns:1032 frame:0
|           TX packets:93198 errors:0 dropped:0 overruns:0 carrier:0
|           collisions:0 txqueuelen:100 
|           RX bytes:13691410 (13.0 MiB)  TX bytes:26021047 (24.8 MiB)
|           Interrupt:11 Base address:0xd800 
| 
| lo        Link encap:Local Loopback  
|           inet addr:127.0.0.1  Mask:255.0.0.0
|           inet6 addr: ::1/128 Scope:Host
|           UP LOOPBACK RUNNING  MTU:16436  Metric:1
|           RX packets:22555 errors:0 dropped:0 overruns:0 frame:0
|           TX packets:22555 errors:0 dropped:0 overruns:0 carrier:0
|           collisions:0 txqueuelen:0 
|           RX bytes:10595114 (10.1 MiB)  TX bytes:10595114 (10.1 MiB)
| 
| niehaus@narcotic:~$ 


It has -- again this strange subnet mask.




[2] The tspc log comes here: 

| <tunnel action="info" type="v6v4" lifetime="604800">   
|         <server>     
|                 <address type="ipv4">206.123.31.115</address>
|                 <address type="ipv6">3ffe:0bc0:8000:0000:0000:0000:0000:3ebe</address>
|         </server>
| 
|         <client>
|                 <address type="ipv4">217.184.132.111</address>    
|                 <address type="ipv6">3ffe:0bc0:8000:0000:0000:0000:0000:3ebf</address>
|                 <address type="ns">worst-case.tsps2.freenet6.net</address>     
| 
|                 <router>
|                         <prefix length="48">3ffe:0bc0:10ab:0000:0000:0000:0000:0000</prefix>
|                 </router>
|         </client> 
| </tunnel>


-- 



Reply to: