[radvd-devel-l] Wrongly picks and advertises /80 IPs

[Reuben Hawkins]

Hi Roman,

Why should RADVD not advertise the /80?  It's in the config file and it
appears to be enabled?  What am I missing?

Thanks,
Reuben


On Sat, Feb 16, 2013 at 9:04 AM, Reuben Hawkins <reubenhwk at gmail.com> wrote:

> Hi Roman,
>
> Thanks for the bug report.  I'll look into it when I get some surplus time.
>
> Thanks,
> Reuben
>
>
> On Fri, Feb 15, 2013 at 5:55 AM, Roman Mamedov <rm at romanrm.ru> wrote:
>
>> Hello,
>>
>> radvd.conf:
>>
>> interface eth1.2 {
>>     AdvSendAdvert on;
>>     AdvManagedFlag on;
>>     AdvLinkMTU 1492;
>>     prefix ::/64 { };
>>     RDNSS fd39::39 { };
>>     DNSSL romanrm.ru romanrm.net romanrm.hk version6.ru { };
>> };
>>
>> Interface:
>>
>> eth1.2    Link encap:Ethernet  HWaddr 00:60:6e:20:25:99
>>           inet addr:192.168.2.39  Bcast:192.168.2.255  Mask:255.255.255.0
>>           inet6 addr: 2a02:2698:xxxx:xxxx:fff2::39/80 Scope:Global
>>           inet6 addr: fd39:0:2::39/64 Scope:Global
>>           inet6 addr: fe80::260:6eff:fe20:2599/64 Scope:Link
>>           UP BROADCAST RUNNING MULTICAST  MTU:1492  Metric:1
>>           RX packets:5577 errors:0 dropped:0 overruns:0 frame:0
>>           TX packets:4016 errors:0 dropped:0 overruns:0 carrier:0
>>           collisions:0 txqueuelen:0
>>           RX bytes:477626 (466.4 KiB)  TX bytes:434209 (424.0 KiB)
>>
>>
>> radvdump on the client:
>>
>> #
>> # radvd configuration generated by radvdump 1.8.5
>> # based on Router Advertisement from fe80::260:6eff:fe20:2599
>> # received by interface eth1
>> #
>>
>> interface eth1
>> {
>>         AdvSendAdvert on;
>>         # Note: {Min,Max}RtrAdvInterval cannot be obtained with radvdump
>>         AdvManagedFlag on;
>>         AdvOtherConfigFlag off;
>>         AdvReachableTime 0;
>>         AdvRetransTimer 0;
>>         AdvCurHopLimit 64;
>>         AdvDefaultLifetime 1800;
>>         AdvHomeAgentFlag off;
>>         AdvDefaultPreference medium;
>>         AdvLinkMTU 1492;
>>         AdvSourceLLAddress on;
>>
>>         prefix fd39:0:2::/64
>>         {
>>                 AdvValidLifetime 86400;
>>                 AdvPreferredLifetime 14400;
>>                 AdvOnLink on;
>>                 AdvAutonomous on;
>>                 AdvRouterAddr on;
>>         }; # End of prefix definition
>>
>>
>>         prefix 2a02:2698:xxxx:xxxx:fff2::/80
>>         {
>>                 AdvValidLifetime 86400;
>>                 AdvPreferredLifetime 14400;
>>                 AdvOnLink on;
>>                 AdvAutonomous on;
>>                 AdvRouterAddr on;
>>         }; # End of prefix definition
>>
>>
>>         RDNSS fd39::39
>>         {
>>                 AdvRDNSSLifetime 600;
>>         }; # End of RDNSS definition
>>
>>
>>         DNSSL romanrm.ru romanrm.net romanrm.hk version6.ru
>>         {
>>                 AdvDNSSLLifetime 600;
>>         }; # End of DNSSL definition
>>
>> }; # End of interface definition
>>
>> -----
>>
>> The config clearly states "prefix ::/64".
>> RADVD should not have picked the /80 IP to advertise as a /80 prefix.
>> This IP should have been ignored.
>> This particular IP was never intended by me for RA, and the client
>> now spams the log with
>>
>> [338607.660000] IPv6 addrconf: prefix with wrong length 80
>> [338623.680000] IPv6 addrconf: prefix with wrong length 80
>> [338639.710000] IPv6 addrconf: prefix with wrong length 80
>>
>>
>> --
>> With respect,
>> Roman
>>
>> --
>> radvd-devel-l mailing list  :  radvd-devel-l at litech.org
>> http://lists.litech.org/listinfo/radvd-devel-l
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.litech.org/pipermail/radvd-devel-l/attachments/20130226/be70d0e4/attachment.html>