Ipv6 and miredo - where do ip addresses come from?

A

ainu2012-10-23 15:46:57

linux

ainu, 2012-10-23 15:46:57

I put it on a car with ubuntu miredo. Initially, the provider does not provide ipv6 addresses. Now even ipv6 works. If I connect via ipv6 to another server, on that second server, the ipv6 IP address of the connecting is determined. At this address, you can connect to the first machine (for example, through port 22 via ssh).
Actually, the question is - where does this address come from, and is it permanent, “white”?
In other words, can it be whitelisted?

UPD: ifconfig

eth0      Link encap:Ethernet  HWaddr 00:0e:a6:f4:c4:b2
          inet addr:77.72.250.26  Bcast:77.255.255.255  Mask:255.0.0.0
          inet6 addr: fe80::20e:a6ff:fef4:c4b2/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:14907745 errors:0 dropped:0 overruns:0 frame:0
          TX packets:12642198 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:14337917276 (14.3 GB)  TX bytes:2698605121 (2.6 GB)
          Interrupt:16

eth1      Link encap:Ethernet  HWaddr 00:0e:a6:f4:c5:9e
          inet addr:192.168.0.1  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::20e:a6ff:fef4:c59e/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:9356485 errors:0 dropped:62 overruns:0 frame:2
          TX packets:11817111 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:3030238417 (3.0 GB)  TX bytes:10063333460 (10.0 GB)
          Interrupt:17

lo        Link encap:Локальная петля (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:404326 errors:0 dropped:0 overruns:0 frame:0
          TX packets:404326 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:337272073 (337.2 MB)  TX bytes:337272073 (337.2 MB)

teredo    Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          inet6 addr: fe80::ffff:ffff:ffff/64 Scope:Link
          inet6 addr: 2001:0:53aa:64c:3062:71fe:b2b7:5e5/32 Scope:Общий
          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1280  Metric:1
          RX packets:55 errors:0 dropped:0 overruns:0 frame:0
          TX packets:65 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:500
          RX bytes:9887 (9.8 KB)  TX bytes:11271 (11.2 KB)

Reply

Answer the question

In order to leave comments, you need to log in

1 answer(s)

P

platerx, 2012-10-23
@ainu

It is formed from the ipv4 address of the teredo server, your external ipv4 address, the UDP port on which the tunnel is up, and other parameters. More details can be found here: en.wikipedia.org/wiki/Teredo_tunneling IPv6 addressing section