On 10/28/2011 08:37 PM, Paolo Galtieri wrote:
> According to most recent RFCs IPv6 addresses starting with 0xFD are
> considered unique local addresses.   This is more or less equivalent
> to the IPv4 private addresses.
>
> I have the following IPv6 address configured on eth0
>
> fd00:1111::41/32
>
> When I run ifconfig eth0 I get:
>
> eth0      Link encap:Ethernet  HWaddr 00:18:F8:0E:76:F2 
>           inet addr:10.0.0.65  Bcast:10.0.0.255  Mask:255.255.255.0
>           inet6 addr: fe80::218:f8ff:fe0e:76f2/64 Scope:Link
>           inet6 addr: fd00:1111::41/32 Scope:Global
>           UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
>           RX packets:15616420 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:11913944 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:13426298081 (12.5 GiB)  TX bytes:1913387990 (1.7 GiB)
>           Interrupt:16 Base address:0xe700
>
> Notice that the entry for fd00:1111::41/32 shows its scope as Global. 
> I would have expected something else.  Am I just misunderstanding the
> concept of local vs global?
>
> Thanks,
> Paolo
They are global in scope. There is nothing in the IPv6 that says where
they can or cannot be routed. Just that they shouldn't be on the global
internet. So, you should firewall such traffic from going out and from
coming in unless you have agreements to route such networks between you
and your associates.

You are very much correct that they are in concept the same as IPv4
private addresses. There are just a lot more of them, so networks can
choose to share such traffic with little change of collisions.

Trever
-- 
"Better to remain silent and be thought a fool than to speak out and
remove all doubt." -- A. Lincoln

Attachment: signature.asc
Description: OpenPGP digital signature

-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines

Reply via email to