--On Wednesday, August 29, 2001 03:25:42 PM +0900 "YOSHIFUJI Hideaki
/ =?iso-2022-jp?B?GyRCNUhGIzFRTEAbKEI=?=" <yoshfuji@xxxxxxxxxxxxxx>
wrote:
> In article <15990000.999065086@localhost> (at Wed, 29 Aug 2001
> 08:04:46 +0200), Peter Bieringer <pb@xxxxxxxxxxxx> says:
>
>> > BTW, ip6_forward() in net/ipv6/ip6_output.c checks
>> > ipv6_devconf.forwarding only.
>> > It seems we should check idev_of_input_device->cnf.forwarding,
>> > too...
>>
>> Attention: afaik there are different meanings of this switch
>> "per device" has different meaning than "per IPv6" on setting.
>
> Yes, but
>
>
>> Forwarding switching per device is currently not implemented,
>> control has another meaning (sets isRouter on advertisements).
>
> If a node forwards, it should announce NA with is_router set, IMHO.
I had a discussion with Pekka some time ago in which he find out,
what the settings are really do.
Control the flag isRouter can be needed if a router has more than 2
interfaces and one of them is a stub network for which the router
should not announce that he is a router.
Behavior is like KAME at the moment.
Thread around May 02, 2001
-- 8<-- (itojun on usagi-users)
in KAME stack, the only legal combination is:
accept_rtadv=0, forwarding=1 router
accept_rtadv=1, forwarding=0 autoconfigured host
accept_rtadv=0, forwarding=0 manually configured
host
1/1 combination is not prohibited, just for experimental
purposes.
we are not trying to promote configuration like 1/1.
(netbsd /etc/rc.d/network prohibits 1/1).
-- >8--
BTW: afair in IPv4 (where the forwarding-per-device switch has a
different meaning) this switch is checked on packet input on that
device, not on output.
Peter
|