Re: ipv6 global forward overrides dev-specific forwarding

[Peter Bieringer <pb@xxxxxxxxxxxx>]

At 20:21 01.05.2001, kuznet@xxxxxxxxxxxxx wrote:
> Shortly, this flag responds for protocol part, but it has no
> traffic filtering function.

Thank you for the information.

But is it possible to rename/replace the switches to avoid confusion with 
the existing (and still longer living IPv4 switches).

Suggestions:
1) Global (and one and only) IPv6 forwarding control
- /proc/sys/net/ipv6/conf/all/forwarding
+ /proc/sys/net/ipv6/forwarding

Avoids also headache about why the same named switch in the "conf/all" 
directory has a different behavior than the "conf/$device" directory.

2) Perhaps renaming the "conf/$device/forwarding" to a better name. Looks 
like it was taken from BSD/KAME, but it can be misunderstood by IPv4 to 
IPv6 migrators...

-- 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


3) Let "conf/all/forwarding-renamed" control all 
"conf/$device/forwarding-renamed" at one time. Pleaes update this for 
others, too ("mtu" is also not working).
This is a different behavior to the IPv4 tree, too.
Or was the IPv4 solution not a good one?

        Peter