[Xorp-hackers] register_vif ifindex
Pavlin Radoslavov
pavlin at ICSI.Berkeley.EDU
Tue Aug 19 21:39:27 PDT 2008
Ben Greear <greearb at candelatech.com> wrote:
> It seems that register_vif uses the PifIndex of another
> 'real' port in the router. Should it perhaps use the pimreg
> port, or just have a 0 like the discard interface?
KAME-derived IPv6 kernels require that the register_vif has a valid
physical interface index, hence it is not set to 0.
Also, have in mind that the Linux-specific pimreg kernel interface
is created _after_ the MFEA's setsockopt(MRT_ADD_VIF) for the
VIFF_REGISTER multicast interface. I.e., it is not available when
MfeaNode::add_pim_register_vif() is called.
Pavlin
> root at lanforge-nec-demo> show mfea interface
> Interface State Vif/PifIndex Addr Flags
> 1.2.2 UP 0/84 10.1.2.2 MULTICAST BROADCAST KERN_UP
> 2.3.2 UP 1/86 10.2.3.2 MULTICAST BROADCAST KERN_UP
> br2 UP 2/73 10.2.2.2 MULTICAST BROADCAST KERN_UP
> my_discard DISABLED 3/0 KERN_UP
> register_vif UP 4/73 10.2.2.2 PIM_REGISTER KERN_UP
> root at lanforge-nec-demo>
>
> --
> Ben Greear <greearb at candelatech.com>
> Candela Technologies Inc http://www.candelatech.com
>
> _______________________________________________
> Xorp-hackers mailing list
> Xorp-hackers at icir.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-hackers
More information about the Xorp-hackers
mailing list