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

RE: (usagi-core 01715) Fw: RE: Bind 9.1 + kernel 2.4.1 + debian-s table



Title: RE: (usagi-core 01715) Fw: RE: Bind 9.1 + kernel 2.4.1 + debian-s table

        I use radvd 0.6.2 ......


        the machine with kernel 2.4.1+usagi:

alh-ipv6:/etc/radvd# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:D0:B7:3F:16:EA
          inet addr:192.168.1.182  Bcast:192.168.255.255  Mask:255.255.0.0
          inet6 addr: fe80::2d0:b7ff:fe3f:16ea/10 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:66702 errors:0 dropped:0 overruns:0 frame:3
          TX packets:18258 errors:0 dropped:0 overruns:0 carrier:0
          collisions:1258 txqueuelen:100
          Interrupt:10 Base address:0x2000

alh-ipv6:/etc/radvd# cat /etc/radvd/radvd.conf
interface eth0 {
        AdvSendAdvert on;
#        prefix 5f15:9100:c2dd:1400:8000::0/80 
        prefix 5f15:9100:c2dd:1400::0/64
        {
                AdvOnLink on;
                AdvAutonomous on;
        };
};

-----Mensaje original-----
De: Yuji Sekiya [mailto:sekiya@sfc.wide.ad.jp]
Enviado el: miércoles, 07 de febrero de 2001 19:35
Para: Javier Castillo Alcibar
CC: debian-ipv6@lists.debian.org; usagi-users@linux-ipv6.org
Asunto: Re: (usagi-core 01715) Fw: RE: Bind 9.1 + kernel 2.4.1 +
debian-s table


At Wed, 7 Feb 2001 19:36:14 +0100 ,
Javier  Castillo Alcibar <Castillo@alhsys.com> wrote:

>         I am running radvd to advertise a prefix and I have this experience:
>
>         - with a kernel 2.2(no USAGI patch), the interface eth0 learns the Adv Prefix (Scope: Site)
>         - with a kernel 2.4.1(plus USAGI patch), the interface does not learn the prefix.
>
>         I use the radvd 0.6........I have to config in the kernel/proc any param?

Please use the latest radvd, radvd-0.6.2.

Regards.

-- Yuji Sekiya

-- 
To UNSUBSCRIBE, email to debian-ipv6-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org


Reply to: