In article <200108301829.WAA06144@xxxxxxxxxxxxx> (at Thu, 30 Aug 2001 22:29:25
+0400 (MSK DST)), kuznet@xxxxxxxxxxxxx says:
> Let me to repeat: we do not have any flag which blocks forwarding
> per interface. :-) Killing global flag would mean that we do not have
> any way to disable forwarding at all.
>
> So, as soon as you forward at least on one interface, global
> flag must be ON. And packet filtering must be made with firewall.
This description is true *about current implementation*.
But please note that, for each interface,
- whether we forward a packet from it
- whether we set is_router flag in NA to be sent on it
- whether we join (some scope(s) of) all-routers multicast on it
SHOULD be the same.
The patch is not completed for our (at least David's and my)
thought, but it is a start of hacking....
> > join
> > the all-routers multicast group, etc. etc.
>
> WHAT? Kernel does not use this multicast group, hence it has
> no reasons to join it.
>
> If some module will start to use this group, it will join it.
ping6 ff02::2%eth0 ?
(How about ff05::2%site1 etc... sigh.)
--yoshfuji
|